Neil Dugan wrote:
On Sun, 2005-02-13 at 20:40 -0800, Stephan Szabo wrote:
On Mon, 14 Feb 2005, Neil Dugan wrote:
I am using PostgreSQL 7.4.7
I have a table with serveral fields two of these are a serialno
(bigserial) and name(varchar). I have created two indexs on these
fields.
On Mon, 2005-02-14 at 12:55, Bruce Momjian wrote:
Neil Dugan wrote:
On Sun, 2005-02-13 at 20:40 -0800, Stephan Szabo wrote:
On Mon, 14 Feb 2005, Neil Dugan wrote:
I am using PostgreSQL 7.4.7
I have a table with serveral fields two of these are a serialno
(bigserial) and
Bruce Momjian pgman@candle.pha.pa.us writes:
What this brings up is that we have no way to create indexes that have
mixed ascending/descending column specifications.
Should this be a TODO? I am unsure.
I thought we already had a TODO to provide reverse-sort operator classes
in the standard
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
What this brings up is that we have no way to create indexes that have
mixed ascending/descending column specifications.
Should this be a TODO? I am unsure.
I thought we already had a TODO to provide reverse-sort operator
I am using PostgreSQL 7.4.7
I have a table with serveral fields two of these are a serialno
(bigserial) and name(varchar). I have created two indexs on these
fields.
1) on name
2) on name,serialno
if I use the command
'select * from table order by name limit 1'
everything is OK
if I use
On Mon, 14 Feb 2005, Neil Dugan wrote:
I am using PostgreSQL 7.4.7
I have a table with serveral fields two of these are a serialno
(bigserial) and name(varchar). I have created two indexs on these
fields.
1) on name
2) on name,serialno
if I use the command
'select * from table
On Sun, 2005-02-13 at 20:40 -0800, Stephan Szabo wrote:
On Mon, 14 Feb 2005, Neil Dugan wrote:
I am using PostgreSQL 7.4.7
I have a table with serveral fields two of these are a serialno
(bigserial) and name(varchar). I have created two indexs on these
fields.
1) on name
2)
