| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: pg_receivewal starting position |
| Date: | 2021-10-25 07:40:10 |
| Message-ID: | YXZfWkCHo7VuJJUa@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 25, 2021 at 09:15:32AM +0200, Ronan Dunklau wrote:
> Does it make sense though ? The NULL slot_name case handling is pretty
> straight forward has it will be handled by string formatting, but in the case
> of a null restart_lsn, we have no way of knowing if the command was issued at
> all.
If I am following your point, I don't think that it matters much here,
and it seems useful to me to be able to pass NULL for both of them, so
as one can check if the slot exists or not with an API designed this
way.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2021-10-25 07:41:23 | Re: Added schema level support for publication. |
| Previous Message | Ronan Dunklau | 2021-10-25 07:26:30 | Re: Non-superuser subscription owners |