Horton

Re: Sequence Access Method WIP

Petr Jelinek <petr@2ndquadrant.com>

View thread View on postgr.es
From: Petr Jelinek <petr@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>, Simon Riggs <simon@2ndquadrant.com>, Andres Freund <andres@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@2ndquadrant.com>
Date: 2015-02-18T01:59:32Z
Lists: pgsql-hackers 
On 17/02/15 23:11, Robert Haas wrote:
> On Sun, Feb 15, 2015 at 1:40 PM, Petr Jelinek <petr@2ndquadrant.com> wrote:
>> sending new version that is updated along the lines of what we discussed at
>> FOSDEM, which means:
>>
>> - back to single bytea amdata column (no custom columns)
>

Well, the main argument is still future possibility of moving into 
single table for storage. And when we discussed about it in person we 
agreed that there is not too big advantage in having separate columns 
since there need to be dump/restore state interfaces anyway so you can 
see the relevant state via those as we made the output more human 
readable (and the psql support reflects that).

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

Commits

  1. Add missing gss option to msvc config template