On Wed, Aug 2, 2017 at 11:49 AM, Tom Lane wrote:
> Edmundo Robles writes:
>> I mean, to verify the integrity of backup i do:
>> gunzip -c backup_yesterday.gz | pg_restore -d my_database && echo
>> "backup_yesterday is OK"
>
>> but my_database's
On 02/08/17, Steve Atkins (st...@blighty.com) wrote:
> > On Aug 2, 2017, at 9:02 AM, Edmundo Robles wrote:
> >
> > I mean, to verify the integrity of backup i do:
> >
> > gunzip -c backup_yesterday.gz | pg_restore -d my_database && echo
> > "backup_yesterday is OK"
>
On Wed, Aug 2, 2017 at 7:10 PM, Edmundo Robles wrote:
>
> I imagine pg_restore can execute the instructions on dump but don't
> write on disk. just like David said: "tell me what is going to happen but
> don't actually do it"
IIRC pg_restore does not execute SQL
On Wed, Aug 02, 2017 at 12:10:37PM -0500, Edmundo Robles wrote:
> I imagine pg_restore can execute the instructions on dump but don't
> write on disk. just like David said: "tell me what is going to happen
> but don't actually do it"
In fact, this already exists:
pg_restore
On Wed, Aug 2, 2017 at 10:10 AM, Edmundo Robles
wrote:
> I imagine pg_restore can execute the instructions on dump but don't
> write on disk. just like David said: "tell me what is going to happen
> but don't actually do it"
>
You may wish to respond to the actual
I imagine pg_restore can execute the instructions on dump but don't
write on disk. just like David said: "tell me what is going to happen
but don't actually do it"
Regards.
On Wed, Aug 2, 2017 at 11:49 AM, Tom Lane wrote:
> Edmundo Robles
> On Aug 2, 2017, at 9:02 AM, Edmundo Robles wrote:
>
> I mean, to verify the integrity of backup i do:
>
> gunzip -c backup_yesterday.gz | pg_restore -d my_database && echo
> "backup_yesterday is OK"
>
> but my_database's size, uncompresed, is too big more than
Edmundo Robles writes:
> I mean, to verify the integrity of backup i do:
> gunzip -c backup_yesterday.gz | pg_restore -d my_database && echo
> "backup_yesterday is OK"
> but my_database's size, uncompresed, is too big more than 15G and
> sometimes i have no
On Wed, Aug 2, 2017 at 9:02 AM, Edmundo Robles wrote:
> Will be great to have a dry run option, because the time to verify
> reduces a lot and will save space on disk, because just execute with no
> write to disk.
>
"Dry run", the way I understand it, can be
I mean, to verify the integrity of backup i do:
gunzip -c backup_yesterday.gz | pg_restore -d my_database && echo
"backup_yesterday is OK"
but my_database's size, uncompresed, is too big more than 15G and
sometimes i have no space to restore it, so always i must declutter my
disk
10 matches
Mail list logo