Re: proposal: possibility to read dumped table's name from file
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Julien Rouhaud <rjuju123@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, Daniel Gustafsson <daniel@yesql.se>, Andrew Dunstan <andrew@dunslane.net>, John Naylor <john.naylor@enterprisedb.com>, Erik Rijkers <er@xs4all.nl>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>,
Dean Rasheed <dean.a.rasheed@gmail.com>, Stephen Frost <sfrost@snowman.net>, Surafel Temesgen <surafel3000@gmail.com>, vignesh C <vignesh21@gmail.com>, pgsql-hackers@postgresql.org
Date: 2022-11-22T17:02:21Z
Lists: pgsql-hackers
Attachments
- pg_dump-filter-20221122.patch (text/x-patch) patch
Hi út 22. 11. 2022 v 8:39 odesílatel Andres Freund <andres@anarazel.de> napsal: > Hi, > > On 2022-11-13 20:32:47 +0100, Pavel Stehule wrote: > > updated patch attached > > It fails with address sanitizer that's now part of CI: > > https://cirrus-ci.com/task/6031397744279552?logs=test_world#L2659 > > [06:33:11.271] # ==31965==ERROR: AddressSanitizer: heap-buffer-overflow on > address 0x619000000480 at pc 0x559f1ac40822 bp 0x7ffea83e1ad0 sp > 0x7ffea83e1ac8 > [06:33:11.271] # READ of size 1 at 0x619000000480 thread T0 > [06:33:11.271] # #0 0x559f1ac40821 in read_pattern > /tmp/cirrus-ci-build/src/bin/pg_dump/filter.c:302 > [06:33:11.271] # #1 0x559f1ac40e4d in filter_read_item > /tmp/cirrus-ci-build/src/bin/pg_dump/filter.c:459 > [06:33:11.271] # #2 0x559f1abe6fa5 in read_dump_filters > /tmp/cirrus-ci-build/src/bin/pg_dump/pg_dump.c:18229 > [06:33:11.271] # #3 0x559f1ac2bb1b in main > /tmp/cirrus-ci-build/src/bin/pg_dump/pg_dump.c:630 > [06:33:11.271] # #4 0x7fd91fabfd09 in __libc_start_main > (/lib/x86_64-linux-gnu/libc.so.6+0x23d09) > [06:33:11.271] # #5 0x559f1abe5d29 in _start > (/tmp/cirrus-ci-build/tmp_install/usr/local/pgsql/bin/pg_dump+0x39d29) > [06:33:11.271] # > [06:33:11.271] # 0x619000000480 is located 0 bytes to the right of > 1024-byte region [0x619000000080,0x619000000480) > [06:33:11.271] # allocated by thread T0 here: > [06:33:11.271] # #0 0x7fd91fe14e8f in __interceptor_malloc > ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145 > [06:33:11.271] # #1 0x559f1ac69f35 in pg_malloc_internal > /tmp/cirrus-ci-build/src/common/fe_memutils.c:30 > [06:33:11.271] # #2 0x559f1ac69f35 in palloc > /tmp/cirrus-ci-build/src/common/fe_memutils.c:117 > [06:33:11.271] # > [06:33:11.271] # SUMMARY: AddressSanitizer: heap-buffer-overflow > /tmp/cirrus-ci-build/src/bin/pg_dump/filter.c:302 in read_pattern > > should be fixed in attached patch I found and fix small memleak 24bytes per filter row (PQExpBufferData) Regards Pavel > > Greetings, > > Andres Freund >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix array subscript warnings
- 17935e1fdf0a 17.0 landed
-
Read include/exclude commands for dump/restore from file
- a5cf808be55b 17.0 landed
-
Allow records to span multiple lines in pg_hba.conf and pg_ident.conf.
- 8f8154a503c7 14.0 cited