From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: check database integrity |
Date: | 2014-07-20 14:02:42 |
Message-ID: | 20140720140242.GH15455@crankycanuck.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jul 20, 2014 at 02:57:20PM +0200, Torsten Förtsch wrote:
> I ran this query in a separate transaction. The memory was freed only
> when the backend process exited.
>
> Is there a way to work around this memory leak?
Why do you think it's a memory leak. You asked for the full dataset;
you need to have the memory to allocate for it. At least, that's what
I'd expect.
> expensive locks. Then I could also use it in production. But currently I
> need it only to verify a backup.
If you need to verify a backup, why isn't pg_dump acceptable? Or is
it that you are somehow trying to prove that what you have on the
target (backup) machine is in fact production-ready? I guess I don't
really understand what you are trying to do.
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-07-20 14:30:22 | Re: serious issue with age(relfrozenxid)::int. |
Previous Message | Torsten Förtsch | 2014-07-20 12:57:20 | check database integrity |