Magnus Hagander wrote: > Alvaro Herrera wrote: > > Andrew Chernow wrote: > > > Tom Lane wrote: > > >> Silently not locking is surely > > >> not very safe. > > >> > > > > > > Here is the dump code version of the patch. If anyone wants the > > > return value idea, let me know. > > > > So is this a patch we want applied? > > Please see my other thread about libpq thread-locking which should be > finished before this one, after which this patch will change. So no, > this is not the version to be applied.
Hmm, AFAICT on that other thread you state > I'm leaning towards going with the simpler one, which is the patch > from Andrew that crashes on out of memory. which would seem to mean this patch? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
