| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MaxOffsetNumber for Table AMs |
| Date: | 2021-05-05 17:56:56 |
| Message-ID: | 75e094cdd9b1be5bae0ac1fca166fb882734c920.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2021-05-05 at 10:48 -0700, Peter Geoghegan wrote:
> What we have right now has little chance of failing. It also has
> little chance of succeeding (except for something like zheap, which
> can presumably get by with the heapam's idea of TID).
What has little chance of succeeding? Table AMs?
And why isn't columnar an example of someting that can "get by with
heapam's idea of TID"? I mean, it's not a perfect fit, but my primary
complaint this whole thread is that it's undefined, not that it's
completely unworkable.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-05-05 17:58:49 | Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |
| Previous Message | Robert Haas | 2021-05-05 17:56:47 | Re: MaxOffsetNumber for Table AMs |