From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
---|---|
To: | sud <suds1434(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Insert query performance |
Date: | 2024-08-19 07:55:32 |
Message-ID: | CAGeimVqF+2vAwbMRznGvbAWs=1u+4zLkZ11irO3yuBP6sLmPow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Sud,
Please make following change in your postgresql.conf file
log_statement = 'all'
Regards,
Ikram
On Mon, Aug 19, 2024 at 12:48 PM sud <suds1434(at)gmail(dot)com> wrote:
> Hello All,
>
> In a version 15.4 postgres database, Is it possible that , if we have two
> big range partition tables with foreign key relationships between them,
> insert into the child table can cause slowness if we don't have foreign key
> index present in the child table? Basically it need to make sure the new
> row already added to parent partition table or not.
>
>
> And if there is any possible way(example query tracing etc) to get the
> underlying system queries which gets triggered as part of the main insert
> query? For example in above scenario, postgres must be executing some query
> to check if the incoming row to the child table already exists in the
> parent table or not?
>
>
> Regards
>
> Sud
>
--
Muhammad Ikram
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-08-19 11:03:32 | Re: Insert query performance |
Previous Message | sud | 2024-08-19 07:48:18 | Insert query performance |