pgsql: logging: Also add the command prefix to detail and hint messages

2022-05-29 Thread Peter Eisentraut
logging: Also add the command prefix to detail and hint messages This makes the output line up better and allows filtering messages by command. Discussion: https://www.postgresql.org/message-id/[email protected] Branch -- master Details --- https://g

Re: pgsql: Extend pg_publication_tables to display column list and row filt

2022-05-29 Thread Amit Kapila
On Sun, May 29, 2022 at 2:00 AM Andres Freund wrote: > > Hi, > > On 2022-05-19 08:59:13 +0530, Amit Kapila wrote: > > On Thu, May 19, 2022 at 8:40 AM Tom Lane wrote: > > > > > > Amit Kapila writes: > > > > Extend pg_publication_tables to display column list and row filter. > > > > > > Is this re

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: doc: Reword description of roles able to view track_activities's

2022-05-29 Thread Michael Paquier
doc: Reword description of roles able to view track_activities's info The information generated when track_activities is accessible to superusers, roles with the privileges of pg_read_all_stats, as well as roles one has the privileges of. The original text did not outline the last point, while th

pgsql: Fix COPY FROM when database encoding is SQL_ASCII.

2022-05-29 Thread Heikki Linnakangas
Fix COPY FROM when database encoding is SQL_ASCII. In the codepath when no encoding conversion is required, the check for incomplete character at the end of input incorrectly used server encoding's max character length, instead of the client's. Usually the server and client encodings are the same

pgsql: Fix COPY FROM when database encoding is SQL_ASCII.

2022-05-29 Thread Heikki Linnakangas
Fix COPY FROM when database encoding is SQL_ASCII. In the codepath when no encoding conversion is required, the check for incomplete character at the end of input incorrectly used server encoding's max character length, instead of the client's. Usually the server and client encodings are the same

pgsql: Doc: fix missing/bogus documentation of range_intersect_agg().

2022-05-29 Thread Tom Lane
Doc: fix missing/bogus documentation of range_intersect_agg(). The form taking anymultirange had not been documented. This was fixed in HEAD in b21c4cf95, but that should have been back-patched to v14 since the function was added there. Do so now. Also, the form taking anyrange was incorrectly

pgsql: Doc: fix missing/bogus documentation of range_intersect_agg().

2022-05-29 Thread Tom Lane
Doc: fix missing/bogus documentation of range_intersect_agg(). The form taking anymultirange had not been documented. This was fixed in HEAD in b21c4cf95, but that should have been back-patched to v14 since the function was added there. Do so now. Also, the form taking anyrange was incorrectly