Re: Bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: phd2(at)earthling(dot)net
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Bug
Date: 2000-10-06 05:57:33
Message-ID: 24733.970811853@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

A good while back, Oleg Broytmann <phd(at)sun(dot)med(dot)ru> wrote:
>> ran=> create table test1 (n int default nextval('seq_test'), t text);
>> ran=> insert into test1 ("t") select distinct src from test_source;
>> [ doesn't work right ]

> My, that's an interesting case. I think that fits right in with my
> remark yesterday that the SELECT inside an INSERT ... SELECT needs
> to have a targetlist that's separate from the INSERT's list. As it
> stands, we form a targetlist representing the set of values that need
> to be inserted into the target table --- and then the DISTINCT pass
> runs on those tuples :-(, because there is nothing else for it to
> run on.

FYI, this now works in current sources.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alfred Perlstein 2000-10-06 06:32:34 Re: Exited with status 139
Previous Message Kristofer Munn 2000-10-06 05:38:17 Re: Exited with status 139