Re: Delete query takes exorbitant amount of time
| От | Stephan Szabo |
|---|---|
| Тема | Re: Delete query takes exorbitant amount of time |
| Дата | |
| Msg-id | 20050329083336.G58020@megazone.bigpanda.com обсуждение исходный текст |
| Ответ на | Re: Delete query takes exorbitant amount of time (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-performance |
On Tue, 29 Mar 2005, Tom Lane wrote: > Stephan Szabo <sszabo@megazone.bigpanda.com> writes: > > If there were some way to pass a "limit" into SPI_prepare that was treated > > similarly to a LIMIT clause for planning purposes but didn't actually > > change the output plan to only return that number of rows, we could use > > that. > > Hmm ... the planner does have the ability to do that sort of thing (we > use it for cursors). SPI_prepare doesn't expose the capability. > Perhaps adding a SPI_prepare variant that does expose it would be the > quickest route to a solution. > > I get a headache every time I look at the RI triggers ;-). Do they Me too, honestly. > always know at the time of preparing a plan which way it will be used? I believe so. I think each saved plan pretty much lives for a single trigger type/argument set and is basically used in only one place.
В списке pgsql-performance по дате отправления: