| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <akapila(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP. |
| Date: | 2022-03-22 02:06:46 |
| Message-ID: | 2446637.1647914806@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Amit Kapila <akapila(at)postgresql(dot)org> writes:
> The user can specify LSN by ALTER SUBSCRIPTION ... SKIP (lsn = XXX),
> which allows the apply worker to skip the transaction finished at
> specified LSN. The apply worker skips all data modification changes within
> the transaction.
Hmm ... this seems like a really poor choice of syntax.
I would expect ALTER to be used for changes of persistent
object properties, which surely this is not?
An alternative perhaps could be to invoke the operation
via a function.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-03-22 02:53:00 | Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP. |
| Previous Message | Amit Kapila | 2022-03-22 01:56:03 | pgsql: Add ALTER SUBSCRIPTION ... SKIP. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-22 02:13:48 | Re: Frontend error logging style |
| Previous Message | Tom Lane | 2022-03-22 02:00:37 | Re: Frontend error logging style |