Re: partitioning and locking problems
От | Marc Morin |
---|---|
Тема | Re: partitioning and locking problems |
Дата | |
Msg-id | 2BCEB9A37A4D354AA276774EE13FB8C263B3E5@mailserver.sandvine.com обсуждение исходный текст |
Ответ на | partitioning and locking problems ("Marc Morin" <marc@sandvine.com>) |
Ответы |
Re: partitioning and locking problems
|
Список | pgsql-performance |
Tom, Do you mean it would be impossible to change the code so that existing selects continue to use the pre-truncated table until they commit? Or just require a more extensive change? The update/insert rule change appears to be more more doable? No? > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Wednesday, February 01, 2006 12:50 AM > To: Marc Morin > Cc: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] partitioning and locking problems > > "Marc Morin" <marc@sandvine.com> writes: > > Would like to understand the implications of changing postgres' > > code/locking for rule changes and truncate to not require > locking out > > select statements? > > It won't work... > > regards, tom lane > >
В списке pgsql-performance по дате отправления: