Re: Perform streaming logical transactions by background workers and parallel apply

2023-04-30 Thread Masahiko Sawada
On Fri, Apr 28, 2023 at 6:01 PM Amit Kapila wrote: > > On Fri, Apr 28, 2023 at 11:48 AM Masahiko Sawada > wrote: > > > > On Fri, Apr 28, 2023 at 11:51 AM Amit Kapila > > wrote: > > > > > > On Wed, Apr 26, 2023 at 4:11 PM Zhijie Hou (Fujitsu) > > > wrote: > > > > > > > > On Wednesday, April 26

Re: Direct I/O

2023-04-30 Thread Thomas Munro
On Mon, May 1, 2023 at 12:00 PM Tom Lane wrote: > Justin Pryzby writes: > > On Sun, Apr 30, 2023 at 06:35:30PM +1200, Thomas Munro wrote: > >> What about a > >> warning message about that at startup if it's on? > > > Such a warning wouldn't be particularly likely to be seen by someone who > > alr

Re: Direct I/O

2023-04-30 Thread Tom Lane
Justin Pryzby writes: > On Sun, Apr 30, 2023 at 06:35:30PM +1200, Thomas Munro wrote: >> What about a >> warning message about that at startup if it's on? > Such a warning wouldn't be particularly likely to be seen by someone who > already didn't read/understand the docs for the not-feature that

Re: Autogenerate some wait events code and documentation

2023-04-30 Thread Michael Paquier
On Fri, Apr 28, 2023 at 02:29:13PM +0200, Drouvot, Bertrand wrote: > On 4/27/23 8:13 AM, Michael Paquier wrote: >> Generating the contents of Lock would mean to gather in a single file >> the data for the generation of LockTagType in lock.h, the list of >> LockTagTypeNames in lockfuncs.c and the de

Re: Direct I/O

2023-04-30 Thread Justin Pryzby
On Sun, Apr 30, 2023 at 06:35:30PM +1200, Thomas Munro wrote: > On Sun, Apr 30, 2023 at 4:11 PM Noah Misch wrote: > > Speaking of the developer-only status, I find the io_direct name more > > enticing > > than force_parallel_mode, which PostgreSQL renamed due to overuse from > > people > > expec

Re: Direct I/O

2023-04-30 Thread Thomas Munro
On Sun, Apr 30, 2023 at 6:35 PM Thomas Munro wrote: > On Sun, Apr 30, 2023 at 4:11 PM Noah Misch wrote: > > Speaking of the developer-only status, I find the io_direct name more > > enticing > > than force_parallel_mode, which PostgreSQL renamed due to overuse from > > people > > expecting non-

Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound

2023-04-30 Thread Peter Geoghegan
On Sat, Apr 29, 2023 at 7:30 PM John Naylor wrote: > How about > > -HINT: To avoid a database shutdown, [...] > +HINT: To prevent XID exhaustion, [...] > > ...and "MXID", respectively? We could explain in the docs that vacuum and > read-only queries still work "when XIDs have been exhausted", e

Re: Possible regression setting GUCs on \connect

2023-04-30 Thread Jonathan S. Katz
On 4/28/23 12:29 PM, Pavel Borisov wrote: Hi! On Fri, 28 Apr 2023 at 17:42, Jonathan S. Katz wrote: On 4/27/23 8:04 PM, Alexander Korotkov wrote: On Fri, Apr 28, 2023 at 2:30 AM Alexander Korotkov wrote: Additionally, I think if we start recording role OID, then we need a full set of manag

Re: run pgindent on a regular basis / scripted manner

2023-04-30 Thread Tom Lane
Andrew Dunstan writes: > On 2023-04-28 Fr 14:08, Bruce Momjian wrote: >> Can those comments be added by a preprocessor before calling perltidy, >> and then removed on completion? > I imagine so, but we'd need a way of determining algorithmically which > lines to protect. That might not be at all

Re: run pgindent on a regular basis / scripted manner

2023-04-30 Thread Andrew Dunstan
On 2023-04-28 Fr 14:08, Bruce Momjian wrote: On Wed, Apr 26, 2023 at 03:44:47PM -0400, Andrew Dunstan wrote: On 2023-04-26 We 09:27, Tom Lane wrote: I doubt there's something like that. You can freeze arbitrary blocks of code like this (from the manual) #<<<  format skipping: do not let perlti

Re: run pgindent on a regular basis / scripted manner

2023-04-30 Thread Andrew Dunstan
On 2023-04-28 Fr 05:25, Alvaro Herrera wrote: On 2023-Feb-05, Andrew Dunstan wrote: So here's a diff made from running perltidy v20221112 with the additional setting --valign-exclusion-list=", = => || && if unless" I ran this experimentally with perltidy 20230309, and compared that with the -