Pierre Couderc writes:
> Mmm, there is some misunderstanding. I have lost nothing.
> All my DBs are ok.
> I am speaking of the specific "postgres" database that you connect to with
> \c postgres
> What is its use ? how to restore it ?
If you know that there should be nothing
On 05/11/2017 07:10 PM, John R Pierce wrote:
On 5/11/2017 9:53 AM, Pierre Couderc wrote:
I have broken my postgres database by typing :
psql How can I safely repair, knowing that I have the pg_dumpall of last
night, but many dbs have changed today... ?
Thanks in advance
was there
On 5/11/2017 9:53 AM, Pierre Couderc wrote:
I have the pg_dumpall of last night, but many dbs have changed
today... ?
suggestion in the future, instead of simply pg_dumpall, where all your
databases are in one opaque lump, try something like...
#!/bin/bash
#
d=`date +\%a`
On 05/11/2017 07:07 PM, Hunley, Douglas wrote:
On Thu, May 11, 2017 at 11:53 AM, Pierre Couderc > wrote:
How can I safely repair, knowing that I have the pg_dumpall of
last night, but many dbs have changed today... ?
If pg_dumpall is
On 5/11/2017 9:53 AM, Pierre Couderc wrote:
I have broken my postgres database by typing :
psql How can I safely repair, knowing that I have the pg_dumpall of last
night, but many dbs have changed today... ?
Thanks in advance
was there anything in the postgres database other than the
On Thu, May 11, 2017 at 11:53 AM, Pierre Couderc wrote:
> How can I safely repair, knowing that I have the pg_dumpall of last
> night, but many dbs have changed today... ?
>
If pg_dumpall is your only backup mechanism then you've lost all changes
after the dump was taken.
I have broken my postgres database by typing :
psql How can I safely repair, knowing that I have the pg_dumpall of last
night, but many dbs have changed today... ?
Thanks in advance
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your