On Sat, 23 Mar 2024 at 23:08, Laurenz Albe wrote:
> On Sat, 2024-03-23 at 22:41 +0530, veem v wrote:
> > 1)As we see having foreign key defined is making the detach partition run
> > for minutes(in our case 5-10minutes for 60 million rows partition), so
> > how to make the parent table partit
On Sat, 2024-03-23 at 22:41 +0530, veem v wrote:
> 1)As we see having foreign key defined is making the detach partition run
> for minutes(in our case 5-10minutes for 60 million rows partition), so
> how to make the parent table partition detach and drop work fast in such
> a scenario while m
Trying to consolidate the main questions here as below.
1)As we see having foreign key defined is making the detach partition run
for minutes(in our case 5-10minutes for 60 million rows partition), so how
to make the parent table partition detach and drop work fast in such a
scenario while maintai
On Sat, Mar 23, 2024 at 12:33 AM arun chirappurath
wrote:
> Dear All,
>
> Apologies the way i am asking question as i am more a SQL Server person
> and a new postgre man..
>
> I have used a query store in SQL server. it provides me option to load
> statistics data to temp table and get below imp
for 3121s! [migration/25:166]
> >
> > Sounds like failing hardware to me :-(
>
>
> Updating to 15.6 would rule out any bugs squashed in the last 15 months.
Yesterday the message appeared 300 times:
sunrise:~ # xz -dc /var/log/messages-20240323.xz | grep lockup | wc -l
323
S