| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marko Kreen" <markokr(at)gmail(dot)com> |
| Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Jan Wieck" <JanWieck(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Skytools committed without hackers discussion/review |
| Date: | 2007-10-10 19:49:22 |
| Message-ID: | 22846.1192045762@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
"Marko Kreen" <markokr(at)gmail(dot)com> writes:
> On 10/10/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> * Why is txid_current_snapshot() excluding subtransaction XIDs? That
>> might be all right for the current uses in Slony/Skytools, but it seems
>> darn close to a bug for any other use.
> ...
> But I agree, supporting subtransactions makes the API more
> universal. And it wouldn't break Slony/PgQ current usage.
After looking at this more closely, I think txid_current_snapshot is
okay as is, but is_visible_txid is probably buggy: the latter should be
folding subtransaction IDs to top-transaction IDs, no? If not, why not?
I hope the answer is "no" because otherwise the code will be at huge risk
from truncation of pg_subtrans, but it's not apparent why this behavior
is okay.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2007-10-10 19:59:26 | Re: Skytools committed without hackers discussion/review |
| Previous Message | User Rlucas | 2007-10-10 19:43:11 | aupg - aupg_src: Added a rudimentary testing infrastructure. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2007-10-10 19:51:14 | Re: Timezone database changes |
| Previous Message | andy | 2007-10-10 19:26:38 | Re: full text search in 8.3 |