Fix applied.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
The breakage will come when we lengthen NAMEDATALEN, which I plan to
tackle for 7.3. We will need to re-order the NOTIFY structure and put
Here is a patch that implements Tom's suggestion of mallocing the
relation name string as part of PQnotify and not depending on
NAMEDATALEN. Nice trick.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
The
Neil Conway wrote:
On Wed, Mar 20, 2002 at 04:10:14PM -0500, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
The breakage will come when we lengthen NAMEDATALEN, which I plan to
tackle for 7.3. We will need to re-order the NOTIFY structure and put
the NAMEDATALEN string at
[EMAIL PROTECTED] (Neil Conway) writes:
If we're going to change the structure anyway, let's fix it to be
independent of NAMEDATALEN.
Sounds good. If we're making other backwards-incompatible changes to
pgNotify, one thing that bugs me about the API is the use of relname
to refer to name of
On Thu, 2002-03-21 at 00:16, Tom Lane wrote:
[EMAIL PROTECTED] (Neil Conway) writes:
If we're going to change the structure anyway, let's fix it to be
independent of NAMEDATALEN.
Sounds good. If we're making other backwards-incompatible changes to
pgNotify, one thing that bugs me about
Bruce Momjian [EMAIL PROTECTED] writes:
The breakage will come when we lengthen NAMEDATALEN, which I plan to
tackle for 7.3. We will need to re-order the NOTIFY structure and put
the NAMEDATALEN string at the end of the struct so differing namedatalen
backend/clients will work. If you want
