From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Wiki Page Draft for upcoming release |
Date: | 2014-03-18 19:28:53 |
Message-ID: | CAM-w4HO5CkXDOr-ajK77bA0FbMM_EqhUOnP2kZEmt=XTn_9xjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 18, 2014 at 7:05 PM, Greg Stark <stark(at)mit(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2014-03-18 19:29:09 | Re: plpgsql.warn_shadow |
Previous Message | Pavel Stehule | 2014-03-18 19:15:19 | Re: plpgsql.warn_shadow |