| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reducing the log spam |
| Date: | 2024-05-02 10:47:45 |
| Message-ID: | cf374c4a52d2c93cdc118f4245feb6cc822a34f8.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2024-03-11 at 09:33 +0100, Jelte Fennema-Nio wrote:
> - the subscriber's server log.
> + the subscriber's server log if you remove <literal>23505</literal> from
> + <xref linkend="guc-log-suppress-errcodes"/>.
>
> This seems like a pretty big regression. Being able to know why your
> replication got closed seems pretty critical.
Yes. But I'd argue that that is a shortcoming of logical replication:
there should be a ways to get this information via SQL. Having to look into
the log file is not a very useful option.
The feature will become much less useful if unique voilations keep getting logged.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-05-02 11:08:30 | Re: Reducing the log spam |
| Previous Message | Alexander Korotkov | 2024-05-02 10:07:54 | Re: Removing unneeded self joins |