On 6/17/25 10:30, Marcin Gozdalik wrote:
Around 100 DBs, ranging from 1TB to 50TB.
Initial testing showed that it takes 1.5h to dump the DB and 3h to
restore it for a DB of around 3TB.
Just recreating the indexes takes around 30 minutes on the same DBs.
I understand that pg_dump/pg_restore is
On Wed, Jun 11, 2025 at 7:36 PM Hayato Kuroda (Fujitsu)
wrote:
>
> Dear Max,
>
> > We have rewritten as many of our transactions as possible to avoid using
> > temporary tables, and so far, that seems to have resolved the problem.
>
> Good to know. We try to fix as soon as possible.
>
I pushed th
On 6/17/25 09:20, Marcin Gozdalik wrote:
Hi
I am using PostgreSQL 17 and would like to take advantage of performance
and stability across OS updates of builtin C.UTF-8 locale.
I have a cluster with a DB created with en_US.UTF-8 libc locale. I would
like to migrate the DB to C.UTF-8. Ideally th
Hi
I am using PostgreSQL 17 and would like to take advantage of performance
and stability across OS updates of builtin C.UTF-8 locale.
I have a cluster with a DB created with en_US.UTF-8 libc locale. I would
like to migrate the DB to C.UTF-8. Ideally there'd be an "ALTER DATABASE
... SET LOCALE ..
For the record, I haven't seen this deadlock again. I guess it was a bug
on the master branch that got fixed, because I've been testing later
versions a few times.
Dimitris
On Fri, 4 Apr 2025, Dimitrios Apostolou wrote:
On Wed, 2 Apr 2025, Dimitrios Apostolou wrote:
Hello list.
My dat
Thanks!
On Sun, Jun 15, 2025 at 10:11 PM Tom Lane wrote:
> Phillip Diffley writes:
> > Is there a reliable way to determine if an identifier has already been
> > escaped, or alternatively is there a function that will stably escape an
> > identifier such that the identifier will not change if t
