From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: Access method extendability |
Date: | 2016-03-30 14:31:56 |
Message-ID: | 56FBE35C.4000601@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> as we discussed recently [1] you should avoid leaving "holes" with
> uninitialized data in structures. Please fix this or provide a comment
> that describes why things are done here the way they are done.
> [1] http://www.postgresql.org/message-id/56EFF347.20500@anastigmatix.net
That discussion is about SQL-level types which could be stored on disk, not
about in-memory structs
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2016-03-30 14:43:36 | Re: Support for N synchronous standby servers - take 2 |
Previous Message | Tom Lane | 2016-03-30 14:21:29 | Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping. |