Re: Is there a drawback when changing NAMEDATALEN to 64? - Mailing list pgsql-general

From Gregory Wood
Subject Re: Is there a drawback when changing NAMEDATALEN to 64?
Date
Msg-id 007f01c19ae0$a95c8810$7889ffcc@comstock.com
Whole thread Raw
In response to Is there a drawback when changing NAMEDATALEN to 64?  (Frank Joerdens <frank@joerdens.de>)
List pgsql-general
> BTW, there is at least a small potential for breaking applications with
> this change: NAMEDATALEN is part of the exported libpq ABI, because it
> affects the representation of PGnotify structures.  When and if we do
> change the standard setting, I'm inclined to reverse the order of the
> fields in PGnotify, so that accesses to be_pid don't depend on
> NAMEDATALEN.

Would this also not break the method used to create SERIAL sequence names? I
know that I would have to fix a method I've written to calculate the
sequence name for a SERIAL field, and I suspect a few others have as well.
I'd be more than happy to fix it for a longer name though...

Greg


pgsql-general by date:

Previous
From: Sam Tregar
Date:
Subject: ANN: Bricolage Content-Management and Publishing System 1.2.0
Next
From: will trillich
Date:
Subject: Re: caching subtotals: update vs sum -- aaugh!