| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Chapman Flack <chap(at)anastigmatix(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: dfmgr additional ABI version fields |
| Date: | 2021-10-13 16:50:38 |
| Message-ID: | CA+Tgmoa6hTrDBKE0MF+66RztePgU185Ua_ZcGZCFzDP4iKXPPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 12, 2021 at 8:13 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> So here is a patch. This does what I had in mind as a use case.
> Obviously, the naming and wording can be tuned. Input from other
> vendors is welcome.
I'm not a different vendor, but I do work on different code than you
do, and I like this. Advanced Server accidentally dodges this problem
at present by shipping with a different FUNC_MAX_ARGS value, but this
is much cleaner.
Would it be reasonable to consider something similar for the control
file, for the benefit of distributions that are not the same on disk?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-10-13 16:54:26 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Robert Haas | 2021-10-13 16:46:27 | Re: pg14 psql broke \d datname.nspname.relname |