The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/sql-merge.html
Description:
From the description it looks like a single WHEN clause is accepted, which
is definitely not true.
Please let us know how many WHEN clauses are accepted for eac
On 2022-Nov-17, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/sql-merge.html
> Description:
>
> From the description it looks like a single WHEN clause is accepted, which
> is definitely not true.
H
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/logical-replication-row-filter.html
Description:
There are several things missing here and some of them I found to be highly
important:
1. How can I find why a logical replication failed.
Hello!Thank you. I was fooled by the fact that sometimes it is marked with
[...] and other times with [,...]
I think that consistency might worth attention, since [...] may indicate
"anything", while [,...] are more likely to indicate a specific thing that may
be repeated.
Best regards, Cristi B
On Thu, Nov 17, 2022 at 11:20 AM Boboc Cristi wrote:
> Hello!
> Thank you. I was fooled by the fact that sometimes it is marked with [...]
> and other times with [,...]
>
> I think that consistency might worth attention, since [...] may indicate
> "anything", while [,...] are more likely to indic
I agree that your statement is true, but it is still not quite self sufficient.
For the time being I have no idea how to make it easier to be understood. As I
have said, for me it is a little confusing.
I would pay attention to Kirk Parker idea: when_clause [
when_clause [...]] to indicate repet
On Thu, Nov 17, 2022 at 12:06 PM Boboc Cristi wrote:
> I agree that your statement is true, but it is still not quite self
> sufficient.
>
> For the time being I have no idea how to make it easier to be understood.
> As I have said, for me it is a little confusing.
>
> I would pay attention to Ki
OK, I agree. I'll do my best to adopt the site conventions for every specific
type of site within the corresponding pages.
Top-posting is not by my choice, it is how the email client works.
Since you have good reasons to keep the conventions of yours, then please
accept that email clients have th
On Thu, Nov 17, 2022 at 12:48 PM Boboc Cristi wrote:
> OK, I agree. I'll do my best to adopt the site conventions for every
> specific type of site within the corresponding pages.
>
> *Top-posting is not by my choice, it is how the email client works.*
>
>
Mine has the same default/convention. I
"David G. Johnston" writes:
> On Thu, Nov 17, 2022 at 12:48 PM Boboc Cristi wrote:
>> *Top-posting is not by my choice, it is how the email client works.*
> Mine has the same default/convention. It is not difficult to choose to
> behave differently if one wishes. Given that these messages are
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/plpgsql-trigger.html
Description:
Type alignment issue for salary at "Example 43.4. A PL/pgSQL Trigger
Function for Auditing":
CREATE TABLE emp_audit(
operation char(1) NOT
On Thu, 2022-11-17 at 18:14 +, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/13/plpgsql-trigger.html
>
> Type alignment issue for salary at "Example 43.4. A PL/pgSQL Trigger
> Function for Auditing":
>
> CREATE TABLE emp_audit(
> operation char(1) NOT NULL,
Dear David, your suggestion would be good if it could be applied.
I have not found the setting you are talking about. I attach here a screenshot
of the settings page. Since obviously you are more experimented than me about
the mail clients, please help.I mention I am using Yahoo's web client.
13 matches
Mail list logo
