From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why is time with timezone 12 bytes? |
Date: | 2010-09-23 17:53:55 |
Message-ID: | 201009231753.o8NHrtM24366@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Thu, Sep 23, 2010 at 1:29 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> Josh Berkus wrote:
> >>> It would be a good project to add to the list of "easy TODOs to get
> >>> started with."
>
> >> Except for the pg_upgrade issue.
>
> > Which is a big "except".
>
> Yeah. That constraint is what leads me to think that the return on
> effort is just not worth it. Maybe we should file this in the category
> of "things to look at next time we break on-disk compatibility".
Yes, I would like to see such a category on the TODO list. Should I do
it?
FYI, I am please at the lack of serious problems with pg_upgrade.
People are obviously using it because the are filing bug reports, but
none of them are serious, and relate to pilot error or odd
configurations.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2010-09-23 18:06:52 | Re: security label support, revised |
Previous Message | Tom Lane | 2010-09-23 17:46:44 | Re: Why is time with timezone 12 bytes? |