On publisher it shows me "terminating walsender process due to replication
timeout"
But the problem is that this message is occurring 3 or 4 times a day only.
It tries to send data, gets a timeout then shows the message. Then it waits
a long long long time to try again, I don´t know why.
wal_send
So, there is a way to call replication, to client restart connection and try
again ?
Because aparently it stays disconnected for hours to try again, gets that
timeout message and remains disconnected for hours again
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.htm
On 2021-04-07 10:35:55 -0600, Rob Sargent wrote:
> On Apr 7, 2021, at 10:17 AM, Ron wrote:
>
> On 4/5/21 9:37 PM, Rob Sargent wrote:
>
> It's a small thing, but UUIDs are absolutely not memorizable by
> humans; they have zero semantic value. Sequential numeric
>
From: Miles Elam
Sent: Tuesday, April 6, 2021 4:19 PM
Sadly, this is a cloud-managed database without direct access to 5432 from
outside the VPC and bastian instances are frowned upon by our security folks.
Guess I'm stuck with bisecting. Thanks for the confirmation.
It'd
Following up in case someone else runs into this problem. I changed the
function the CHECK statement called to raise a warning. Not perfect, but
noticeably better. I don't get the column that failed but I do get what bad
input gummed things up.
CREATE OR REPLACE FUNCTION po.confirm(p_val anyelemen
Hi guys,
We face "index contains unexpected zero page" problem in prd postgresql 11
environment
This url shows that need to backup database firstly, is it necessary?
https://cloudblue.freshdesk.com/support/solutions/articles/44001889599-error-index-tablename-contains-unexpected-zero-page
If "cre
