On Wed, Jun 29, 2022 at 4:30 PM Marcos Pegoraro wrote:
>
> I´m using 14.4.
>
This additional information will be available in 15 as it is committed
as part of commit abc0910e.
--
With Regards,
Amit Kapila.
I´m using 14.4.
These are some lines with that error, and context is empty.
And yes, if context had this info you wrote would be fine
2022-06-28 08:18:23.600 -03,,,20915,,62b9c77b.51b3,1328,,2022-06-27
12:06:35 -03,4/690182,433844252,ERROR,23505,"duplicate key value violates
unique constraint ""pk
On Tue, Jun 28, 2022 at 5:50 PM Marcos Pegoraro wrote:
>
> I don´t know how to create a patch, maybe someday, but for now I´m just
> sending this little problem if somebody can solve it.
>
> In a multi schema environment where several tables has same structure is a
> little bit hard to know whic
I don´t know how to create a patch, maybe someday, but for now I´m just
sending this little problem if somebody can solve it.
In a multi schema environment where several tables has same structure is a
little bit hard to know which one already has that primary key.
On log I see now on replica serv
