On Wed, Sep 7, 2011 at 4:00 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvhe...@commandprompt.com> writes: >> Excerpts from Robert Haas's message of mar sep 06 19:57:07 -0300 2011: >>> TBH, I'm very unclear what could cause the postmaster to go belly-up >>> copying a bounded amount of data out of shared memory for logging >>> purposes only. It's surely possible to make the code safe against any >>> sequence of bytes that might be found there. > >> A mishandled encoding conversion could be problematic, so that needs to >> be carefully considered (perhaps just shut off unconditionally). > > That, and the question of exactly what makes the amount bounded, and
The fact that it's a fixed-size chunk of shmem. We won't copy more bytes than the size of the buffer. -- 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
