Re: define PG_REPLSLOT_DIR

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: define PG_REPLSLOT_DIR
Date: 2024-08-20 08:41:48
Message-ID: ZsRWzOBVliIzd84O@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 20, 2024 at 11:10:46AM +0530, Ashutosh Bapat wrote:
> Since these are all related changes, doing them at once might make it
> faster. You may use multiple commits (one for each change)

Doing multiple commits with individual definitions for each path would
be the way to go for me. All that is mechanical, still that feels
slightly cleaner.

> to "contain" errors.

I am not sure what you mean by that.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-08-20 08:42:25 Re: Adding clarification to description of IPC wait events XactGroupUpdate and ProcArrayGroupUpdate
Previous Message shveta malik 2024-08-20 08:30:53 Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber