| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 32/64-bit transaction IDs? |
| Date: | 2003-03-21 06:12:39 |
| Message-ID: | 10431.1048227159@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> I need a guaranteed ordering of transaction IDs as they are queued for
> asyncronous replication. I'd use the 32-bit internal transaction ID from
> GetTransactionId(), but 32-bits will not suffice for the logic I'd like to
> use. A 64-bit ID would work well enough.
Uh ... your replication logic cannot ensure to reach closure within two
billion transactions? Something's pretty out of joint there.
> Further, I am uncertain those 32-bit transaction IDs represent a correctly
> ordered sequence of transactions.
XIDs are issued in transaction start order, not transaction commit
order. Dunno if that's what's concerning you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar<shridhar_daithankar@persistent.co.in> | 2003-03-21 06:13:29 | Re: [HACKERS] Extracting time from timestamp |
| Previous Message | Christopher Kings-Lynne | 2003-03-21 06:08:27 | Re: [HACKERS] Extracting time from timestamp |