From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Stefan Schwarzer" <stefan(dot)schwarzer(at)grid(dot)unep(dot)ch>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
Subject: | Re: Forgot to dump old data before re-installing machine |
Date: | 2008-01-18 16:47:39 |
Message-ID: | 937d27e10801180847u7573276as57e824d1d6827e61@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
On 18/01/2008, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Am Freitag, 18. Januar 2008 schrieb Dave Page:
> > It got figured out when someone who knew what they were looking for
> > peeked at the byte ordering in a file which for all we knew at the
> > time might have been damaged anyway
>
> What might be better is if we had an explicit endianness mark in pg_control
> rather than relying on users discovering endianness problems by seemingly
> corrupted version numbers.
Seems reasonable to me. Obviously I'd mixed up the datetime/time_t
issues I ran into previously, so having the configure options as well
would be largely useless.
That said, is zlib used by toast or do we have some other code for
that? If it is used for that, do we record it's presence or absence in
pg_control?
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-01-18 16:59:06 | Re: Forgot to dump old data before re-installing machine |
Previous Message | Jan de Visser | 2008-01-18 16:44:35 | transactionid lock type? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-01-18 16:59:06 | Re: Forgot to dump old data before re-installing machine |
Previous Message | Peter Eisentraut | 2008-01-18 16:37:32 | Re: Forgot to dump old data before re-installing machine |