Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes: > If we don't fix that within the server, we will need to document that > caveat and every installation will need to work around that one way or > another. Maybe with some monitoring software and an automatic restart. Ugh. > > I wasn't really asking if it's possible to fix, I meant "Let's think > about *how* to fix that".
Did I mention my viewpoint on that already? http://archives.postgresql.org/pgsql-hackers/2009-07/msg00943.php It could well be I'm talking about things that have no relation at all to what is in the patch currently, and that make no sense for where we want the patch to go. But I'd like to know about that so that I'm not banging my head on the nearest wall each time the topic surfaces. Regards, -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
