Hi Laurenz,
Thank you for your answer
>> For some projects we need a fast manual switchover to address Near Zero
>> downtime maintenance
I forgot to say that application would not be stopped during maintenance…
>There is no need for synchronous replication; you cannot lose data with a
>switcho
> > what could we expect (in term of downtime in both worlds) ?
>
> Usually seconds, so plan for ten minutes.
*lol*
So true ...
On Mon, Sep 8, 2025 at 12:37 PM Klaus Darilion
wrote:
>
>
> *From:* Ron Johnson
> *Sent:* Monday, September 8, 2025 6:10 PM
> *To:* pgsql-general@lists.postgresql.org
> *Subject:* Re: Fast switchover
>
>
>
> On Mon, Sep 8, 2025 at 11:03 AM legrand legrand <
> legrand_legr...@hotmail.com> wrote:
From: Ron Johnson
Sent: Monday, September 8, 2025 6:10 PM
To: pgsql-general@lists.postgresql.org
Subject: Re: Fast switchover
On Mon, Sep 8, 2025 at 11:03 AM legrand legrand
mailto:legrand_legr...@hotmail.com>> wrote:
Hello all the readers,
For some projects we need a fast manual switchover to
Looking at the postgresql code, the LW lock SerializableFinishedList appears to
be acquired and then released, usually in the duration of a call to a
procedure. Base on that (admittedly maybe faulty) view of the code, I am
surprised to see the lock held open for over and hour and a half.
From:
Hello,
Thanks for your response.
# Currently, I have a function text and a function array with the same body but
a distinct type return .
-> Example with the array of text function :
SELECT public.calfxi3s_all_elements_text_array(12345678, '2025-01-01 00:00') ;
calfxi3s_all_elements_text_arr
Hello all the readers,
For some projects we need a fast manual switchover to address Near Zero
downtime maintenance
(not speaking here about automated failover like those provided by HA tools,
but just planned, controlled operations)
Database Physical replication switchover itself:
- initial r
On Mon, Sep 8, 2025 at 5:37 AM PALAYRET Jacques
wrote:
> I can manage with this method, but it shoud be better with a include
> directive.
>
Even if we had includes, I would strongly advise "this method" which seems
pretty clean and maintainable. What is the issue with SQL functions that
call a
Thanks Justin,
We’ll try the lock_timeout configuration. We originally discarded it’s use
because statement_timeout seemed to cover it according to the documentation.
Attached are some of information from the pg_locks and pg_stat_activity we are
logging when this crisis happens.
The stored pro
