| From: | Igor Korot <ikorot01(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Another documentation issue |
| Date: | 2025-04-24 05:29:17 |
| Message-ID: | CA+FnnTyhKdyPa3UggX7L5wAfq+BV-NcW0xcDihYNTdk4mS76TA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi, David,
On Thu, Apr 24, 2025 at 12:23 AM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wednesday, April 23, 2025, Igor Korot <ikorot01(at)gmail(dot)com> wrote:
>>
>>
>> How do you handle sch situation from the client POV?
>
>
> Get the current value. If it’s non-zero the system definitely supports it. If it’s zero it probably doesn’t. But give the user an option to specify a value anyway just in case. If they try and it errors, it doesn’t support it.
There definitely is an option to set it.
The question is more about the default value...
Thank you.
>
> David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-04-24 05:43:56 | Re: Another documentation issue |
| Previous Message | Igor Korot | 2025-04-24 05:26:47 | Re: Another documentation issue |