Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes: > Possible fixes:
> a) Ignore, hoping GCC will change before final release. (unlikely at > this point) > b) Add compiler option to disable this particular warning, worry about > it later. (Might be an option for backpatching.) > c) Expand the target buffer sizes until the warning goes away. (Sample > patch attached.) > d) Replace most of the problematic code with psprintf() and dynamically > sized buffers. +1 for (c) as you have it. Later we might think about selectively doing (d), but it seems like more work for probably not much benefit. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers