| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix output of zero privileges in psql |
| Date: | 2023-10-16 21:51:39 |
| Message-ID: | cww6udzxvxorpznocvufq42mly3qyi3wcjx45nhlbj3wm6rjfc@36pzmsfodow5 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-10-16 17:56 +0200, Laurenz Albe write:
> David, how do you feel about this? I am wondering whether to set this patch
> "ready for committer" or not.
>
> There is Tom wondering upthread whether changing psql's behavior like that
> is too much of a compatibility break or not, but I guess it is alright to
> leave that final verdict to a committer.
What's the process for the CommitFest now since we settled on your
patch? This is my first time being involved in this, so still learning.
I'see that you've withdrawn your initial patch [1] but this thread is
still attached to my patch [2]. Should I edit my CF entry (or withdraw
it) and you reactivate yours?
[1] https://commitfest.postgresql.org/45/4603/
[2] https://commitfest.postgresql.org/45/4593/
--
Erik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2023-10-16 22:07:02 | Re: Patch: Improve Boolean Predicate JSON Path Docs |
| Previous Message | Timothy Nelson | 2023-10-16 21:39:49 | Re: Postgres Architecture |