| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | niraj nandane <niraj(dot)nandane(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: Regarding backpatching to v14 |
| Date: | 2023-02-27 23:40:51 |
| Message-ID: | Y/0/gy3HnwKcWVpR@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 27, 2023 at 04:02:42PM +0530, niraj nandane wrote:
> https://www.postgresql.org/message-id/flat/9f568c97-87fe-a716-bd39-65299b8a60f4%40iki.fi
>
> Is it possible to backpatch in PG 14?
> We use this and using PG 14.4 as of now.
> ref link:
> https://dba.stackexchange.com/questions/320997/pg-rewind-succeed-but-postgresql-showing-error-when-trying-to-make-standby-with/324006#324006
I am adding Heikki in CC. It seems to me that there is an argument
for a backpatch, here.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-02-28 03:12:38 | BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set |
| Previous Message | Tom Lane | 2023-02-27 22:54:23 | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |