| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Richard Huxton" <dev(at)archonet(dot)com>, "Tom Yeh" <tom_m_yeh(at)yahoo(dot)com> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1487: Index problem |
| Date: | 2005-02-21 16:04:15 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472B63E@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> -----Original Message-----
> From: pgsql-bugs-owner(at)postgresql(dot)org
> [mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Richard Huxton
> Sent: 21 February 2005 15:37
> To: Tom Yeh
> Cc: pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] BUG #1487: Index problem
>
> > The above can be replicated by using pgAdmin III only.
>
> Are you saying it doesn't do this from psql?
pgAdmin uses libpq, just as psql does, so I cannot imagine why this
would be the case. pgAdmin also does not do anything to try to affect
query plans in any way.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-02-21 16:12:31 | Re: BUG #1487: Index problem |
| Previous Message | Richard Huxton | 2005-02-21 15:36:57 | Re: BUG #1487: Index problem |