Alvaro Herrera writes:
> On 2022-Aug-30, Matheus Martin wrote:
>> Good idea on using an actual prepared statement but unfortunately it didn't
>> produce any different result.
> I should have also mentioned to try the EXPLAIN EXECUTE six times and
> see if the last one produces a different plan.
Hi Guillaume/team,
I set archive_mode = always in master and standby.
Archival to standby WAL directory completed when
* standby server was restarted
* pg_stop_backup was executed in master
But archival hangs when pg_stop_backup is executed in standby.
Could someone help to get this work
On 2022-Aug-30, Matheus Martin wrote:
> Good idea on using an actual prepared statement but unfortunately it didn't
> produce any different result.
I should have also mentioned to try the EXPLAIN EXECUTE six times and
see if the last one produces a different plan. That's when it switches
from pl
The threshold for `auto_explain` was changed to 500 ms and explain plans
are still not being logged.
On Tue, 30 Aug 2022 at 13:30, Julien Rouhaud wrote:
> Hi,
>
> On Tue, Aug 30, 2022 at 01:16:43PM +0200, Alvaro Herrera wrote:
> > On 2022-Aug-30, Matheus Martin wrote:
> >
> > > Our Postgres rece
Good idea on using an actual prepared statement but unfortunately it didn't
produce any different result.
Could you please elaborate a bit on your advice concerning
ExecutorEnd/PortalCleanup? I am afraid it doesn't mean much to me.
On Tue, 30 Aug 2022 at 12:16, Alvaro Herrera
wrote:
> On 2022-A
Hi,
On Tue, Aug 30, 2022 at 01:16:43PM +0200, Alvaro Herrera wrote:
> On 2022-Aug-30, Matheus Martin wrote:
>
> > Our Postgres recently started reporting considerably different
> > execution times for the same query. When executed from our JDBC
> > application the Postgres logs report an average
On 2022-Aug-30, Matheus Martin wrote:
> Our Postgres recently started reporting considerably different
> execution times for the same query. When executed from our JDBC
> application the Postgres logs report an average execution time of 1500
> ms but when the query is manually executed through `ps
Our Postgres recently started reporting considerably different
execution times for the same query. When executed from our JDBC
application the Postgres logs report an average execution time of 1500
ms but when the query is manually executed through `psql` it doesn't
take longer than 50 ms.
With a
Hi Igor,
On Fri, 26 Aug 2022 at 13:43, Lahnov, Igor wrote:
> I can't answer your question. What do you think, the recovery from the
> archive should work in this case?
>
> 1. the partial file should not be restored at all cases
>
> 2. the partial file should recover as a partial and replace the
