| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add support for logging the current role |
| Date: | 2011-01-14 22:10:38 |
| Message-ID: | 4D30C9DE.7080302@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/14/2011 05:04 PM, Aidan Van Dyk wrote:
> 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.
>
> If the 1st column is always the version, tools can easily know if
> they understand all the columns (and what order they are in) and it'
> easy to write a "conversion" that strips/re-aranges columns from a
> newer CVS dump to match an older one if you have tools that don't know
> about newer column layouts..
>
>
The whole point of having CSV logs is so you can load them into a
database table without needing preprocessing tools. So I'm not going to
be very receptive to changes that are predicated on using such tools.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-14 22:13:22 | Re: LOCK for non-tables |
| Previous Message | Tom Lane | 2011-01-14 22:08:08 | Re: Add support for logging the current role |