Re: collations in shared catalogs? - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: collations in shared catalogs?
Date
Msg-id 8f109522612e93d8dfba936d82e51423@biglumber.com
Whole thread Raw
In response to Re: collations in shared catalogs?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> It's maybe not absolutely strictly necessary. In fact in earlier
> versions of the patch it was name. But replication solutions like bdr,
> slony, whatever will have to store a bunch of values identifying a node
> in there. And that's much easier if you're not constrained by 63 chars.

That's silly. We (third-party tools) already have to work around lots 
of things constrained by namedatalen.

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201505182138
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlValBYACgkQvJuQZxSWSsiODwCfRDTNsEHKsp7rbK24lT4lApwa
X1sAn0QL33wJyn/AWT2aLL9u+Ybt+aNb
=VjvO
-----END PGP SIGNATURE-----





pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: collations in shared catalogs?
Next
From: Noah Misch
Date:
Subject: Re: a few thoughts on the schedule