| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, 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:32:57 |
| Message-ID: | CA+TgmoaxuJPGWJY2pWikmnvwZ-W0QCGgoULdF8FhspT17o8UMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 5, 2021 at 1:13 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> "In core" shouldn't matter. In fact, if it's in core, stability of the
> APIs is much less important.
I don't know what to say here. I think it's unrealistic to believe
that a very new API that has only 1 in-core user is going to be fully
stable, or that we can know how it might evolve. I can understand why
you and probably other people want that, but if somebody figures out a
way to make some part of core significantly better and it requires
changing that API, they're going to change the API, not give up on the
idea.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isaac Morland | 2021-05-05 17:34:18 | Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |
| Previous Message | Chapman Flack | 2021-05-05 17:23:01 | Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |