Aidan Van Dyk <ai...@highrise.ca> writes:
> If there is going to be any change, how about using fixed columns (an
> possibly allowing them to be empty for stuff that's expensive to
> create/write), but adding a 1st column that contains a "version"
> identifyer. And to make it easy, maybe the PG major version as the
> version value.
Seems like that just adds even more overhead, without really solving any
of the problems we're concerned about. Code consuming the CSV log would
still need a-priori knowledge of what columns to expect.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
