Current open 6.3 issues
Here they are:
---------------------------------------------------------------------------
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
self-join optimizer bug
subselects(Vadim)
On Wed, 21 Jan 1998, Bruce Momjian wrote:
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
The last I saw, we agreed (on the client side) to leave the current
settings for 8k tuples.
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
self-join optimizer bug
subselects(Vadim)
PS: I'm having to commute to London all this week, so I'm not getting the
time to do anything :-(
Hopefully it should ease after this Friday.
--
Peter T Mount petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk
Where can i get it ?
On Wed, 21 Jan 1998, Bruce Momjian wrote:
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
self-join optimizer bug
subselects(Vadim)
SY, Serj
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
Unfortunately I simply don't have time to implement any of the nicer suggestions
for how this should work. I wish I did...
self-join optimizer bug
subselects(Vadim)
Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775
Import Notes
Resolved by subject fallback
max tuple length settings(Darren & Peter)
The last I saw, we agreed (on the client side) to leave the current
settings for 8k tuples.PS: I'm having to commute to London all this week, so I'm not getting the
time to do anything :-(Hopefully it should ease after this Friday.
--
Peter T Mount petermount@earthling.net or pmount@maidast.demon.co.uk
Know the feeling... I commute to London every day :-( (except when I
work at home...)
Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775
Import Notes
Resolved by subject fallback
Where can i get it ?
Beta is feb1. Copy on ftp.postgresql.org now.
On Wed, 21 Jan 1998, Bruce Momjian wrote:
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
self-join optimizer bug
subselects(Vadim)SY, Serj
--
Bruce Momjian
maillist@candle.pha.pa.us
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)Unfortunately I simply don't have time to implement any of the nicer suggestions
for how this should work. I wish I did...
OK, what are we doing the .psqlrc. Can you send the old patch, or are
we dropping it for 6.3?
--
Bruce Momjian
maillist@candle.pha.pa.us
On Wed, 21 Jan 1998, Bruce Momjian wrote:
Here they are:
---------------------------------------------------------------------------GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)The last I saw, we agreed (on the client side) to leave the current
settings for 8k tuples.
I thought we were increasing the client size to the maximum value
allowable for any backend.
pg_user defaults to world-readable until passwords used(Todd)
psql .psqlrc file startup(Andrew)
self-join optimizer bug
subselects(Vadim)PS: I'm having to commute to London all this week, so I'm not getting the
time to do anything :-(Hopefully it should ease after this Friday.
--
Peter T Mount petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk
--
Bruce Momjian
maillist@candle.pha.pa.us
Where can i get it ?
Beta is feb1. Copy on ftp.postgresql.org now.
-rw-r--r-- 1 1005 96 2858711 Jan 16 08:03
postgresql.snapshot.tar.gz
Is it, or not ?
--
SY, Serj
On Thu, 22 Jan 1998, Serj wrote:
Where can i get it ?
Beta is feb1. Copy on ftp.postgresql.org now.
-rw-r--r-- 1 1005 96 2858711 Jan 16 08:03
postgresql.snapshot.tar.gzIs it, or not ?
It is purely a alpha copy, meant for testing purposes only, until Feb
1st...expect the new one coming out on Friday to have major changes in it
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
psql .psqlrc file startup(Andrew)
Unfortunately I simply don't have time to implement any of the nicer suggestions
for how this should work. I wish I did...OK, what are we doing the .psqlrc. Can you send the old patch, or are
we dropping it for 6.3?--
Bruce Momjian
maillist@candle.pha.pa.us
Here's the patch I supplied before:
*** src/bin/psql/psql.c.orig Fri Jun 20 21:54:31 1997
--- src/bin/psql/psql.c Fri Jun 20 22:23:49 1997
***************
*** 1598,1603 ****
--- 1598,1605 ----
bool singleSlashCmd = 0;
int c;+ char *home = NULL; /* Used to store $HOME */
+
memset(&settings, 0, sizeof settings);
settings.opt.align = 1;
settings.opt.header = 1;
***************
*** 1728,1733 ****
--- 1730,1760 ----
printf(" type \\g or terminate with semicolon to execute query\n");
printf(" You are currently connected to the database: %s\n\n", dbname);
}
+
+ /*
+ * 20.06.97 ACRM See if we've got a /etc/psqlrc or .psqlrc file
+ */
+ if(!access("/etc/psqlrc",R_OK))
+ HandleSlashCmds(&settings, "\\i /etc/psqlrc", "");
+ if((home = getenv("HOME"))!=NULL) {
+ char *psqlrc = NULL,
+ *line = NULL;
+
+ if((psqlrc = (char *)malloc(strlen(home) + 10))!=NULL) {
+ sprintf(psqlrc, "%s/.psqlrc", home);
+ if(!access(psqlrc, R_OK)) {
+ if((line = (char *)malloc(strlen(psqlrc) + 5))!=NULL) {
+ sprintf(line, "\\i %s", psqlrc);
+ HandleSlashCmds(&settings, line, "");
+ free(line);
+ }
+ }
+ free(psqlrc);
+ }
+ }
+ /* End of check for psqlrc files */
+
+
if (qfilename || singleSlashCmd) {
/*
* read in a file full of queries instead of reading in queriesAndrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775
Import Notes
Resolved by subject fallback
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
self-join optimizer bug
subselects(Vadim)
As far as I know, none of these are ready for 6.3, which is due on
Sunday. What is the game plan, folks?
And the tools/RELEASE_CHANGES files have not been updated. I
will do the FAQ, TODO, HISTORY files.
--
Bruce Momjian
maillist@candle.pha.pa.us
Import Notes
Resolved by subject fallback
Bruce Momjian wrote:
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
self-join optimizer bug
^^^^^^^^^^^^^^^^^^^^^^^
Test case, please.
subselects(Vadim)
As far as I know, none of these are ready for 6.3, which is due on
^^^ beta
Sunday. What is the game plan, folks?
I'm working...
Vadim
On Fri, 30 Jan 1998, Bruce Momjian wrote:
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
self-join optimizer bug
subselects(Vadim)As far as I know, none of these are ready for 6.3, which is due on
Sunday. What is the game plan, folks?
"bugs" can be fixed up to RELEASE date, which covers 4 of the
above...
And the tools/RELEASE_CHANGES files have not been updated. I
will do the FAQ, TODO, HISTORY files.
I believe I'm supposed to be handling the RELEASE_CHANGES
file...will take a look into that over the next week or so...its a month
before the RELEASE :)
On Fri, 30 Jan 1998, Vadim B. Mikheev wrote:
Bruce Momjian wrote:
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
self-join optimizer bug^^^^^^^^^^^^^^^^^^^^^^^
Test case, please.
I'm not sure if this is an example of the self-join bug mentioned above
or just an example of an "exceptional" computing challenge. I repost
the example so that those of you who understand what's going on can
judge for yourself.
On Fri, 30 Jan 1998, Bruce Momjian wrote:
GROUP BY bug of duplicates
GROUP BY nulls bug
ORDER BY nulls(Vadim?)
many OR's exhaust optimizer memory(Vadim?)
max tuple length settings(Darren & Peter)
pg_user defaults to world-readable until passwords used(Todd)
self-join optimizer bug
subselects(Vadim)As far as I know, none of these are ready for 6.3, which is due on
Sunday. What is the game plan, folks?"bugs" can be fixed up to RELEASE date, which covers 4 of the
above...And the tools/RELEASE_CHANGES files have not been updated. I
will do the FAQ, TODO, HISTORY files.I believe I'm supposed to be handling the RELEASE_CHANGES
file...will take a look into that over the next week or so...its a month
before the RELEASE :)
This is 6.3 beta. IMHO, the stuff has to say at least 6.3, if not 6.3
beta by Feb 1. Don't want beta users saying they have 6.2.1.
--
Bruce Momjian
maillist@candle.pha.pa.us