PG 17 has integrated zstd compression, while --format=directory lets you do
multi-threaded dumps. That's much faster than a single-threaded pg_dump
into a multi-threaded compression program.
(If for _Reasons_ you require a single-file backup, then tar the directory
of compressed files using the -
Sorry for not including the full command - yes , its piping to a
compression command :
| lbzip2 -n --best >
I think we found the issue! I'll do further testing and see how it goes !
On Wed, 17 Sept 2025 at 11:02, Ron Johnson wrote:
> So, piping or redirecting to a file? If so, then that
On 9/16/25 17:54, R Wahyudi wrote:
pg_dump was done using the following command :
pg_dump -Fc -Z 0 -h -U -w -d
What do you do with the output?
--
Adrian Klaver
adrian.kla...@aklaver.com
So, piping or redirecting to a file? If so, then that's the problem.
pg_dump directly to a file puts file offsets in the TOC.
This how I do custom dumps:
cd $BackupDir
pg_dump -Fc --compress=zstd:long -v -d${db} -f ${db}.dump 2> ${db}.log
On Tue, Sep 16, 2025 at 8:54 PM R Wahyudi wrote:
> pg
On 9/16/25 15:25, R Wahyudi wrote:
I'm trying to troubleshoot the slowness issue with pg_restore and
stumbled across a recent post about pg_restore scanning the whole file :
> "scanning happens in a very inefficient way, with many seek calls and
small block reads. Try strace to see them. Th
On Tue, Sep 16, 2025 at 1:55 PM Adrian Klaver
wrote:
> On 9/16/25 08:14, Adrian Klaver wrote:
> > On 9/16/25 02:09, Daniel Westermann (DWE) wrote:
> >> Hi,
> >>
> >> Is this table outdated?:
> >> https://www.postgresql.org/download/windows/
> >>
> >> ... or is the EDB installer indeed not support
On 9/16/25 08:14, Adrian Klaver wrote:
On 9/16/25 02:09, Daniel Westermann (DWE) wrote:
Hi,
Is this table outdated?:
https://www.postgresql.org/download/windows/
... or is the EDB installer indeed not supported on Windows Server 2025?
From the link:
"The installers are tested by EDB on the
On 9/16/25 04:01, Jaime Casanova wrote:
Hi,
I have a database with UTF8 encoding. This database seems to be
receiving data in WIN1252 encoding from some client.
I even see this:
db=# select * from pg_db_role_setting ;
setdatabase | setrole | setconfig
-
On Tue, Sep 16, 2025 at 7:25 AM Vladlen Popolitov <
v.popoli...@postgrespro.ru> wrote:
> Checksum calculation takes ~0.5% of query time, it is not bottleneck
> in PostgreSQL.
I consider checksums=on to be a mandatory setting. Often, these types of
things are not bugs in postgres itself, but bug
Pawel Kudzia писал(а) 2025-09-14 15:47:
On Sun, Sep 14, 2025 at 12:35 PM Laurenz Albe
wrote:
gdb stack trace for that process:
#0 0x55cb571ef444 in hash_search_with_hash_value ()
#1 0x55cb5706217a in BufTableLookup ()
Hi,
Probably, it does not hang in function hash_search_with
Hi,
I have a database with UTF8 encoding. This database seems to be
receiving data in WIN1252 encoding from some client.
I even see this:
db=# select * from pg_db_role_setting ;
setdatabase | setrole | setconfig
-+--+---
Hi,
Is this table outdated?:
https://www.postgresql.org/download/windows/
... or is the EDB installer indeed not supported on Windows Server 2025?
Many thanks in advance
Daniel
12 matches
Mail list logo
