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: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, vignesh C <vignesh21@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-09-07T05:08:18Z
Lists: pgsql-hackers

Attachments

pá 4. 9. 2020 v 5:21 odesílatel Pavel Stehule <pavel.stehule@gmail.com>
napsal:

>
>
> pá 4. 9. 2020 v 2:15 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
>
>> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> > So, Tom added a coding pattern for doing this in commit 8f8154a503c7,
>> > which is ostensibly also to be used in pg_regress [1] -- maybe it'd be
>> > useful to have this in src/common?
>>
>> Done, see pg_get_line() added by 67a472d71.
>>
>
> Here is updated patch for pg_dump
>

another update based on pg_get_line_append function

Regards

Pavel


> Regards
>
> Pavel
>
>
>
>>
>>                         regards, tom lane
>>
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix array subscript warnings

  2. Read include/exclude commands for dump/restore from file

  3. Allow records to span multiple lines in pg_hba.conf and pg_ident.conf.