| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: Tarball builds in the new world order |
| Date: | 2024-04-29 12:39:57 |
| Message-ID: | 710f1828-0584-4312-a509-2b32967298c1@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26.04.24 21:24, Tom Lane wrote:
> Concretely, I'm proposing the attached. Peter didn't like
> PG_COMMIT_HASH, so I have PG_COMMIT_REFSPEC below, but I'm not
> wedded to that if a better name is proposed.
Um, "refspec" leads me here
<https://git-scm.com/book/en/v2/Git-Internals-The-Refspec>, which seems
like the wrong concept. I think the more correct concept is "revision"
(https://git-scm.com/docs/gitrevisions), so something like PG_GIT_REVISION?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2024-04-29 12:39:58 | Re: using extended statistics to improve join estimates |
| Previous Message | Robert Haas | 2024-04-29 12:38:22 | Re: Direct SSL connection with ALPN and HBA rules |