| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | felix(at)crowfix(dot)com |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: DELETE with JOIN |
| Date: | 2008-08-07 22:12:32 |
| Message-ID: | 20080807221232.GL4171@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
felix(at)crowfix(dot)com wrote:
> On Thu, Aug 07, 2008 at 03:58:51PM -0400, Tom Lane wrote:
> > felix(at)crowfix(dot)com writes:
> > > I have tried to do this before and always found a way, usually
> >
> > > DELETE FROM a WHERE a.b_id IN (SELECT id FROM b WHERE second_id = ?)
> >
> > > but I have too many rows, millions, in the IN crowd, ha ha, and it
> > > barfs.
> >
> > Define "barfs". That seems like the standard way to do it, and it
> > should work.
>
> In this case, the first database I tried was Oracle, and it complained
> of too much transactional data; I forget the exact wording now.
I suggest you do not assume that Oracle implementation details apply to
Postgres, because they do not, most of the time. They certainly don't
in this case.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | felix | 2008-08-07 23:37:41 | Re: DELETE with JOIN |
| Previous Message | Christophe | 2008-08-07 21:42:10 | Re: DELETE with JOIN |