Having contributed to the need for pg_dump/initdb/restore when
upgrading from 7.2 to 7.3, I plan to submit a patch which *could* make
future transitions easier.
bufpage.h:
typedef struct PageHeaderData
{
...
uint32 pd_type;/* kind and version */
...
}
#define
Manfred Koizar [EMAIL PROTECTED] writes:
Having contributed to the need for pg_dump/initdb/restore when
upgrading from 7.2 to 7.3, I plan to submit a patch which *could* make
future transitions easier.
We do need a page version code but I do not want to waste 4 bytes per
page on it.
I was
I didn't follow the index part completely, but will heap and index pages
have the version info in the same offset? Will there be a way to
easily identify an index page vs. a heap page.
---
Tom Lane wrote:
Manfred Koizar
Bruce Momjian [EMAIL PROTECTED] writes:
I didn't follow the index part completely, but will heap and index pages
have the version info in the same offset?
Sure, low byte of pd_pagesize.
Will there be a way to easily identify an index page vs. a heap page.
There already is: heap pages have
As the upcoming release is breaking compatibility anyway: what do you
think about placing a magic number and some format version info into
the page header?
One 32-bit-number per page should be enough to encode page type and
version. We have just to decide, how we want it:
a) combine page type
Manfred Koizar wrote:
As the upcoming release is breaking compatibility anyway: what do you
think about placing a magic number and some format version info into
the page header?
One 32-bit-number per page should be enough to encode page type and
version. We have just to decide, how we
