| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | pgsql(at)mohawksoft(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Kouber Saparev <postgresql(at)saparev(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Help me recovering data |
| Date: | 2005-02-16 17:02:44 |
| Message-ID: | 20050216085819.W49236@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 16 Feb 2005, Joshua D. Drake wrote:
>
> >Do you have a useful suggestion about how to fix it? "Stop working" is
> >handwaving and merely basically saying, "one of you people should do
> >something about this" is not a solution to the problem, it's not even an
> >approach towards a solution to the problem.
> >
> >
> I believe that the ability for PostgreSQL to stop accepting
> queries and to log to the file or STDERR why it stopped working
> and how to resolve it is appropriate.
Right, but since the how to resolve it currently involves executing a
query, simply stopping dead won't allow you to resolve it. Also, if we
stop at the exact wraparound point, can we run into problems actually
trying to do the vacuum if that's still the resolution technique? If so,
how far in advance of wraparound must we stop to guarantee it will
succeed? It's not rocket science, but figuring such things out is part of
actually making a workable solution.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql | 2005-02-16 17:16:38 | Re: Help me recovering data |
| Previous Message | Joshua D. Drake | 2005-02-16 16:43:49 | Re: Help me recovering data |