Re: [PATCH] PostgreSQL DLR speedup
"Vincent CHAVANIS" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <124b01c70898$97dbe3d0$9600a8c0@vince> |
Ok the question now is: Can we broke the <= v7 user's compatibility Obviously not. Vincent ----- Original Message ----- From: "Andreas Fink" <[email protected]> To: "Alexander Malysh" <[email protected]> Cc: <[email protected]> Sent: Wednesday, November 15, 2006 8:03 AM Subject: Re: [PATCH] PostgreSQL DLR speedup > postgres does support LIMIT 1 in version 8. > > On 15.11.2006, at 01:58, Alexander Malysh wrote: > >> Am 14.11.2006, 14:36 Uhr, schrieb Andreas Fink <[email protected]>: >> >>> >>> On 10.11.2006, at 18:52, Georg von Zezschwitz wrote: >>> >>>> Alexander Malysh schrieb: >>>>> Hi, >>>>> >>>>> Andreas , this is not true what you say. Mysql use LIMIT 1 in >>>>> delete and update. Postgres should use oid because there is not >>>>> limit support. >>>>> >>> >>> This was not about LIMIT 1 (there was a reason for that) but about >>> doing DELETE and SELECT in one statement. >>> The LIMIT 1 was a workaround in the error of EMI protocol not >>> giving unique timestamps. >>> the timestamp on a SMSC is not unique, not even for one >>> destination number. >> >> Postgres doesn't support LIMIT 1 so there no way except with >> subselect to tell postgres to delete only one row. >>