Re: GUC names in messages

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: GUC names in messages
Date: 2024-09-04 16:00:00
Message-ID: 36ba4d1b-bc80-e3e2-287f-aacd3199c3d7@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Peter,

[ sorry for the kind of off-topic ]

17.05.2024 14:57, Peter Eisentraut wrote:
> I committed your 0001 and 0002 now, with some small fixes.
>
> There has also been quite a bit of new code, of course, since you posted your patches, so we'll probably find a few
> more things that could use adjustment.
>
> I'd be happy to consider the rest of your patch set after beta1 and/or for PG18.

While translating messages, I've encountered a weird message, updated by
17974ec25:
    printf(_("(in \"wal_sync_method\" preference order, except fdatasync is Linux's default)\n"));

Does "except ..." make sense here or it's just a copy-and-paste from docs?:
        The default is the first method in the above list that is supported
        by the platform, except that <literal>fdatasync</literal> is the default on
        Linux and FreeBSD.

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxim Orlov 2024-09-04 16:05:32 Re: Test 041_checkpoint_at_promote.pl faild in installcheck due to missing injection_points
Previous Message Andres Freund 2024-09-04 15:58:33 GetRelationPath() vs critical sections