Re: Wiki Page Draft for upcoming release - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Wiki Page Draft for upcoming release
Date
Msg-id CAM-w4HO5CkXDOr-ajK77bA0FbMM_EqhUOnP2kZEmt=XTn_9xjA@mail.gmail.com
Whole thread Raw
In response to Re: Wiki Page Draft for upcoming release  (Greg Stark <stark@mit.edu>)
Responses Re: Wiki Page Draft for upcoming release  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Tue, Mar 18, 2014 at 7:05 PM, Greg Stark <stark@mit.edu> wrote:
> I'll do a first pass now.

I fixed the "Causes" section. I haven't touched the other sections
which are pretty reasonable. It would be nice to have more suggestions
for what people should do other than dump/restore.

It would be nice to be able to tell people that if they vacuum, then
reindex and check all their foreign key constraints then they should
be ok. I think that's almost true except I'm not sure how to tell that
they've waited long enough before vacuuming and I'm not 100% sure
it'll fix the problem. (Also they could have lost a row which has
since had all all it's referencing rows deleted. The database won't be
able to help them find that.)

-- 
greg



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: plpgsql.warn_shadow
Next
From: Andres Freund
Date:
Subject: Re: Wiki Page Draft for upcoming release