On Fri, Dec 22, 2023 at 10:55:24AM +0200, Kouber Saparev wrote:
> The table for this file node is not even included in any of the
> publications we have. I've found a similar issue described [1] before, so I
> was wondering whether this patch is applied? Our subscriber database is
> PostgreSQL 16.1
On 12/23/23 10:05, Johnathan Tiamoh wrote:
More information needed:
1) Exact Postgres version e.g 14.x
Postgresql Version 14. 10
2) Is it community version or fork?
Community version
3) What was the command you used to start the cluster?
systemctl start postgresql-14
4) Do you have replica
More information needed:
1) Exact Postgres version e.g 14.x
Postgresql Version 14. 10
2) Is it community version or fork?
Community version
3) What was the command you used to start the cluster?
systemctl start postgresql-14
4) Do you have replication/WAL archiving set up?
Yes.
Just to ad
On 12/22/23 22:48, Johnathan Tiamoh wrote:
Hello,
I am able to start postgresql because of the below error. Please is
there any help
User
You
FATAL: xlog flush request 4392/164662F8 is not satisfied --- flushed
only to 4392/F58
UserYouFATAL: xlog flush request 4392/164662F8 is not s
On 12/23/23 08:12, Wilma Wantren wrote:
Thank you!
I had already feared that such a variable does not exist (because I had not
found it). I think that's a pity, because I suspect that in at least 90% of the
cases where a function needs a search_path, this variable would be the value of
the sea
Thank you!
I had already feared that such a variable does not exist (because I had not
found it). I think that's a pity, because I suspect that in at least 90% of the
cases where a function needs a search_path, this variable would be the value of
the search_path, so that in 90% of the cases no c
