Re: Another unexpected behaviour

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Another unexpected behaviour
Date: 2011-07-20 05:44:35
Message-ID: CAKt_Zftm3mDNTEcs+RqzrdiArXZg-mwudf6j+_L8xKHN=Bh0mQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jul 19, 2011 at 10:41 PM, <tomas(at)tuxteam(dot)de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, Jul 18, 2011 at 03:18:43PM -0700, Shianmiin wrote:
>> setup:
>> ====
>> drop table if exists t1;
>> create table t1 (f1 int);
>> create unique index uix_t1 on t1(f1) ;
>> insert into t1(f1) values (1), (2), (3);
>> select * from t1;
>>
>> f1

If you are trying to make this work, you can add an order by to the
update and that allows you to avoid this problem.

Best Wishes,
Chris Travers

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2011-07-20 05:56:37 Re: Building an home computer for best Poker Tracker performance
Previous Message tomas 2011-07-20 05:41:02 Re: Another unexpected behaviour