Re: Speed of lo_unlink vs. DELETE on BYTEA
| От | Albe Laurenz |
|---|---|
| Тема | Re: Speed of lo_unlink vs. DELETE on BYTEA |
| Дата | |
| Msg-id | D960CB61B694CF459DCFB4B0128514C2049FCE78@exadv11.host.magwien.gv.at обсуждение исходный текст |
| Ответ на | Speed of lo_unlink vs. DELETE on BYTEA ("Reuven M. Lerner" <reuven@lerner.co.il>) |
| Ответы |
Re: Speed of lo_unlink vs. DELETE on BYTEA
|
| Список | pgsql-general |
Reuven M. Lerner wrote: > When a record in the main table is deleted, there is a rule (yes a rule -- not a trigger) in the > referencing table that performs a lo_unlink on the associated object. > I just want to check that my intuition is correct: Wouldn't it be way faster and more efficient > for us to use BYTEA columns to store the data (which can get into the 20-50 MB range), > and for us to just depend on ON DELETE CASCADE, rather than a rule? [followed by dramatic performance numbers] Could you try with a trigger instead of a rule and see if the performance is better? Yours, Laurenz Albe
В списке pgsql-general по дате отправления: