Hi,
I reported a bug aobut it earlier, and from what I know it has been
fixed, but new release will come later.
For now I have this situation:
1. max_replication_slots is 50
2. database to replicate has 67 schemas, and ~ 26k tables.
3. schemas are split into 5 slots
4. pg14 side has max_sync_work
Hello Dear
sorry for the late reply
your response helped me to finish the feature successfully
thank you for your efforts
my best regards
On Wed, 17 Aug 2022, 6:59 pm Laurenz Albe, wrote:
> On Wed, 2022-08-17 at 14:33 +0300, Mohammed falih wrote:
> > I created the dictionary by this query
> > CR
I have not been able to get the "ON CONFLICT" clause to work
I am using psql 14.4 on ubuntu
Given the following table definition
CREATE TABLE my_companies (
company_id SERIAL NOT NULL PRIMARY KEY,
second_id INTEGER NOT NULL REFERENCES big_list(second_id),
string_company_id TEXT NOT NULL,
You need to prefix the rhs column(s) with 'excluded.'. For example:
on conflict (company_name) do update set company_name =
concat(excluded.company_name,'++',excluded.string_company_id);
On Sat, Sep 24, 2022 at 7:28 AM Barry Kimelman wrote:
>
> I have not been able to get the "ON CONFLICT" clau
On Fri, Sep 23, 2022 at 2:28 PM Barry Kimelman wrote:
>
> CREATE UNIQUE INDEX my_companies_id_unique ON
> my_companies(string_company_id) WHERE delete_timestamp IS NULL;
> CREATE UNIQUE INDEX my_companies_company_name_unique ON
> my_companies(company_name) WHERE delete_timestamp IS NULL;
>
> I is
On Fri, Sep 23, 2022 at 4:43 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Sep 23, 2022 at 2:28 PM Barry Kimelman
> wrote:
>
>>
>> CREATE UNIQUE INDEX my_companies_id_unique ON
>> my_companies(string_company_id) WHERE delete_timestamp IS NULL;
>> CREATE UNIQUE INDEX my_compa
