Martijn van Oosterhout wrote: > On Fri, Jun 08, 2007 at 08:31:54AM -0400, Andrew Dunstan wrote: > > The situation with this patch is that I now have it in a state where I > > think it could be applied, but there is one blocker, namely that we do > > not have a way of preventing the interleaving of log messages from > > different backends, which leads to garbled logs. This is an existing > > issue about which we have had complaints, but it becomes critical for a > > facility the whole purpose of which is to provide logs in a format > > guaranteed to work with our COPY command. > > The whole semantics of PIPEBUF should prevent garbling, as long as each > write is a complete set of lines and no more than PIPEBUF bytes long. > Have we determined the actual cause of the garbling?
No, that's the main problem -- but it has been reported to happen on entries shorter than PIPE_BUF chars. -- Alvaro Herrera http://www.PlanetPostgreSQL.org/ "La persona que no quería pecar / estaba obligada a sentarse en duras y empinadas sillas / desprovistas, por cierto de blandos atenuantes" (Patricio Vogel) ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
