| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "satishcampus(at)gmail(dot)com" <satishcampus(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16544: How to identify trigger is called from the node where row is created? |
| Date: | 2020-07-16 05:31:34 |
| Message-ID: | CAKFQuwZ51Sq_zo44G23e3quYwUgeqZe_F0e1PYC9NB0a8siPkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, July 15, 2020, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16544
> Logged by: sat
> Email address: satishcampus(at)gmail(dot)com
> PostgreSQL version: 12.3
> Operating system: Debian
> Description:
>
> In BDR cluster, I have multiple nodes say A and B and it has table named
> 'config'.
>
This isn’t the right mailing list for this topic. It isn’t a bug report.
Moreover, core PostgreSQL doesn’t have BDR so this seems like it should
directed to whichever product is providing that capability. I’m pretty
sure that nothing in core PostgreSQL ties nodes to data. But if you want
explore this on the community lists you want to send to the -general list,
not the bug reporting one.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-07-16 07:19:01 | Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows |
| Previous Message | PG Bug reporting form | 2020-07-16 04:54:58 | BUG #16544: How to identify trigger is called from the node where row is created? |