From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump: Remove "blob" terminology |
Date: | 2022-12-05 08:04:58 |
Message-ID: | 95467596-834d-baa4-c67c-5db1096ed549@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02.12.22 09:34, Daniel Gustafsson wrote:
>> On 2 Dec 2022, at 08:09, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
>> fixed
>
> +1 on this version of the patch, LGTM.
committed
>> I also put back the old long options forms in the documentation and help but marked them deprecated.
>
> + <term><option>--blobs</option> (deprecated)</term>
> While not in scope for this patch, I wonder if we should add a similar
> (deprecated) marker on other commandline options which are documented to be
> deprecated. -i on bin/postgres comes to mind as one candidate.
makes sense
From | Date | Subject | |
---|---|---|---|
Next Message | Drouvot, Bertrand | 2022-12-05 08:11:43 | Re: Generate pg_stat_get_* functions with Macros |
Previous Message | David Rowley | 2022-12-05 08:02:06 | Re: slab allocator performance issues |