| From: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martín Fernández <fmartin91(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Transaction Id Space, Freezing and Wraparound |
| Date: | 2018-12-09 00:47:10 |
| Message-ID: | fc177d37-878c-6a3b-bd7a-6e8e753681b8@ardentperf.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/20/18 13:00, Tom Lane wrote:
> If the stored XIDs were 64 bits wide, we'd not have to bother with all
> of this mess ... but adding another 64 bits to tuple headers would be
> a painful space cost, not to mention the storage compatibility issues.
People keep saying that. But didn't someone come up with a way to do
this by storing the top 32 bits just once somewhere in the block, rather
than adding 64 bits to every tuple? I can't remember if there was an
email thread.
Maybe some other drawbacks to that approach, but lets at least point out
adding 64 bits to the tuple header isn't the only way to accomplish this.
And the other thread about memory management... if I'm going to start
religious wars, might as well just start them all at once right? ;)
-J
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Lissner | 2018-12-09 07:26:46 | Errors with schema migration and logical replication — expected? |
| Previous Message | Andres Freund | 2018-12-08 23:38:18 | Re: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |