| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jose Luis Tallon <jltallon(at)adv-solutions(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump dump catalog ACLs |
| Date: | 2016-03-30 18:01:33 |
| Message-ID: | CA+TgmoYRFjN1J=g8zs39rTdtXoG39mcxrw-aZRqOZFEdKD2w6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 30, 2016 at 1:35 PM, Jose Luis Tallon
<jltallon(at)adv-solutions(dot)net> wrote:
> DESIGN/DOCUMENTATION
> * int4 for the "objsubid" field? and int2 would surely suffice, given that we only allow up to 1600 columns ... if it's a matter of alignment, it would be interesting to say so somewhere (code comments, maybe?)
There is a lot of existing precedent for objsubid being int4, and
basically no advantage to making it int2.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Pedersen | 2016-03-30 18:08:05 | Re: Speedup twophase transactions |
| Previous Message | Tom Lane | 2016-03-30 17:55:02 | Re: [COMMITTERS] pgsql: Introduce SP-GiST operator class over box. |