[COMMITTERS] pgsql: Fix btree_gist to handle timetz zone correctly per recent

2005-04-25 Thread Tom Lane
Log Message: --- Fix btree_gist to handle timetz zone correctly per recent changes. Modified Files: -- pgsql/contrib/btree_gist: btree_time.c (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_time.c.diff?r1=1.5&r2=1.6

[COMMITTERS] pgsql: Re-add item with better description: > * Allow ORDER BY ...

2005-04-25 Thread Bruce Momjian
Log Message: --- Re-add item with better description: > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > all values to return th

Re: [COMMITTERS] pgsql: Remove item, not sure what it refers to:

2005-04-25 Thread Bruce Momjian
Kris Jurka wrote: > > > On Sat, 23 Apr 2005, Bruce Momjian wrote: > > > Log Message: > > --- > > Remove item, not sure what it refers to: > > > > < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > > < index using a sequential scan for highest/lowest values > > <

Re: [COMMITTERS] pgsql: Remove item, not sure what it refers to:

2005-04-25 Thread Bruce Momjian
Stephen Frost wrote: -- Start of PGP signed section. > * Bruce Momjian ([email protected]) wrote: > > Thanks, TODO item readded with a clearer description: > > > > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > > index using a sequential scan for highest

[COMMITTERS] tablelog - tablelog: Created function to create view that will do a

2005-04-25 Thread User Kimhanse
Log Message: --- Created function to create view that will do a backwards restore Modified Files: -- tablelog: table_log_restore.sql (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/table_log_restore.sql.diff?r1=1.1&r2=1.2) ---

Re: [COMMITTERS] pgsql: Remove item, not sure what it refers to:

2005-04-25 Thread Stephen Frost
* Bruce Momjian ([email protected]) wrote: > Thanks, TODO item readded with a clearer description: > > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index

Re: [COMMITTERS] pgsql: Remove item, not sure what it refers to:

2005-04-25 Thread Oleg Bartunov
On Mon, 25 Apr 2005, Stephen Frost wrote: * Bruce Momjian ([email protected]) wrote: Thanks, TODO item readded with a clearer description: * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or index using a sequential scan for highest/lowest values R

Re: [COMMITTERS] pgsql: Re-add item with better description: > * Allow ORDER BY ...

2005-04-25 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Re-add item with better description: >> * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or >> index using a sequential scan for highest/lowest values >> >> Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort >> all v

[COMMITTERS] pgsql: Update description: < * Allow ORDER BY ...

2005-04-25 Thread Bruce Momjian
Log Message: --- Update description: < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > * Allow ORDER BY ... LIMIT # to select high/low value without sort or 868c868 < Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > Right now, if no index

Re: [COMMITTERS] pgsql: Re-add item with better description: > * Allow

2005-04-25 Thread Bruce Momjian
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Re-add item with better description: > > >> * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > >> index using a sequential scan for highest/lowest values > >> > >> Right now, if no index exists, ORDER BY ... LIMI

[COMMITTERS] pgsql: Fix btree_gist to handle timetz zone correctly per recent

2005-04-25 Thread Tom Lane
Log Message: --- Fix btree_gist to handle timetz zone correctly per recent changes. Tags: REL8_0_STABLE Modified Files: -- pgsql/contrib/btree_gist: btree_time.c (r1.3.4.4 -> r1.3.4.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gi

[COMMITTERS] pgsql: get_expr_result_type probably needs to be able to handle OpExpr

2005-04-25 Thread Tom Lane
Log Message: --- get_expr_result_type probably needs to be able to handle OpExpr as well as FuncExpr, to cover cases where a function returning tuple is invoked via an operator. Modified Files: -- pgsql/src/backend/utils/fmgr: funcapi.c (r1.20 -> r1.21) (ht

[COMMITTERS] pgsql: Fix ExpandIndirectionStar to handle cases where the expression to

2005-04-25 Thread Tom Lane
Log Message: --- Fix ExpandIndirectionStar to handle cases where the expression to be expanded is of RECORD type, eg 'select (foo).* from (select foo(f1) from t1) ss' where foo() is a function declared with multiple OUT parameters. Modified Files: -- pgsql/src/backend/parse

[COMMITTERS] oledb - oledb: Added experimental support for "bytea".

2005-04-25 Thread User Shachar
Log Message: --- Added experimental support for "bytea". Modified Files: -- oledb: PgRS.cpp (r1.38 -> r1.39) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/oledb/oledb/PgRS.cpp.diff?r1=1.38&r2=1.39) PgRS.h (r1.24 -> r1.25) (http://cvs.pgfound

[COMMITTERS] pgsql: On further experimentation, there were still a couple of bugs in

2005-04-25 Thread Tom Lane
Log Message: --- On further experimentation, there were still a couple of bugs in ExpandIndirectionStar() ... and in markTargetListOrigin() too. Modified Files: -- pgsql/src/backend/parser: parse_target.c (r1.132 -> r1.133) (http://developer.postgresql.org/

[COMMITTERS] pgsql: Mention that PAM requires the user already exist in the database,

2005-04-25 Thread Bruce Momjian
Log Message: --- Mention that PAM requires the user already exist in the database, per Dick Davies. Modified Files: -- pgsql/doc/src/sgml: client-auth.sgml (r1.76 -> r1.77) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/client-auth.sgml.diff

[COMMITTERS] pgsql: Mention that PAM requires the user already exist in the database,

2005-04-25 Thread Bruce Momjian
Log Message: --- Mention that PAM requires the user already exist in the database, per Dick Davies. Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml: client-auth.sgml (r1.70.4.4 -> r1.70.4.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/

Re: [COMMITTERS] pgsql: Mention that PAM requires the user already exist in the database,

2005-04-25 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Mention that PAM requires the user already exist in the database, per > Dick Davies. I don't recall exactly what Dick suggested, but the patch as applied seems like fairly useless verbiage. Exactly which of our other auth methods allow users who *don't*