From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Marko Kreen" <markokr(at)gmail(dot)com> |
Cc: | "Chris Browne" <cbbrowne(at)acm(dot)org>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [RFC] extended txid docs |
Date: | 2007-10-17 17:36:43 |
Message-ID: | 8288.1192642603@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Marko Kreen" <markokr(at)gmail(dot)com> writes:
> Thanks. Here is a version with your changes applied, plus
> minor code cleanup and example output.
I can't really see the reasoning for putting this into the PG
documentation. It's tremendously complicated and doesn't seem like
something very many people would want to read about. In any case
it seems rather out of place where it is --- we don't have large
code examples elsewhere in func.sgml.
It almost looks like something that should be turned into a pgfoundry
or contrib module.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-10-17 17:57:51 | Deprecating heap_formtuple/heap_modifytuple/heap_deformtuple |
Previous Message | Heikki Linnakangas | 2007-10-17 17:36:32 | Re: Why copy_relation_data only use walwhenWALarchivingis enabled |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacky Leng | 2007-10-18 01:27:49 | Re: Why copy_relation_data only use wal whenWALarchivingis enabled |
Previous Message | Heikki Linnakangas | 2007-10-17 17:36:32 | Re: Why copy_relation_data only use walwhenWALarchivingis enabled |