On Mon, Jan 23, 2012 at 8:11 AM, Robert Haas <robertmh...@gmail.com> wrote: > On Mon, Jan 23, 2012 at 5:29 AM, Fujii Masao <masao.fu...@gmail.com> wrote: >> If many people think the patch is not acceptable without such a safeguard, >> I will do that right now. > > That's my view. I think we ought to resolve this issue before commit, > especially since it seems unclear that we know how to fix it.
Actually, never mind. On reading this more carefully, I'm not too concerned about the possibility of people breaking it with pg_lesslog or similar. But it should be solid if you use only the functionality built into core. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
