dumping - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-06-10 10:35:00 | BUG #18952: pg_restore --help and document have strange description: Dump something (PG Bug reporting form)
dump or pg_dumpall. Usage: pg_restore [OPTION]... [FILE] (snip) --with-data dump the data
Mailing lists >> pgsql-bugs >> Thread
2025-06-08 15:21:40 | tlsv1 alert iso-8859-1 ca error on cert authentication (Andrus)
dump" -f "test.backup" -F c -h localhost -U postgres postgres Observed: > pg_dump: error
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-06-08 06:16:54 | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql (Lowell Hought)
dump file is about 20 GB, so not terribly large. I could attempt to dump
Mailing lists >> pgsql-bugs >> Thread
2025-05-24 08:09:56 | Re: BUG #18936: Trigger enable users to modify the tables which hedoesn't have privilege (Laurenz Albe)
dump. PostgreSQL takes great care that nothing can go wrong in these cases. Yours, Laurenz
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (4)
2025-05-15 22:03:11 | Re: BUG #18923: pg_dump 18beta1 fails to process complex table names (Corey Huinker)
This patch looks good to me, though I'm wondering if we should add a
Mailing lists >> pgsql-bugs >> Thread
2025-05-14 06:27:14 | BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform (PG Bug reporting form)
environments, dumps, or help isolate the patch if needed. Thanks, Robb Shecter [robb@public.law](mailto:robb@public.law)
Mailing lists >> pgsql-bugs >> Thread
2025-05-05 11:00:12 | BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may (PG Bug reporting form)
dump, pg_verifybackup, and pg_rewind, which use the frontend version of palloc (from libpgcommon
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (5)
2025-04-29 17:44:16 | Re: pg_restore error with partitioned table having exclude constraint (Japin Li)
dumped data to a database. Instead, it dumps to a file using pg_restore. Is that
Mailing lists >> pgsql-bugs >> Thread
2025-04-23 04:57:53 | Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load (Euler Taveira)
dump -t test_table -p 5340 -d test_db -f - | sort > /tmp/p.out $ pg_dump -t test
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (13)
2025-04-21 13:56:39 | Command order bug in pg_dump (Kirill Reshke)
dump-restore ./pgbin/bin/pg_dump -d db1 --schema-only > dump-p.sql ./pgbin/bin/createdb db2 restore fails db2=# \i dump
Mailing lists >> pgsql-bugs >> Thread
2025-04-18 15:38:08 | BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference (PG Bug reporting form)
dump a simple backtrace */ 47 #ifdef HAVE_BACKTRACE_SYMBOLS 48 { 49 void *buf[100]; 50 int nframes
Mailing lists >> pgsql-bugs >> Thread
2025-04-10 19:47:44 | BUG #18891: /src/include/lib/simplehash.h possible palloc0 problems (PG Bug reporting form)
dump, pg_verifybackup, pg_rewind. It seems these utils use the frontend version of palloc
Mailing lists >> pgsql-bugs >> Thread
2025-03-14 17:27:07 | Re: BUG #18848: DEREF_AFTER_NULL.EX.COND After having been compared to a NULL (Tom Lane)
dump core if ind_name is null, with or without an Assert. Given the lack
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-03-13 23:52:49 | CHECK that involves a function call behaves differently during bulk load? (Kirk Parker)
dump in COPY from STDIN mode, then when I encountered the issue switched to --inserts
Mailing lists >> pgsql-bugs >> Thread
2025-03-08 04:14:42 | Re: BUG #18836: Cannot import foreign schema under different schema name when foreign table uses (Tom Lane)
dump inside postgres_fdw, which is not a task I care to buy into. But hey, maybe