[ADMIN] 6.5.3/doesn't recognize localhost in pg_hba.conf

Started by Larry Rosenmanover 26 years ago1 messagesgeneral

Jump to latest

Larry Rosenman

ler@lerami.lerctr.org

over 26 years ago

HELP!

Just recompiled PostgreSQL 6.5.3 on UnixWare 7.1.0 on a P-III.

Followed all the steps, but when I try to connect, it says
that there is NO pg_hba.conf entry, but there is.

Anyone else see this?

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

************

----- End of forwarded message from Larry Rosenman -----

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

From bouncefilter Sat Nov 13 16:32:22 1999
Received: from lerami.lerctr.org (ler@lerami.lerctr.org [207.158.72.11])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA09748
for <pgsql-general@postgresql.org>;
Sat, 13 Nov 1999 16:31:33 -0500 (EST)
(envelope-from ler@lerami.lerctr.org)
Received: (from ler@localhost)
by lerami.lerctr.org (8.10.0.Beta6/8.10.0.Beta6/19991109) id
dADLVVM03316
for pgsql-general@postgresql.org; Sat, 13 Nov 1999 15:31:31 -0600 (CST)
From: Larry Rosenman <ler@lerami.lerctr.org>
Message-Id: <199911132131.dADLVVM03316@lerami.lerctr.org>
Subject: [ADMIN] 6.5.3/doesn't recognize localhost in pg_hba.conf (fwd)
To: pgsql-general@postgresql.org
Date: Sat, 13 Nov 1999 15:31:30 -0600 (CST)
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Just trying to get answers....

LER
----- Forwarded message from Larry Rosenman -----

From bouncefilter Sat Nov 13 23:56:27 1999
Received: from mcs.anl.gov (cliff-32.mcs.anl.gov [140.221.32.31])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA60991
for <pgsql-general@postgreSQL.org>;
Sat, 13 Nov 1999 23:56:14 -0500 (EST)
(envelope-from selkovjr@xnet.com)
Received: from antares (antares.mcs.anl.gov [140.221.9.6])
by mcs.anl.gov (8.9.3/8.9.3) with ESMTP id WAA353554;
Sat, 13 Nov 1999 22:54:37 -0600
Message-Id: <199911140456.WAA13708@antares>
To: Manuel Weindorf <weindorf@ipf.uni-karlsruhe.de>,
pgsql-general@postgreSQL.org
From: "Gene Selkov, Jr." <selkovjr@mcs.anl.gov>
Subject: Re: [GENERAL] Problem with C functions ?
In-Reply-To: Your message of "Thu, 11 Nov 1999 14:40:35 +0100."
<382AC753.505410CE@ipf.uni-karlsruhe.de>
Date: Sat, 13 Nov 1999 23:56:25 -0500
Sender: selkovjr@xnet.com

[having found this topic irrelevant to INTERFACES, I'm not posting my reply there]

Hi there,

I compiled a C-funtion to compute the azimuth of a LSEG but the function
never
returns the correct value

double ori;
....
return( ori );

The right way to do it would be:

#include "postgres.h"
#include "utils/palloc.h"

float64 ori = (float64) palloc(sizeof(float64data));

*ori = (float64) .... /* double type expression */

return ( ori );
}

--Gene

From bouncefilter Sun Nov 14 00:44:28 1999
Received: from mcs.anl.gov (cliff-32.mcs.anl.gov [140.221.32.31])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA70842
for <pgsql-general@postgreSQL.org>;
Sun, 14 Nov 1999 00:44:25 -0500 (EST)
(envelope-from selkovjr@xnet.com)
Received: from antares (antares.mcs.anl.gov [140.221.9.6])
by mcs.anl.gov (8.9.3/8.9.3) with ESMTP id XAA90374;
Sat, 13 Nov 1999 23:42:43 -0600
Message-Id: <199911140544.XAA14453@antares>
To: Peter Eisentraut <peter_e@gmx.net>, vandewal@dhc.net,
pgsql-general@postgreSQL.org
From: "Gene Selkov, Jr." <selkovjr@mcs.anl.gov>
Subject: Re: [GENERAL] does GIS DMS data type already exist?
In-Reply-To: Your message of "Sat, 13 Nov 1999 19:03:15 +0100."
<Pine.GSO.4.02A.9911131858300.606-100000@Val.DoCS.UU.SE>
Date: Sun, 14 Nov 1999 00:44:31 -0500
Sender: selkovjr@xnet.com

On Sat, 13 Nov 1999 Peter Eisentraut wrote:

Funny, just today I was thinking "Hmm, a DMS data type might be useful to
implement."

Right now there is no such thing (in the official sources anyway). Unless
you want to walk the long path of making up your own datatype (which we'd
appreciate, of course),

The path is not very long if you just want to solve the problem by
writing an extension in the form of a shared object. You'll have to
write a couple screenfuls of c code, a simple Makefile and a sql
script to craft your data type into the postgres schema. An
entry-level c student with two days of experience can easily do
this. I agree the documentation on extensions is somewhat lean, but I
can guide everyone wishing to write their own types through the entire
process. Contact me directly, we'll do a few iterations, then report
to the list.

However, if you plan on making your type a backend built-in or if you
want to make a configurable and portable extension, you and I could
use some help. I only know how to build shared objects for linux,
freebsd and sun/solaris. Someone's got to know how to add a built-in
type: there were much fewer types at the time when postgres left
Berkeley.

you might be better off creating a conversion
function or two in the backend or letting the frontend handle the
conversion.

doing the conversion in the front end seems like a plausible idea if
you pick an adequate base type to represent your data. I would
advocate using the box type *both* for locations and rectangular areas
in geography -- that will account for efficient indexing and uniform
usage. Same idea if you build your own type -- make it equivalent to
the box type. One can also try and derive the type from the built-in
by writing special i/o and interface functions.

On second thought, perhaps you could abuse the time datatype. Of course
it's more like HMS, but perhaps you could make a spin off.

the time datatype is ok as long as your degrees are between zero
and 24. also, you won't be able to do the geometrical indexing on
it. Like I said, do your own, it's going to be fun!

--Gene

On Sat, 13 Nov 1999 vandewal@dhc.net wrote:

Hey,

I am builing a system that is going to be dealing with a large
amount of GIS (geographic) data from USGS. Some of their data
provides lattitude and longitude in the DMS (degrees minnutes seconds)
format, other provides lat/lon in decimal format. The decimal is
obviously not a problem for postgres, but the DMS is. I am going to
need to be doing queries based on the DMS data, and will need it
treated as numeric instead of just a text string.

Soooo (to get to my question already!) what I want to know is
whether anyone else has already coded up a data type to do this
kind of thing or whether I just have to do it myself.

I search around but didn't find one.

Thanks for you time.

dv

// David E. Vandewalle | The best diplomat I know is a fully
// vandewal@skyblue.com | activated phaser bank.
// david.e.vandewalle@lmco.com | -- Scotty

************

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

************

From bouncefilter Sun Nov 14 17:08:39 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA83180
for <pgsql-general@postgresql.org>;
Sun, 14 Nov 1999 17:08:36 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1)
id 11n7pD-0006GC-00; Sun, 14 Nov 1999 22:08:43 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11n7oz-0001Hw-00; Sun, 14 Nov 1999 22:08:29 +0000
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
To: ler@lerami.lerctr.org (Larry Rosenman)
Date: Sun, 14 Nov 1999 22:08:29 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Cc: pgsql-general@postgresql.org
Reply-To: prlw1@cam.ac.uk
In-Reply-To: <199911132131.dADLVVM03316@lerami.lerctr.org> from "Larry
Rosenman" at Nov 13, 99 03:31:30 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11n7oz-0001Hw-00@quartz.newn.cam.ac.uk>

Larry Rosenman wrote:

Just trying to get answers....

LER

HELP!

Just recompiled PostgreSQL 6.5.3 on UnixWare 7.1.0 on a P-III.

Followed all the steps, but when I try to connect, it says
that there is NO pg_hba.conf entry, but there is.

Anyone else see this?

Does $PGDATA/pg_hba.conf exist on your system? Did you run initdb?

Cheers,

Patrick

From bouncefilter Sun Nov 14 17:19:40 1999
Received: from lerami.lerctr.org (ler@lerami.lerctr.org [207.158.72.11])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA84589
for <pgsql-general@postgreSQL.org>;
Sun, 14 Nov 1999 17:19:17 -0500 (EST)
(envelope-from ler@lerami.lerctr.org)
Received: (from ler@localhost)
by lerami.lerctr.org (8.10.0.Beta6/8.10.0.Beta6/19991109) id
dAEMJ9l14076; Sun, 14 Nov 1999 16:19:09 -0600 (CST)
From: Larry Rosenman <ler@lerami.lerctr.org>
Message-Id: <199911142219.dAEMJ9l14076@lerami.lerctr.org>
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
In-Reply-To: <E11n7oz-0001Hw-00@quartz.newn.cam.ac.uk> from Patrick Welche at
"Nov 14, 1999 10: 8:29 pm"
To: prlw1@cam.ac.uk
Date: Sun, 14 Nov 1999 16:19:09 -0600 (CST)
Cc: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Yes, and Yes.

# su - postgres

$ id -a
uid=400(postgres) gid=400(postgres) groups=400(postgres)
$ ls -l $PGDATA/pg_hba.conf
-r-------- 1 postgres postgres 5192 Nov 13 15:59 /usr/local/pgsql/data/pg_hba.conf
$ postmaster -i&
[1]: http://www.postgresql.org/docs/programmer/xplang1501.htm
$ psql
No pg_hba.conf entry for host localhost, user postgres, database postgres
Connection to database 'postgres' failed.
No pg_hba.conf entry for host localhost, user postgres, database postgres
$ ls -laR $PGDATA
total 92
drwx------ 3 postgres postgres 1024 Nov 13 15:59 .
drwxr-xr-x 8 postgres postgres 1024 Nov 13 16:01 ..
-rw------- 1 postgres postgres 4 Nov 13 15:59 PG_VERSION
drwx------ 3 postgres postgres 96 Nov 13 15:58 base
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_database
-r-------- 1 postgres postgres 3407 Nov 13 15:59 pg_geqo.sample
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_group
-r-------- 1 postgres postgres 5192 Nov 13 15:59 pg_hba.conf
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_log
-rw-rw-rw- 1 postgres postgres 53 Nov 13 15:59 pg_pwd
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_shadow
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_variable

/usr/local/pgsql/data/base:
total 6
drwx------ 3 postgres postgres 96 Nov 13 15:58 .
drwx------ 3 postgres postgres 1024 Nov 13 15:59 ..
drwx------ 2 postgres postgres 2048 Nov 13 15:59 template1

/usr/local/pgsql/data/base/template1:
total 1878
drwx------ 2 postgres postgres 2048 Nov 13 15:59 .
drwx------ 3 postgres postgres 96 Nov 13 15:58 ..
-rw------- 1 postgres postgres 4 Nov 13 15:59 PG_VERSION
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_aggregate
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_am
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_amop
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_amproc
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_attrdef
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_attrdef_adrelid_index
-rw------- 1 postgres postgres 49152 Nov 13 15:59 pg_attribute
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_attribute_attrelid_index
-rw------- 1 postgres postgres 49152 Nov 13 15:59 pg_attribute_relid_attnam_index
-rw------- 1 postgres postgres 32768 Nov 13 15:59 pg_attribute_relid_attnum_index
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_class
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_class_oid_index
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_class_relname_index
-rw------- 1 postgres postgres 65536 Nov 13 15:59 pg_description
-rw------- 1 postgres postgres 40960 Nov 13 15:59 pg_description_objoid_index
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_index
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_indexes
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_inheritproc
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_inherits
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_ipl
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_language
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_listener
-rw------- 1 postgres postgres 8192 Nov 13 15:59 pg_opclass
-rw------- 1 postgres postgres 65536 Nov 13 15:59 pg_operator
-rw------- 1 postgres postgres 172032 Nov 13 15:59 pg_proc
-rw------- 1 postgres postgres 40960 Nov 13 15:59 pg_proc_oid_index
-rw------- 1 postgres postgres 139264 Nov 13 15:59 pg_proc_proname_narg_type_index
-rw------- 1 postgres postgres 57344 Nov 13 15:59 pg_proc_prosrc_index
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_relcheck
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_relcheck_rcrelid_index
-rw------- 1 postgres postgres 24576 Nov 13 15:59 pg_rewrite
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_rules
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_statistic
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_tables
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_trigger
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_trigger_tgrelid_index
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_type
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_type_oid_index
-rw------- 1 postgres postgres 16384 Nov 13 15:59 pg_type_typname_index
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_user
-rw------- 1 postgres postgres 0 Nov 13 15:59 pg_views
$ tail -10 $PGDATA/pg_hba.conf
# The above would allow users from 192.168.0.x hosts to connect to any
# database, but if Ident says the user is "bryanh" and he requests to
# connect as PostgreSQL user "guest1", the connection is only allowed if
# there is an entry for map "omicron" in pg_ident.conf that says "bryanh" is
# allowed to connect as "guest1".

# By default, allow anything over UNIX domain sockets and localhost.

local all trust
host all 127.0.0.1 255.255.255.255 trust
$

Patrick Welche wrote:

Larry Rosenman wrote:

Just trying to get answers....

LER

HELP!

Just recompiled PostgreSQL 6.5.3 on UnixWare 7.1.0 on a P-III.

Followed all the steps, but when I try to connect, it says
that there is NO pg_hba.conf entry, but there is.

Anyone else see this?

Does $PGDATA/pg_hba.conf exist on your system? Did you run initdb?

Cheers,

Patrick

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

From bouncefilter Sun Nov 14 17:25:39 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA85623
for <pgsql-general@postgresql.org>;
Sun, 14 Nov 1999 17:25:30 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1)
id 11n85i-0006Gh-00; Sun, 14 Nov 1999 22:25:46 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11n85T-0001J0-00; Sun, 14 Nov 1999 22:25:31 +0000
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
To: ler@lerami.lerctr.org (Larry Rosenman)
Date: Sun, 14 Nov 1999 22:25:31 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Cc: pgsql-general@postgresql.org
Reply-To: prlw1@cam.ac.uk
In-Reply-To: <199911142219.dAEMJ9l14076@lerami.lerctr.org> from "Larry
Rosenman" at Nov 14, 99 04:19:09 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11n85T-0001J0-00@quartz.newn.cam.ac.uk>

Larry Rosenman wrote:

Yes, and Yes.

...

$ psql
No pg_hba.conf entry for host localhost, user postgres, database postgres
Connection to database 'postgres' failed.
No pg_hba.conf entry for host localhost, user postgres, database postgres

...

$ ls -laR $PGDATA

...

/usr/local/pgsql/data/base:
total 6
drwx------ 3 postgres postgres 96 Nov 13 15:58 .
drwx------ 3 postgres postgres 1024 Nov 13 15:59 ..
drwx------ 2 postgres postgres 2048 Nov 13 15:59 template1

How about

psql template1

Cheers,

Patrick

From bouncefilter Sun Nov 14 17:50:39 1999
Received: from lerami.lerctr.org (ler@lerami.lerctr.org [207.158.72.11])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA89288
for <pgsql-general@postgreSQL.org>;
Sun, 14 Nov 1999 17:50:10 -0500 (EST)
(envelope-from ler@lerami.lerctr.org)
Received: (from ler@localhost)
by lerami.lerctr.org (8.10.0.Beta6/8.10.0.Beta6/19991109) id
dAEMo7u19178; Sun, 14 Nov 1999 16:50:07 -0600 (CST)
From: Larry Rosenman <ler@lerami.lerctr.org>
Message-Id: <199911142250.dAEMo7u19178@lerami.lerctr.org>
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
In-Reply-To: <E11n85T-0001J0-00@quartz.newn.cam.ac.uk> from Patrick Welche at
"Nov 14, 1999 10:25:31 pm"
To: prlw1@cam.ac.uk
Date: Sun, 14 Nov 1999 16:50:07 -0600 (CST)
Cc: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Same result.

Patrick Welche wrote:

Larry Rosenman wrote:

Yes, and Yes.

...

$ psql
No pg_hba.conf entry for host localhost, user postgres, database postgres
Connection to database 'postgres' failed.
No pg_hba.conf entry for host localhost, user postgres, database postgres

...

$ ls -laR $PGDATA

...

/usr/local/pgsql/data/base:
total 6
drwx------ 3 postgres postgres 96 Nov 13 15:58 .
drwx------ 3 postgres postgres 1024 Nov 13 15:59 ..
drwx------ 2 postgres postgres 2048 Nov 13 15:59 template1

How about

psql template1

?

Cheers,

Patrick

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

From bouncefilter Sun Nov 14 17:54:39 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA89553
for <pgsql-general@postgresql.org>;
Sun, 14 Nov 1999 17:54:02 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1)
id 11n8XJ-0006HM-00; Sun, 14 Nov 1999 22:54:17 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11n8X4-0001L2-00; Sun, 14 Nov 1999 22:54:02 +0000
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
To: ler@lerami.lerctr.org (Larry Rosenman)
Date: Sun, 14 Nov 1999 22:54:02 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Cc: pgsql-general@postgresql.org
Reply-To: prlw1@cam.ac.uk
In-Reply-To: <199911142250.dAEMo7u19178@lerami.lerctr.org> from "Larry
Rosenman" at Nov 14, 99 04:50:07 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11n8X4-0001L2-00@quartz.newn.cam.ac.uk>

Larry Rosenman wrote:

Same result.

OK, still guessing... How about

psql -h 127.0.0.1 template1

Cheers,

Patrick

From bouncefilter Sun Nov 14 18:07:39 1999
Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207])
by hub.org (8.9.3/8.9.3) with SMTP id SAA91972
for <pgsql-general@postgreSQL.org>;
Sun, 14 Nov 1999 18:07:07 -0500 (EST)
(envelope-from tesio@easynet.fr)
Received: (qmail 15840 invoked from network); 14 Nov 1999 23:07:06 -0000
Received: from mailgate2.easynet.fr (192.168.1.3)
by mailserver.easynet.fr with QMQP; 14 Nov 1999 23:07:06 -0000
Received: from pop-nice-235.pops.easynet.fr (HELO atesio) (195.114.95.235)
by mrelay2.easynet.fr with SMTP; 14 Nov 1999 23:07:05 -0000
Message-ID: <004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
From: "Alain TESIO" <tesio@easynet.fr>
To: <pgsql-general@postgreSQL.org>
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
Subject: RPM 6.5.3
Date: Mon, 15 Nov 1999 00:08:29 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

Hello,

I installed these RPM (all of the files available on the ftp site)
on RedHat 6.0 without any error reported and it looks like
some parts are missing.
No $PGDATA variable is set for the user postgres and most
usual files in this directory are missing are missing.
Is there any fix or should I get the tgz files ?

Alain

From bouncefilter Sun Nov 14 18:13:39 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA92851;
Sun, 14 Nov 1999 18:13:16 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id TAA90257;
Sun, 14 Nov 1999 19:13:28 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Sun, 14 Nov 1999 19:13:27 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
cc: pgsql-hackers@postgresql.org
Subject: Looks like hell, but ...
Message-ID: <Pine.BSF.4.10.9911141908330.75865-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

http://www.pgsql.com/app-index ...

Its a start, at least. I have to add 'update' facilities for ppl to edit
records, and it *looks* like hell, but its a start...

I'm concentrating on apps first, and, eventually, its going to include
'Usage of' records...

All input has to be approved before it becomes live...and it will
eventually contain information similar to what FreshMeat provides
(dependancies, license, etc)...

Check it out, add content and watch it evolve...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Sun Nov 14 18:33:40 1999
Received: from lerami.lerctr.org (ler@lerami.lerctr.org [207.158.72.11])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA96127;
Sun, 14 Nov 1999 18:32:55 -0500 (EST)
(envelope-from ler@lerami.lerctr.org)
Received: (from ler@localhost)
by lerami.lerctr.org (8.10.0.Beta6/8.10.0.Beta6/19991109) id
dAENWq023681; Sun, 14 Nov 1999 17:32:52 -0600 (CST)
From: Larry Rosenman <ler@lerami.lerctr.org>
Message-Id: <199911142332.dAENWq023681@lerami.lerctr.org>
Subject: Re: [GENERAL] [ADMIN] 6.5.3/doesn't recognize localhost in
pg_hba.conf (fwd)
In-Reply-To: <E11n8X4-0001L2-00@quartz.newn.cam.ac.uk> from Patrick Welche at
"Nov 14, 1999 10:54: 2 pm"
To: prlw1@cam.ac.uk
Date: Sun, 14 Nov 1999 17:32:52 -0600 (CST)
Cc: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org,
pgsql-admin@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

That works. The other gent traced it, and I placed a debug statement.

It appears that on AF_LOCAL sockets on this release/ptf level
sa_family is NOT set to AF_LOCAL.

I'll file a bug with SCO.

$ psql -h lerami2 -p 5432 template1
raddr->sa.sa_family = 2
Welcome to the POSTGRESQL interactive sql monitor:
Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 6.5.3 on i586-pc-unixware7.1.0, compiled by cc ]

type \? for help on slash commands
type \q to quit
type \g or terminate with semicolon to execute query
You are currently connected to the database: template1

template1=> EOF
$ psql
raddr->sa.sa_family = 0
No pg_hba.conf entry for host localhost, user postgres, database postgres
Connection to database 'postgres' failed.
No pg_hba.conf entry for host localhost, user postgres, database postgres
$

Patrick Welche wrote:

Larry Rosenman wrote:

Same result.

OK, still guessing... How about

psql -h 127.0.0.1 template1

?

Cheers,

Patrick

************

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

From bouncefilter Sun Nov 14 10:53:34 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id KAA41118
for pgsql-general@postgresql.org; Sun, 14 Nov 1999 10:52:58 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
Message-ID: <38302C56.385744F1@journal_of_the_hyperlinked.org>
Date: Mon, 15 Nov 1999 15:52:54 +0000
From: "j's hyperlinked organisation" <joho@journal_of_the_hyperlinked.org>
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
X-Newsgroups: comp.databases.postgresql.questions
Subject: Re: PostgreSQL server for Win95 machine
References: <7vtg03$rn67@imsp212.netvigator.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: 14 Nov 1999 14:52:56 GMT, userai91.netscapeonline.co.uk
Lines: 16
X-Report: Report abuse to abuse@netscapeonline.co.uk
To: pgsql-questions@postgresql.org

How is the Windows machine communicating with the Linux Box?

HK Woo wrote:

Hi,

I have set up the PostgreSQL on Linux machine and I have download the ODBC
driver and install it in my win95 machine. However, I don't how to setup the
Linux machine so that I can use the SQL server at my win95 machine.

Please suggest a procedure for the configruation.

Thank You!

HK Woo

From bouncefilter Mon Nov 15 12:13:52 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA27662
for <pgsql-hackers@postgresql.org>;
Mon, 15 Nov 1999 12:13:27 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.8.7/8.8.5) with ESMTP id MAA19195;
Mon, 15 Nov 1999 12:12:54 -0500
Message-ID: <38303F0F.90E320D@wgcr.org>
Date: Mon, 15 Nov 1999 12:12:47 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Looks like hell, but ...
References: <Pine.BSF.4.10.9911141908330.75865-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The Hermit Hacker wrote:

Check it out, add content and watch it evolve...

A good start, Marc. I added the interesting package called onShore
Timesheet -- looks like your entry form covers most of the bases.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Mon Nov 15 12:51:53 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA32678
for <pgsql-hackers@postgresql.org>;
Mon, 15 Nov 1999 12:50:55 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id NAA97214;
Mon, 15 Nov 1999 13:50:34 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 15 Nov 1999 13:50:33 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Lamar Owen <lamar.owen@wgcr.org>
cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Looks like hell, but ...
In-Reply-To: <38303F0F.90E320D@wgcr.org>
Message-ID: <Pine.BSF.4.10.9911151349390.75865-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 15 Nov 1999, Lamar Owen wrote:

The Hermit Hacker wrote:

Check it out, add content and watch it evolve...

A good start, Marc. I added the interesting package called onShore
Timesheet -- looks like your entry form covers most of the bases.

Thanks...I've been populating it with what I can readily find (through
freshmeat so far), but I definitely don't know everything that is out
there :)

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 15 13:16:53 1999
Received: from loopy.berkhirt.com (loopy.berkhirt.com [209.220.85.54])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA36443
for <pgsql-hackers@postgreSQL.org>;
Mon, 15 Nov 1999 13:16:13 -0500 (EST)
(envelope-from bhirt@loopy.berkhirt.com)
Received: (from bhirt@localhost)
by loopy.berkhirt.com (8.9.3/8.8.7) id MAA25428;
Mon, 15 Nov 1999 12:14:26 -0600
Date: Mon, 15 Nov 1999 12:14:26 -0600
From: Brian Hirt <bhirt@mobygames.com>
To: The Hermit Hacker <scrappy@hub.org>
Cc: Lamar Owen <lamar.owen@wgcr.org>, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Looks like hell, but ...
Message-ID: <19991115121426.A25286@loopy.berkhirt.com>
Reply-To: bhirt@mobygames.com
References: <38303F0F.90E320D@wgcr.org>
<Pine.BSF.4.10.9911151349390.75865-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4us
In-Reply-To: <Pine.BSF.4.10.9911151349390.75865-100000@thelab.hub.org>;
from The Hermit Hacker on Mon, Nov 15, 1999 at 01:50:33PM -0400
X-PC-Gaming: http://www.mobygames.com/

On Mon, Nov 15, 1999 at 01:50:33PM -0400, The Hermit Hacker wrote:

Thanks...I've been populating it with what I can readily find (through
freshmeat so far), but I definitely don't know everything that is out
there :)

I'm not sure if you worked on the user gallery also, but I like that as
well. I do have one suggestion and a comment. It would be nice if a
description of the project could be included. I'd like to browse through
some of the other project but clicking on each one and seeing a description
of the project would help decide which ones to look at.

My comment is that there appears to be no maintainer of the gallery. There
is a project name testing_shit. I counted at least 10 duplicate entries and
many that are obvously incomplete. Do you want any help with the gallery?

-brian

--
The world's most ambitious and comprehensive PC game database project.

http://www.mobygames.com

From bouncefilter Mon Nov 15 13:43:53 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA39945
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 13:43:41 -0500 (EST) (envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id LAA23857
for <pgsql-general@postgreSQL.org>; Mon, 15 Nov 1999 11:44:01 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: pgsql-general@postgreSQL.org
Subject: vacuum analyze works on tables, but not on entire database
Date: Mon, 15 Nov 1999 11:38:19 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
<004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
In-Reply-To: <004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
MIME-Version: 1.0
Message-Id: <99111511415501.15505@stilborne>
Content-Transfer-Encoding: 8bit

hi...

something bizarre (at least to my experience) has started occuring in our
production database:

i can run vacuum analyze on each and every table INDIVIDUALLY no problem.. but
when i vacume analyze the whole db (by going into psql and uttering 'vacuum
analyze;') it dies.

any thoughts?

its not a huge problem, except that vacuum anlyzing each of the 40 tables is a
little cumbersome.

--
Aaron J. Seigo
Sys Admin

From bouncefilter Mon Nov 15 14:27:57 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA45692
for <pgsql-hackers@postgreSQL.org>;
Mon, 15 Nov 1999 14:27:41 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA97842;
Mon, 15 Nov 1999 15:26:57 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 15 Nov 1999 15:26:56 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Brian Hirt <bhirt@mobygames.com>
cc: Lamar Owen <lamar.owen@wgcr.org>, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Looks like hell, but ...
In-Reply-To: <19991115121426.A25286@loopy.berkhirt.com>
Message-ID: <Pine.BSF.4.10.9911151524190.75865-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 15 Nov 1999, Brian Hirt wrote:

On Mon, Nov 15, 1999 at 01:50:33PM -0400, The Hermit Hacker wrote:

Thanks...I've been populating it with what I can readily find (through
freshmeat so far), but I definitely don't know everything that is out
there :)

I'm not sure if you worked on the user gallery also, but I like that as
well. I do have one suggestion and a comment. It would be nice if a
description of the project could be included. I'd like to browse through
some of the other project but clicking on each one and seeing a description
of the project would help decide which ones to look at.

My comment is that there appears to be no maintainer of the gallery. There
is a project name testing_shit. I counted at least 10 duplicate entries and
many that are obvously incomplete. Do you want any help with the gallery?

Now that I have what looks like a nice format (technically, not visually)
for the apps, I'm going to redo the user gallery itself also...assuming
nothing comes up later tonight, will hopefully have most of it converted
then...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 15 15:03:54 1999
Received: from mail3.mgfairfax.rr.com (fe3.southeast.rr.com [24.93.67.50])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA54124
for <pgsql-general@postgresql.org>;
Mon, 15 Nov 1999 15:03:28 -0500 (EST)
(envelope-from anon@mgfairfax.rr.com)
Received: from rsdevelop ([24.28.195.168]) by mail3.mgfairfax.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Mon, 15 Nov 1999 14:57:35 -0500
Message-ID: <00f301bf2fa4$b8a0a120$0200a8c0@rsdevelop>
From: "Bruce Bantos" <anon@mgfairfax.rr.com>
To: <pgsql-general@postgresql.org>
Subject: RPM vs. tar for 6.5.3
Date: Mon, 15 Nov 1999 15:05:10 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

I have just finished installing the 6.5.3 tar on my linux database server.
After testing, I have found PostgreSQL to be an excellent database. I was
especially impressed by the full feature set that is available. My thanks to
everyone who has contributed to this project.

I now want to deploy the client to a few workstations, and install the
server on another linux server. What is the best way to deploy this version?
The last time I tried the 6.5.2 RPM's, there where a few things missing, so
I removed them and installed the tar. Are the 6.5.3 RPM's complete? Do I
give up anything by using the RPM's? Is it advisable to install another
server with the RPM's, or is administration hampered if I do this as opposed
to building from the source?

Thanks for your help.

From bouncefilter Mon Nov 15 16:02:54 1999
Received: from ws-173.e-connectsolutions.net (ws-173.e-connectsolutions.net
[209.124.91.173]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA61933
for <pgsql-general@postgresql.org>;
Mon, 15 Nov 1999 16:02:31 -0500 (EST)
(envelope-from john@ws-173.e-connectsolutions.net)
Received: (from john@localhost)
by ws-173.e-connectsolutions.net (8.9.3/8.9.3) id PAA30714
for pgsql-general@postgresql.org; Mon, 15 Nov 1999 15:57:46 -0500
Date: Mon, 15 Nov 1999 15:57:46 -0500
From: John Hyland <john@e-connectsolutions.com>
To: pgsql-general@postgresql.org
Subject: type creation question
Message-ID: <19991115155746.A30600@e-connectsolutions.com>
Mail-Followup-To: pgsql-general@postgresql.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
Organization: Five Star Communications
Title: SysAdmin

Hi, I'm John Hyland and I just joined the list.

Briefly, I am attempting to create a number of types that are essentially the
text type by different names. The command I'm using to do this is

CREATE TYPE mytype
(INPUT = textin, OUTPUT = textout, INTERNALLENGTH = VARIABLE);

When I do this I get an error that reads

ERROR: TypeCreate: function 'array_in(opaque)' does not exist

I'm using PostgreSQL 6.5.2

Help?

(If anybody is curious as to why I would be doing this, I'm writing a web app
in PHP (4.0b2) for project management. Each different 'thing' that I'm keeping
track of (customers, sites, etc) has it's own table in the database. I want to
write one script to view any 'thing', one to edit any 'thing', one to add any
new 'thing', etc. The php scripts will know how to build the html by looking
at the data types, but to postgres it will all look like text).

--
John Hyland
SysAdmin, Programmer
e-Connect Solutions, Inc.

From bouncefilter Mon Nov 15 15:58:54 1999
Received: from guinness.urw.org (root@guinness.urw.org [209.32.194.52])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA61312
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 15:58:32 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from wookimus.net (chewie@wookimus.net [209.32.194.62])
by guinness.urw.org (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id OAA15238;
Mon, 15 Nov 1999 14:58:22 -0600
Date: Mon, 15 Nov 1999 14:58:22 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@guinness.urw.org
To: Bruce Bantos <anon@mgfairfax.rr.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] RPM vs. tar for 6.5.3
In-Reply-To: <00f301bf2fa4$b8a0a120$0200a8c0@rsdevelop>
Message-ID: <Pine.LNX.4.10.9911151450120.15225-100000@guinness.urw.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 15 Nov 1999, Bruce Bantos wrote:

BB> I now want to deploy the client to a few workstations, and install
BB> the server on another linux server. What is the best way to deploy
BB> this version? The last time I tried the 6.5.2 RPM's, there where a
BB> few things missing, so I removed them and installed the tar. Are
BB> the 6.5.3 RPM's complete? Do I give up anything by using the
BB> RPM's? Is it advisable to install another server with the RPM's,
BB> or is administration hampered if I do this as opposed to building
BB> from the source?

The only way is to install the RPM and find out. ;-) You may want to
install via tarball for security reasons and control reasons, but I've
found that if you're going to stick with the filesystem layout for a
particular distribution of Linux, the easiest way to do it is to install
the packages built for it. Another reason to install the tarball over an
RPM may be concurrency with the most recent version. By their nature,
packages always lag behind the source tarballs and patches.

It's up to you, really. What I see as a trend for system administrator's
policies is the eventual migration to "roll-your-own" binaries. For ease
of use and installation, immediate gratification, etc., go with RPM. For
configurability of the binary, control of the file-placement schema, and
security of the source code, "rolling-your-own" is most definitely the way
to go.

Chad

From bouncefilter Mon Nov 15 16:09:56 1999
Received: from iodynamics.com (IDENT:fozz@www.iodynamics.com [206.81.134.150])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA62760
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 16:09:55 -0500 (EST)
(envelope-from fozz@iodynamics.com)
Received: (from fozz@localhost) by iodynamics.com (8.9.3/8.9.3) id OAA02552;
Mon, 15 Nov 1999 14:09:07 -0700
Date: Mon, 15 Nov 1999 14:09:06 -0700
From: "Doran L. Barton" <fozz@iodynamics.com>
To: "Aaron J. Seigo" <aaron@gtv.ca>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] vacuum analyze works on tables,
but not on entire database
Message-ID: <19991115140906.C2513@iodynamics.com>
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
<004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
<99111511415501.15505@stilborne>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4us
In-Reply-To: <99111511415501.15505@stilborne>;
from Aaron J. Seigo on Mon, Nov 15, 1999 at 11:38:19AM -0700

Not long ago, Aaron J. Seigo proclaimed...

something bizarre (at least to my experience) has started occuring in our
production database:

i can run vacuum analyze on each and every table INDIVIDUALLY no problem.. but
when i vacume analyze the whole db (by going into psql and uttering 'vacuum
analyze;') it dies.

any thoughts?

its not a huge problem, except that vacuum anlyzing each of the 40 tables is a
little cumbersome.

Would you care to mutter something about the PG version you're running and
the platform and OS on which you're operating?
--
Doran L. Barton <fozz@iodynamics.com>
Iodynamics LLC -- "Internetworking the masses"
<URL:http://www.iodynamics.com/>

From bouncefilter Mon Nov 15 16:24:55 1999
Received: from ws-173.e-connectsolutions.net (ws-173.e-connectsolutions.net
[209.124.91.173]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA64781
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 16:24:01 -0500 (EST)
(envelope-from john@ws-173.e-connectsolutions.net)
Received: (from john@localhost)
by ws-173.e-connectsolutions.net (8.9.3/8.9.3) id QAA30758
for pgsql-general@postgreSQL.org; Mon, 15 Nov 1999 16:19:16 -0500
Date: Mon, 15 Nov 1999 16:19:16 -0500
From: John Hyland <john@5sc.net>
To: pgsql-general@postgreSQL.org
Subject: user-defined types question
Message-ID: <19991115161916.B30745@e-connectsolutions.com>
Mail-Followup-To: pgsql-general@postgreSQL.org
References: <199911152103.QAA61998@hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
In-Reply-To: <199911152103.QAA61998@hub.org>;
from owner-pgsql-general@postgreSQL.org on Mon, Nov 15, 1999 at
04:03:04PM -0500
Organization: Five Star Communications
Title: SysAdmin

Hi, I'm John Hyland and I just joined the list.

Briefly, I am attempting to create a number of types that are essentially the
text type by different names. The command I'm using to do this is

CREATE TYPE mytype
(INPUT = textin, OUTPUT = textout, INTERNALLENGTH = VARIABLE);

When I do this I get an error that reads

ERROR: TypeCreate: function 'array_in(opaque)' does not exist

I'm using PostgreSQL 6.5.2

Help?

--
John Hyland
SysAdmin, Programmer
e-Connect Solutions, Inc.

From bouncefilter Mon Nov 15 16:43:55 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA70278
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 16:43:32 -0500 (EST) (envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id OAA24206;
Mon, 15 Nov 1999 14:43:53 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: "Doran L. Barton" <fozz@iodynamics.com>
Subject: Re: [GENERAL] vacuum analyze works on tables,
but not on entire database
Date: Mon, 15 Nov 1999 14:27:48 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: pgsql-general@postgreSQL.org
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
<99111511415501.15505@stilborne>
<19991115140906.C2513@iodynamics.com>
In-Reply-To: <19991115140906.C2513@iodynamics.com>
MIME-Version: 1.0
Message-Id: <99111514415202.15505@stilborne>
Content-Transfer-Encoding: 8bit

On Mon, 15 Nov 1999, Doran L. Barton wrote:

Not long ago, Aaron J. Seigo proclaimed...

something bizarre (at least to my experience) has started occuring in our
production database:

i can run vacuum analyze on each and every table INDIVIDUALLY no problem.. but
when i vacume analyze the whole db (by going into psql and uttering 'vacuum
analyze;') it dies.

any thoughts?

its not a huge problem, except that vacuum anlyzing each of the 40 tables is a
little cumbersome.

Would you care to mutter something about the PG version you're running and
the platform and OS on which you're operating?

oops =)

PGSQL: 6.5.1
OS: Linux (Redhat 5.2)

--
Aaron J. Seigo
Sys Admin

From bouncefilter Mon Nov 15 17:01:55 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA74534
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 17:01:41 -0500 (EST) (envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id PAA24428;
Mon, 15 Nov 1999 15:02:04 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: Bruce Bantos <anon@mgfairfax.rr.com>
Subject: Re: [GENERAL] RPM vs. tar for 6.5.3
Date: Mon, 15 Nov 1999 14:58:40 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <Pine.LNX.4.10.9911151450120.15225-100000@guinness.urw.org>
In-Reply-To: <Pine.LNX.4.10.9911151450120.15225-100000@guinness.urw.org>
Cc: pgsql-general@postgreSQL.org
MIME-Version: 1.0
Message-Id: <99111515000203.15505@stilborne>
Content-Transfer-Encoding: 8bit

hi...

It's up to you, really. What I see as a trend for system administrator's
policies is the eventual migration to "roll-your-own" binaries. For ease
of use and installation, immediate gratification, etc., go with RPM. For
configurability of the binary, control of the file-placement schema, and
security of the source code, "rolling-your-own" is most definitely the way
to go.

of course, you can make your own RPMs. there are some decent tools out there to
ease this process. so you can roll you own on one system, package it, and
distribute it as RPM across your network...

--
Aaron J. Seigo
Sys Admin

From bouncefilter Mon Nov 15 18:28:56 1999
Received: from as411.tel.hr (as411.tel.hr [205.219.255.32])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA86762
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 18:28:12 -0500 (EST)
(envelope-from izvori@iname.com)
Received: from slavica (IDENT:slavica@ad11-m9.tel.hr [195.29.234.9])
by as411.tel.hr (8.9.3/8.9.3) with SMTP id AAA18892;
Tue, 16 Nov 1999 00:27:59 +0100 (MET)
From: Slavica Stefic <izvori@iname.com>
To: "Aaron J. Seigo" <aaron@gtv.ca>
Subject: Re: [GENERAL] vacuum analyze works on tables,
but not on entire database
Date: Tue, 16 Nov 1999 00:16:26 +0100
X-Mailer: KMail [version 1.0.20]
Content-Type: text/plain
References: <99111514415202.15505@stilborne>
Cc: pgsql-general@postgreSQL.org
MIME-Version: 1.0
Message-Id: <99111600263601.01115@slavica>
Content-Transfer-Encoding: 8bit

you wrote:

On Mon, 15 Nov 1999, Doran L. Barton wrote:

Not long ago, Aaron J. Seigo proclaimed...

something bizarre (at least to my experience) has started occuring in our
production database:

i can run vacuum analyze on each and every table INDIVIDUALLY no problem.. but
when i vacume analyze the whole db (by going into psql and uttering 'vacuum
analyze;') it dies.

any thoughts?

its not a huge problem, except that vacuum anlyzing each of the 40 tables is a
little cumbersome.

Would you care to mutter something about the PG version you're running and
the platform and OS on which you're operating?

oops =)

PGSQL: 6.5.1
OS: Linux (Redhat 5.2)

similar problem. But I have a table (big: 1.3MB, 7585 rows) on which the vacuum
analyze crash.

I use 6.5.2 also on redhat 5.2

---------
Marko Mikulicic

--
Aaron J. Seigo
Sys Admin

************

From bouncefilter Mon Nov 15 19:17:57 1999
Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207])
by hub.org (8.9.3/8.9.3) with SMTP id TAA94891
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 19:17:40 -0500 (EST)
(envelope-from tesio@easynet.fr)
Received: (qmail 74501 invoked from network); 16 Nov 1999 00:17:39 -0000
Received: from mailgate3.easynet.fr (192.168.1.4)
by mailserver.easynet.fr with QMQP; 16 Nov 1999 00:17:39 -0000
Received: from pop-nice-246.pops.easynet.fr (HELO atesio) (195.114.95.246)
by mrelay3.easynet.fr with SMTP; 16 Nov 1999 02:22:31 -0000
Message-ID: <008501bf2fc8$323ebbc0$f65f72c3@atesio>
From: "Alain TESIO" <tesio@easynet.fr>
To: <pgsql-general@postgreSQL.org>
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
<004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
Subject: Basic question about indexes (6.5.2)
Date: Tue, 16 Nov 1999 01:16:32 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

create table T1 ( x int );
create table T2 ( y int );
< insert from 1 to 1000 in T1 and T2>
create index idx_t1 on T1 ( x );
create index idx_t2 on T2 ( y );
explain select T1.x from T1,T2 where T1.x=T2.y;
drop table T1;
drop table T2;

Hash Join (cost=155.00 rows=1001 width=8)
-> Seq Scan on t2 (cost=43.00 rows=1000 width=4)
-> Hash (cost=43.00 rows=1000 width=4)
-> Seq Scan on t1 (cost=43.00 rows=1000 width=4)

I'm surprised that this simple query can't use indexes, or
it does and it's not reported in the explain output ?

By the way, with these tables, why does this query return
1000 and not 1000000 ?

select count(*) from T1,T2;

count
-----
1000
(1 row)

Alain

From bouncefilter Mon Nov 15 19:22:57 1999
Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207])
by hub.org (8.9.3/8.9.3) with SMTP id TAA95383
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 19:22:00 -0500 (EST)
(envelope-from tesio@easynet.fr)
Received: (qmail 74630 invoked from network); 16 Nov 1999 00:22:00 -0000
Received: from mailgate3.easynet.fr (192.168.1.4)
by mailserver.easynet.fr with QMQP; 16 Nov 1999 00:22:00 -0000
Received: from pop-nice-246.pops.easynet.fr (HELO atesio) (195.114.95.246)
by mrelay3.easynet.fr with SMTP; 16 Nov 1999 02:26:51 -0000
Message-ID: <008c01bf2fc8$cd5c34c0$f65f72c3@atesio>
From: "Alain TESIO" <tesio@easynet.fr>
To: <pgsql-general@postgreSQL.org>
Subject: Using functions with indexes
Date: Tue, 16 Nov 1999 01:20:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

Hello,

I want to use an index for comparisons on strings which are
not case-sensitive (I'm currently using col2=lower(col1))

The type of the column is char(30), it looks like I can't
use the function lower directly as it's not working on
the right type :

dip=> create index idx_tmpplayer_add_low on TMPPLAYER ( lower ( EM_ADDRESS )
text_ops );
ERROR: BuildFuncTupleDesc: function 'lower(bpchar)' does not exist

But I can't manage to define such a function I need for the index, what's
the trick ?

dip=> create function mylower(char) returns char as 'select lower($1)'
language 'sql';
ERROR: return type mismatch in function: declared to return char, returns
text
dip=> create function mylower(char) returns char as 'select
char(lower(char_text($1)))' language 'sql';
ERROR: parser: parse error at or near "lower"

Thanks
Alain

From bouncefilter Mon Nov 15 19:40:57 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id TAA98019
for <pgsql-general@postgreSQL.org>;
Mon, 15 Nov 1999 19:40:15 -0500 (EST) (envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id RAA24700;
Mon, 15 Nov 1999 17:40:31 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: "Alain TESIO" <tesio@easynet.fr>, <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Basic question about indexes (6.5.2)
Date: Mon, 15 Nov 1999 17:34:02 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <199911142250.dAEMo7u19178@lerami.lerctr.org>
<004e01bf2ef5$2c5fbc00$eb5f72c3@atesio>
<008501bf2fc8$323ebbc0$f65f72c3@atesio>
In-Reply-To: <008501bf2fc8$323ebbc0$f65f72c3@atesio>
MIME-Version: 1.0
Message-Id: <99111517383005.15505@stilborne>
Content-Transfer-Encoding: 8bit

Hi...

On Mon, 15 Nov 1999, Alain TESIO wrote:

create table T1 ( x int );
create table T2 ( y int );
< insert from 1 to 1000 in T1 and T2>
create index idx_t1 on T1 ( x );
create index idx_t2 on T2 ( y );
explain select T1.x from T1,T2 where T1.x=T2.y;

instead try:

explain select T1.x from T1,T2 where T1.x=T2.y::int;

NOTICE: QUERY PLAN:

Nested Loop (cost=2093.00 rows=100001 width=8)
-> Seq Scan on t2 (cost=43.00 rows=1000 width=4)
-> Index Scan using idx_t1 on t1 (cost=2.05 rows=1000 width=4)

EXPLAIN

the reason for this is that unless the input is specifically known to be of the
right type (and it almost never does unless you force a typecast) it won't use
the index(es) available.

--
Aaron J. Seigo
Sys Admin

From bouncefilter Mon Nov 15 22:29:59 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA19871
for <pgsql-general@postgresql.org>;
Mon, 15 Nov 1999 22:29:08 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from ocis.ocis.net (IDENT:http@ocis.ocis.net [209.52.173.1])
by ocis.ocis.net (8.9.3/8.9.3) with SMTP id TAA26339
for pgsql-general@postgresql.org; Mon, 15 Nov 1999 19:29:05 -0800
Date: Mon, 15 Nov 1999 19:29:05 -0800
From: Jason Leach <jcl@mail.ocis.net>
Message-Id: <199911160329.TAA26339@ocis.ocis.net>
Subject: Debian PKG.
To: undisclosed-recipients:;

hi,

Does anyone know of an update to the Debain 2.1 pgsql
package? At the moment I have 6.3.x, and would like
to at least get up to 6.4 so I can compile the perl DBI and
DBD interfaces.

Also, what is generally more parctical to learn? Pgsql with
Perl or Java? What's more commonly used as an interface
in a production system under Linux/Unix?

Thanks,
Jason

From bouncefilter Tue Nov 16 03:32:09 1999
Received: from tinago.msuiit.edu.ph (IDENT:manny@calitan.msuiit.edu.ph
[165.220.48.4]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA62759;
Tue, 16 Nov 1999 03:30:30 -0500 (EST)
(envelope-from manny@tinago.msuiit.edu.ph)
Received: from localhost (manny@localhost)
by tinago.msuiit.edu.ph (8.8.7/8.8.7) with ESMTP id QAA08784;
Tue, 16 Nov 1999 16:32:01 +0800
Date: Tue, 16 Nov 1999 16:32:01 +0800 (JST)
From: Manuel Cabido <manny@tinago.msuiit.edu.ph>
To: pgsql-general@hub.org
cc: pgsql-general-digest@hub.org
Subject: Re: pgsql-general-digest V1 #529
In-Reply-To: <199911160403.XAA24596@hub.org>
Message-ID: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sir:

I would like to inquire if with PostgreSQL 6.5.3.x I can put the same
database on two or more different Linux server such that each update will
be replicated on all database backends...

Manny C. Cabido
====================================
e-mail:manny@tinago.msuiit.edu.ph
manny@sun.msuiit.edu.ph
=====================================

From bouncefilter Tue Nov 16 10:48:14 1999
Received: from nefertiti.pasteur.fr (nefertiti.pasteur.fr [157.99.64.20])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA44103
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 10:47:46 -0500 (EST)
(envelope-from bortz@pasteur.fr)
Received: from ezili.sis.pasteur.fr (ezili.sis.pasteur.fr [157.99.60.56])
by nefertiti.pasteur.fr (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id
dAGFlTL26908; Tue, 16 Nov 1999 16:47:29 +0100 (MET)
Received: from pasteur.fr (localhost [127.0.0.1])
by ezili.sis.pasteur.fr (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id
QAA11430; Tue, 16 Nov 1999 16:47:28 +0100
Message-Id: <199911161547.QAA11430@ezili.sis.pasteur.fr>
X-Authentication-Warning: ezili.sis.pasteur.fr: Host localhost [127.0.0.1]
claimed to be pasteur.fr
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
From: Stephane Bortzmeyer <bortzmeyer@pasteur.fr>
To: Jason Leach <jcl@mail.ocis.net>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Debian PKG.
In-reply-to: <199911160329.TAA26339@ocis.ocis.net>
(Jason Leach <jcl@mail.ocis.net>'s message of
Mon, 15 Nov 1999 19:29:05 PST)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 16 Nov 1999 16:47:28 +0100
Sender: bortz@pasteur.fr

On Monday 15 November 1999, at 19 h 29, the keyboard of Jason Leach
<jcl@mail.ocis.net> wrote:

Does anyone know of an update to the Debain 2.1 pgsql
package?

The package in "unstable" (alias "potato", the future Debian 2.2) is 6.5.2.
But, because the GNU libc maintainers broke the compatibility :-( you cannot
install it on Debian 2.1 ("slink"). It may be possible to recompile it on a
2.1 machine.

At the moment I have 6.3.x, and would like
to at least get up to 6.4 so I can compile the perl DBI and
DBD interfaces.

They exist as Debian packages on Debian 2.1, they work fine and you don't have
to compile them.

Also, what is generally more parctical to learn? Pgsql with
Perl or Java? What's more commonly used as an interface
in a production system under Linux/Unix?

I use Perl.

From bouncefilter Tue Nov 16 11:29:15 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA48847;
Tue, 16 Nov 1999 11:28:43 -0500 (EST) (envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id JAA25927;
Tue, 16 Nov 1999 09:28:42 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: Manuel Cabido <manny@tinago.msuiit.edu.ph>, pgsql-general@hub.org
Subject: Re: replication
Date: Tue, 16 Nov 1999 09:24:00 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: pgsql-general-digest@hub.org
References: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
In-Reply-To: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
MIME-Version: 1.0
Message-Id: <99111609264002.18220@stilborne>
Content-Transfer-Encoding: 8bit

hi...

I would like to inquire if with PostgreSQL 6.5.3.x I can put the same
database on two or more different Linux server such that each update will
be replicated on all database backends...

this is on the to-do list under "Exotic Features". it seems to be one of the
more asked about features that doesn't exist at the moment on the General list.
unfortunately, it isn't a trivial project so it won't happen over night...

right now, you can jury rig your own system up using network file systems,
periodic updates of local filesystems, etc... this is limited in
usefulness...

true replication does not exist (ala Oracle or MSJet)... yet.

--
Aaron J. Seigo
Sys Admin

From bouncefilter Tue Nov 16 12:22:15 1999
Received: from propertykey.com (IDENT:root@propertykey.com [206.196.37.193])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA56546;
Tue, 16 Nov 1999 12:21:47 -0500 (EST)
(envelope-from jeff@propertykey.com)
Received: from propertykey.com (gotojail.propertykey.com [206.196.37.197])
by propertykey.com (8.9.3/8.9.3) with ESMTP id LAA05427;
Tue, 16 Nov 1999 11:21:45 -0600
Message-ID: <383192A9.AA3E25C4@propertykey.com>
Date: Tue, 16 Nov 1999 11:21:45 -0600
From: Jeff Hoffmann <jeff@propertykey.com>
Organization: PropertyKey.com
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: pgsql-general@hub.org, pgsql-general-digest@hub.org
Subject: Re: [GENERAL] Re: replication
References: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
<99111609264002.18220@stilborne>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Aaron J. Seigo" wrote:

I would like to inquire if with PostgreSQL 6.5.3.x I can put the same
database on two or more different Linux server such that each update will
be replicated on all database backends...

right now, you can jury rig your own system up using network file systems,
periodic updates of local filesystems, etc... this is limited in
usefulness...

my favorite hack is to wrap the c/c++ api so you can set up a group of
mirror database connections and then calling the wrapped functions will
call the original function on each of the mirror database connections.
i've really never thought of it as something that should be part of the
library, though, since that's pretty easy to implement in the
application.

From bouncefilter Tue Nov 16 12:58:16 1999
Received: from ws-173.e-connectsolutions.net (ws-173.e-connectsolutions.net
[209.124.91.173]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA61775
for <pgsql-general@postgresql.org>;
Tue, 16 Nov 1999 12:58:08 -0500 (EST)
(envelope-from john@ws-173.e-connectsolutions.net)
Received: (from john@localhost)
by ws-173.e-connectsolutions.net (8.9.3/8.9.3) id MAA00366
for pgsql-general@postgresql.org; Tue, 16 Nov 1999 12:53:21 -0500
Date: Tue, 16 Nov 1999 12:53:21 -0500
From: John Hyland <john@e-connectsolutions.com>
To: pgsql-general@postgresql.org
Subject: create type question again
Message-ID: <19991116125321.N31253@e-connectsolutions.com>
Mail-Followup-To: pgsql-general@postgresql.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
X-Organization: Five Star Communications
X-Duties: SysAdmin, Programmer

Hi, I posted yesterday about a problem I was having creating multiple 'text'
types by different names. I was getting an error that array_in(opaque) was not
defined. I think I found an answer for my problem, though, and I thought I'd
share it.

It seems that if I

CREATE TYPE array_in(opaque) RETURNS text
AS '/usr/local/src/postgres-6.5.2/src/include/postgres.h'
LANGUAGE 'c';

as user 'postgres' and then create my types with textin as the input function and
textout as the output function, everything seems to work the way I want it to.

--
John Hyland
SysAdmin, Programmer
e-Connect Solutions

From bouncefilter Tue Nov 16 13:36:16 1999
Received: from unix.netstream.net (IDENT:qmailr@unix.netstream.net
[216.136.15.13]) by hub.org (8.9.3/8.9.3) with SMTP id NAA67487
for <pgsql-general@postgresql.org>;
Tue, 16 Nov 1999 13:35:41 -0500 (EST)
(envelope-from bibach@unix.netstream.net)
Received: (qmail 17626 invoked by uid 504); 16 Nov 1999 18:35:36 -0000
Date: Tue, 16 Nov 1999 12:35:36 -0600
From: Brandon Ibach <bibach@infomansol.com>
To: pgsql-general@postgresql.org
Subject: CREATE OPERATOR error
Message-ID: <19991116123536.B16386@unix.netstream.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i

Can anybody explain what might be happening here?

abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
abc-> procedure = vciceq, commutator = =* );
ERROR: parser: parse error at or near "varchar"

The function "vciceq" already exists, and works. I've tried a
number of variations on the above with different spacing, with no
success. Is there some syntax peculiarity I'm missing? This is on
PostgreSQL 6.5.2 on a Linux x86 system (RedHat 5.1, kernel 2.0.34).
TIA...

-Brandon :)

From bouncefilter Tue Nov 16 14:02:17 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA72043
for <pgsql-general@hub.org>; Tue, 16 Nov 1999 14:01:57 -0500 (EST)
(envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id MAA26508;
Tue, 16 Nov 1999 12:02:17 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: Jeff Hoffmann <jeff@propertykey.com>
Subject: Re: [GENERAL] Re: replication
Date: Tue, 16 Nov 1999 11:54:23 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
<99111609264002.18220@stilborne>
<383192A9.AA3E25C4@propertykey.com>
In-Reply-To: <383192A9.AA3E25C4@propertykey.com>
Cc: pgsql-general@hub.org
MIME-Version: 1.0
Message-Id: <99111612001404.18220@stilborne>
Content-Transfer-Encoding: 8bit

hi...

my favorite hack is to wrap the c/c++ api so you can set up a group of
mirror database connections and then calling the wrapped functions will
call the original function on each of the mirror database connections.
i've really never thought of it as something that should be part of the
library, though, since that's pretty easy to implement in the
application.

very cool... but i too agree that this shouldn't necessarily be in the
libraries...

this needs to be in the back end... otherwise, if you have multiple people
performing updates on different replicated servers, how can you guarentee
concurancy? how do you manage the differences between read-only and updateable
replicants? (this can be done using your wrapper method, but quickly gets
clumsy)

also, it would make maintaining replication simpler if it were part of the
back end process... and not prone to some app that goes around your wrapped lib
and defeats the replication scheme altogether... imo, it should be part of the
transaction system.... =)

--
Aaron J. Seigo
Sys Admin

From bouncefilter Tue Nov 16 14:33:17 1999
Received: from propertykey.com (IDENT:root@propertykey.com [206.196.37.193])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA76685
for <pgsql-general@hub.org>; Tue, 16 Nov 1999 14:33:14 -0500 (EST)
(envelope-from jeff@propertykey.com)
Received: from propertykey.com (gotojail.propertykey.com [206.196.37.197])
by propertykey.com (8.9.3/8.9.3) with ESMTP id NAA05623;
Tue, 16 Nov 1999 13:33:02 -0600
Message-ID: <3831B16E.F1D48D46@propertykey.com>
Date: Tue, 16 Nov 1999 13:33:02 -0600
From: Jeff Hoffmann <jeff@propertykey.com>
Organization: PropertyKey.com
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Aaron J. Seigo" <aaron@gtv.ca>, pgsql-general@hub.org
Subject: Re: [GENERAL] Re: replication
References: <Pine.LNX.4.04.9911161628270.8457-100000@tinago.msuiit.edu.ph>
<99111609264002.18220@stilborne>
<383192A9.AA3E25C4@propertykey.com>
<99111612001404.18220@stilborne>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Aaron J. Seigo" wrote:

this needs to be in the back end... otherwise, if you have multiple people
performing updates on different replicated servers, how can you guarentee
concurancy? how do you manage the differences between read-only and updateable
replicants? (this can be done using your wrapper method, but quickly gets
clumsy)

yeah it can get clumsy, but fortunately updates are pretty rare in my
case (and usually only performed by one person) so i don't really worry
about those issues, but i should. the only safety issue i use is
starting a transaction for each connection, perform the action on all of
the databases, and then commit the transaction on each. it's not bad
unless one of the commits fails and the others don't, then i have to
retry the failed ones & hope it works. i don't know how to fix it if i
had to give up on one of the transactions for a mirror. again, not
perfect, but it works pretty well for me & my simpler cases.

From bouncefilter Tue Nov 16 15:39:21 1999
Received: from falla.videotron.net (falla.videotron.net [205.151.222.106])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA84743
for <pgsql-general@hub.org>; Tue, 16 Nov 1999 15:39:09 -0500 (EST)
(envelope-from rwelsh@OneStepInternet.com)
Received: from laptop ([24.200.30.33]) by falla.videotron.net (Sun Internet
Mail Server sims.3.5.1999.07.30.00.05.p8)
with SMTP id <0FLB00A0A55DWN@falla.videotron.net> for
pgsql-general@hub.org; Tue, 16 Nov 1999 15:34:26 -0500 (EST)
Date: Tue, 16 Nov 1999 15:41:23 -0500
From: Richard Welsh <rwelsh@OneStepInternet.com>
Subject: Re: [GENERAL] Re: replication
To: pgsql-general@hub.org
Message-id: <008601bf3072$f2593200$6301a8c0@laptop.local>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.1
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3

Is it possible to log the transactions ( as complete statements ) on one
database then process the logged transactions on the second database at
intervals to keep it up to date?

RDW.

-----Original Message-----
From: Jeff Hoffmann <jeff@propertykey.com>
To: Aaron J. Seigo <aaron@gtv.ca>; pgsql-general@hub.org
<pgsql-general@hub.org>
Date: November 16, 1999 2:28 PM
Subject: Re: [GENERAL] Re: replication

"Aaron J. Seigo" wrote:

this needs to be in the back end... otherwise, if you have multiple

people

performing updates on different replicated servers, how can you guarentee
concurancy? how do you manage the differences between read-only and

updateable

replicants? (this can be done using your wrapper method, but quickly gets
clumsy)

yeah it can get clumsy, but fortunately updates are pretty rare in my
case (and usually only performed by one person) so i don't really worry
about those issues, but i should. the only safety issue i use is
starting a transaction for each connection, perform the action on all of
the databases, and then commit the transaction on each. it's not bad
unless one of the commits fails and the others don't, then i have to
retry the failed ones & hope it works. i don't know how to fix it if i
had to give up on one of the transactions for a mirror. again, not
perfect, but it works pretty well for me & my simpler cases.

************

From bouncefilter Tue Nov 16 16:17:18 1999
Received: from alert.infoplease.com ([208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA90312
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:16:36 -0500 (EST)
(envelope-from boris@range.infoplease.com)
Received: from griddle.infoplease.com (griddle [10.0.1.210])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id QAA05337
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:16:06 -0500 (EST)
Received: (from boris@localhost)
by griddle.infoplease.com (8.9.3/8.9.1) id QAA25781;
Tue, 16 Nov 1999 16:16:05 -0500
X-Authentication-Warning: griddle.infoplease.com: boris set sender to
boris@alert.infoplease.com using -f
From: Boris Goldowsky <boris@range.infoplease.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14385.51605.660473.625912@griddle.infoplease.com>
Date: Tue, 16 Nov 1999 16:16:05 -0500 (EST)
To: pgsql-general@postgreSQL.org
Subject: concurrency
X-Mailer: VM 6.69 under Emacs 20.4.1
X-Attribution: Bng

It seems that whenever we are doing a large operation -- eg, CREATE
INDEX on a sizable table, or VACUUM on a big database -- all other
postgres operations on that server stop dead. Attempts to do simple
operations on completely separate databases (but on the same server)
will hang (or perhaps they proceed extremely slowly) until after the large
operation is finished.

Is there any way around this limitation? Is this something that can
be addressed through parameter tweaking of the postmaster, or would it
be solved by having multiple CPUs on the database machine?

Bng
--
Boris Goldowsky Engineering & Development Manager
Information Please, LLC boris@alert.infoplease.com
www.infoplease.com 617 832-0324

From bouncefilter Tue Nov 16 16:21:21 1999
Received: from alert.infoplease.com ([208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA90834
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:20:40 -0500 (EST)
(envelope-from boris@range.infoplease.com)
Received: from griddle.infoplease.com (griddle [10.0.1.210])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id QAA06621
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:20:10 -0500 (EST)
Received: (from boris@localhost)
by griddle.infoplease.com (8.9.3/8.9.1) id QAA25802;
Tue, 16 Nov 1999 16:20:10 -0500
X-Authentication-Warning: griddle.infoplease.com: boris set sender to
boris@alert.infoplease.com using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14385.51850.6966.587429@griddle.infoplease.com>
Date: Tue, 16 Nov 1999 16:20:10 -0500 (EST)
From: Boris Goldowsky <boris@alum.mit.edu>
Reply-to: Boris Goldowsky <boris@alum.mit.edu>
To: pgsql-general@postgreSQL.org
Subject: concurrency
X-Mailer: VM 6.69 under Emacs 20.4.1
X-Attribution: Bng

Is there any way around this limitation? Is this something that can
be addressed through parameter tweaking of the postmaster, or would it
be solved by having multiple CPUs on the database machine?

Boris Goldowsky

From bouncefilter Tue Nov 16 16:27:18 1999
Received: from gandalf.digicool.com (digitalcreations05.erols.com
[216.164.72.5]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA91490
for <pgsql-general@postgresql.org>;
Tue, 16 Nov 1999 16:27:07 -0500 (EST)
(envelope-from petrilli@digicool.com)
Received: from [216.164.72.35] (alanke.digicool.com [216.164.72.35]) by
gandalf.digicool.com with SMTP (Microsoft Exchange Internet
Mail Service Version 5.5.1960.3)
id WSNC13AS; Tue, 16 Nov 1999 16:37:06 -0500
User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513)
Date: Tue, 16 Nov 1999 16:26:47 -0500
Subject: Problems installing on FreeBSD 3.3 (PG_VERSION/pg_user missing) 6.5.3
From: Christopher Petrilli <petrilli@digicool.com>
To: <pgsql-general@postgresql.org>
Message-ID: <B4573646.60F0%petrilli@digicool.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit

Ok, I've done this three times on 3 different machines, and get it wrong
each time...

I go through the INSTALL docs, compile, install, run initdb and then get:

"""...
File '/usr/local/pgsql/data/PG_VERSION' does not exist or no read
permission."""

It's not the latter, it's missing... it's not in data/template1 either. And
if I fake it (put the X.Y version in the file), I still am missing the
pg_user tables... I've tried this 3-4 times on the same install as well...
no go.

This is on PostgreSQL 6.5.3 just downloaded.

Chris

--
| Christopher Petrilli Python Powered Digital Creations, Inc.
| petrilli@digicool.com http://www.digicool.com

From bouncefilter Tue Nov 16 16:33:18 1999
Received: from guinness.urw.org (root@guinness.urw.org [209.32.194.52])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA92362
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:32:55 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from wookimus.net (chewie@wookimus.net [209.32.194.62])
by guinness.urw.org (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id PAA16896;
Tue, 16 Nov 1999 15:32:49 -0600
Date: Tue, 16 Nov 1999 15:32:49 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@guinness.urw.org
To: Brandon Ibach <bibach@infomansol.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] CREATE OPERATOR error
In-Reply-To: <19991116123536.B16386@unix.netstream.net>
Message-ID: <Pine.LNX.4.10.9911161532150.16841-100000@guinness.urw.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 16 Nov 1999, Brandon Ibach wrote:

BI> Can anybody explain what might be happening here?
BI>
BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
BI> abc-> procedure = vciceq, commutator = =* );
BI> ERROR: parser: parse error at or near "varchar"
BI>
BI> The function "vciceq" already exists, and works. I've tried a
BI> number of variations on the above with different spacing, with no
BI> success. Is there some syntax peculiarity I'm missing? This is
BI> on PostgreSQL 6.5.2 on a Linux x86 system (RedHat 5.1, kernel
BI> 2.0.34).

Isn't the operator '=*' a reserved operator for a right outer join?

Chad

From bouncefilter Tue Nov 16 16:52:19 1999
Received: from mail.enterprise.net (mail.enterprise.net [194.72.192.18])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA95659
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:51:34 -0500 (EST) (envelope-from olly@lfix.co.uk)
Received: from linda.lfix.co.uk (root@max03-010.enterprise.net
[194.72.196.10])
by mail.enterprise.net (8.8.5/8.8.5) with ESMTP id VAA18204;
Tue, 16 Nov 1999 21:51:31 GMT
Received: from lfix.co.uk (olly@localhost [127.0.0.1])
by linda.lfix.co.uk (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id VAA31339;
Tue, 16 Nov 1999 21:50:15 GMT
Message-Id: <199911162150.VAA31339@linda.lfix.co.uk>
X-Authentication-Warning: linda.lfix.co.uk: Host olly@localhost [127.0.0.1]
claimed to be lfix.co.uk
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
To: Jason Leach <jcl@mail.ocis.net>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Debian PKG.
In-Reply-To: Message from Jason Leach <jcl@mail.ocis.net> of "Mon,
15 Nov 1999 19:29:05 PST." <199911160329.TAA26339@ocis.ocis.net>
References: <199911160329.TAA26339@ocis.ocis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 16 Nov 1999 21:50:12 +0000
From: "Oliver Elphick" <olly@lfix.co.uk>

Jason Leach wrote:

Does anyone know of an update to the Debain 2.1 pgsql
package? At the moment I have 6.3.x, and would like
to at least get up to 6.4 so I can compile the perl DBI and
DBD interfaces.

6.3.x is in the stable release of Debian; later versions of postgresql are
to be found in the unstable distribution.

Also, what is generally more parctical to learn? Pgsql with
Perl or Java? What's more commonly used as an interface
in a production system under Linux/Unix?

My personal view of Java on Linux is that it is rather unstable and it is
difficult to get good free software.

Perl is much more reliable; however I haven't learnt it. My own efforts are
devoted to making an Eiffel library to interface to libpq.

--
Vote against SPAM: http://www.politik-digital.de/spam/
========================================
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"Therefore being justified by faith, we have peace
with God through our Lord Jesus Christ." Romans 5:1

From bouncefilter Tue Nov 16 16:58:18 1999
Received: from unix.netstream.net (IDENT:qmailr@unix.netstream.net
[216.136.15.13]) by hub.org (8.9.3/8.9.3) with SMTP id QAA96383
for <pgsql-general@postgreSQL.org>;
Tue, 16 Nov 1999 16:57:27 -0500 (EST)
(envelope-from bibach@unix.netstream.net)
Received: (qmail 19265 invoked by uid 504); 16 Nov 1999 21:57:25 -0000
Date: Tue, 16 Nov 1999 15:57:24 -0600
From: Brandon Ibach <bibach@infomansol.com>
To: ^chewie <chewie@wookimus.net>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] CREATE OPERATOR error
Message-ID: <19991116155724.C16386@unix.netstream.net>
References: <19991116123536.B16386@unix.netstream.net>
<Pine.LNX.4.10.9911161532150.16841-100000@guinness.urw.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <Pine.LNX.4.10.9911161532150.16841-100000@guinness.urw.org>;
from ^chewie on Tue, Nov 16, 1999 at 03:32:49PM -0600

Quoting ^chewie <chewie@wookimus.net>:

On Tue, 16 Nov 1999, Brandon Ibach wrote:

BI> Can anybody explain what might be happening here?
BI>
BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
BI> abc-> procedure = vciceq, commutator = =* );
BI> ERROR: parser: parse error at or near "varchar"
BI>
BI> The function "vciceq" already exists, and works. I've tried a
BI> number of variations on the above with different spacing, with no
BI> success. Is there some syntax peculiarity I'm missing? This is
BI> on PostgreSQL 6.5.2 on a Linux x86 system (RedHat 5.1, kernel
BI> 2.0.34).

Isn't the operator '=*' a reserved operator for a right outer join?

That may be, but I just tried it with an operator name of =: and
got the same result, so that doesn't appear to be the problem here. :(

-Brandon :)

From bouncefilter Tue Nov 16 17:45:19 1999
Received: from genisys.gtv.ca (h-207-228-97-106.gen.cadvision.com
[207.228.97.106]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA02515
for <pgsql-general@hub.org>; Tue, 16 Nov 1999 17:44:43 -0500 (EST)
(envelope-from aaron@gtv.ca)
Received: from stilborne (h-207-228-97-110.gen.cadvision.com [207.228.97.110])
by genisys.gtv.ca (8.9.3/8.8.7) with SMTP id PAA26972;
Tue, 16 Nov 1999 15:44:57 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: Richard Welsh <rwelsh@OneStepInternet.com>, pgsql-general@hub.org
Subject: Re: [GENERAL] Re: replication
Date: Tue, 16 Nov 1999 15:15:23 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <008601bf3072$f2593200$6301a8c0@laptop.local>
In-Reply-To: <008601bf3072$f2593200$6301a8c0@laptop.local>
MIME-Version: 1.0
Message-Id: <99111615425505.18220@stilborne>
Content-Transfer-Encoding: 8bit

hi...

Is it possible to log the transactions ( as complete statements ) on one
database then process the logged transactions on the second database at
intervals to keep it up to date?

transaction logging is already done on disk in pg_log, however you can't count
on it being correct (esp as pgsql moves towards things such as WAL) as there
will be things in memory that aren't necessarily on disk... this leaves us with
no better a solution than doing it some other way...

the best place for this would be in the transaction handler of pgsql itself.
where a transaction completed on a Master server would cause the same updates
on all Replicants... this would do it for read-only database replication...
under this sort of system, you could only update one database, but all
databases would show the updates (MS Jet works this way? *tries to remember*)...

past that, you could then modify transactions to check not just for
transactions locally, but for transactions on any other given database
installation(s)... global locking, in other words...

this works as long as you can reach all your hosts all the time... if you
can't... then you either get you entire replication setup hung (which would be
pointless) ... or ... you keep revision #s on each row/field that are kept
locally should other Masters not be reachable by design or accident (i believe
this is how Oracle does it.. revision #s)... and once communication is
restored, then the systems sort out the revisions amongst themselves, asking
for user intervention on deadlocks. this would allow multiple Masters, multiple
Replicants and downtimes between them all. this is very tricky and probably the
last piece of the puzzle that would/should be tackled...

looking through the source there are a few promising places to start... (this
should probaly be on the hackers list now.. heh.. *shrug*)

acess/transam - the transaction manager... the commit functionality would need
to be altered to do updates across replicated systems...

storage/lmgr - lock manager... would need to be made aware of other lock tables
that may not be local.. possibly an interface to allow remote checking of lock
tables... a read-only node would always see a write lock on its own tables...
perhaps it would be rerouted to the Master for writing.

utils/time - checks the timliness of data due to transactions... could be
extended eventually to provide, along with the lock manager, concurency between
multiple masters? additional logging information would also be required to
pull this one off (assuming a network connection that isn't up 100% of the
time)...

then there is the point of where you would define the Master/Replicant
relationships within the database(s) itself.. e.g. would it be another system
table to keep track of Masters/Replicants and rules for their operations?

anyways, this is just the thoughts that come to mind... no real detail here,
nor any sense if this would be The Right Way to do it... however, my guess
would be to say that these places in the source would be where to start
looking...

word from those in the know?

--
Aaron J. Seigo
Sys Admin

From bouncefilter Tue Nov 16 18:41:20 1999
Received: from mail.iconz.co.nz (oldmail.iconz.co.nz [202.14.100.36])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA13318
for <pgsql-general@postgresql.org>;
Tue, 16 Nov 1999 18:40:45 -0500 (EST)
(envelope-from markir@hnz.co.nz)
Received: from [192.173.20.11] (mail.hnz.co.nz [192.173.20.11])
by mail.iconz.co.nz (8.9.3/8.9.3) with SMTP id MAA113840942795665
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 12:41:05 +1300 (NZDT)
Received: from hiscorpxy01.hnz.co.nz by [192.173.20.11]
via smtpd (for mail.iconz.co.nz [210.48.22.36]) with SMTP;
16 Nov 1999 23:36:29 UT
Received: FROM hufin0.hnz.co.nz BY hiscorpxy01.hnz.co.nz ;
Wed Nov 17 12:38:32 1999 +1300
Received: from hudev0.hnz.co.nz (hudev0 [10.24.10.46]) by hufin0.hnz.co.nz
with ESMTP (8.8.6 (PHNE_14041)/8.7.1) id MAA06413 for
<pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 12:39:07 +1300 (NZDT)
Received: (from markir@localhost) by hudev0.hnz.co.nz (8.7.6/8.7.1) id
MAA09493 for pgsql-general@postgresql.org;
Wed, 17 Nov 1999 12:38:46 +1300 (NZDT)
Date: Wed, 17 Nov 1999 12:38:46 +1300 (NZDT)
From: Mark Kirkwood <markir@hnz.co.nz>
Message-Id: <199911162338.MAA09493@hudev0.hnz.co.nz>
subject: a comparison of 4 databases
To: undisclosed-recipients:;

A Comparison Of 4 Databases
---------------------------

Intro
-----

This paper shows the results of an evaluation of 4 databases. I am posting it
to this mail group as I think Postgresql emerged quite favourably.

The evaluated databases were Oracle, Informix, Mysql and Postgresql.

Features and performance were examined.

Hardware And Operating System
-----------------------------

2 x HP Vertra VE 7 each with 160M RAM + 1x3.2G + 1x13G Quantum IDE Drives were used.
Redhat 6.0 was used as the operating system. No kernel changes were made.

Initial Experiences
-------------------

Mysql was obtained in rpm format and was amazingly easy to install. The
installation process created and started a database. The version was 3.22.27

Documentation was supplied and was good.

Postgresql was similarly elementary to install, and again a database was
created and started. The product comes with the flavour of Linux used and
was in rpm format. The version was 6.5.2

Documentation was supplied and was very good.

Informix was more cryptic to install. It was obtained in rpm format and
installed. However this merely installed an archive and the real installation
process had to be run thereafter. After this it had to be divined as to what
was required next - the install does not create a database.
Using some of the (not supplied) documentation it was discovered how to create
and configure a database. The version was 7.30 ( This is old, but all they
are supplying on this platform - 9.x is current)

Documentation was not supplied, it was available on the Informix web site. It is ok.

Oracle was difficult to judge as the author frequently installs it. However
pretending to be coming to it new, it would be very difficult to install.
It does not come in rpm format. It is downloadable from the Oracle web site.
The small amount of included documentation is sufficient to enable someone
to work out how to start the installer program. This program is a rudimentary
wizard that asks questions and presents a list of components to choose....
a newcomer would suffer confusion here. The installer can create a database as
part of the install. The version was 8.0.5 (this is slightly old - 8.1.5 is
Current but buggy, 8.0.5 is the latest stable release on this platform).

Documentation is not supplied, it is available from the Oracle web site. It is
ok.

Tests And results
-----------------

Database Feature Comparison

Database Cost Trans Row Const Program Sec Fail Hot
actions Lock raints mable ure Safe back

Mysql 0 /3000 No No No Partial Yes No No
Postgresql 0 Yes Yes Partial Yes Yes Yes No
Oracle 3200 Yes Yes Yes Yes Yes Yes Yes
Informix 2000 Yes No Yes Yes Yes No No

Cost

NZ$ for 10 user license. Two prices mean that the product is charged
for if resold as part of an application ( Mysql )
Support is not included

Transactions

Commit, rollback, isolation levels of at least read commited

Row Locking

select for update that locks only the rows selected and does not
block reads

Constraints

primary and foreign key, with ability to enable/ disable or drop / add
existence will give ""Partial"" and enable etc will give "Yes"

Programmable

create trigger, procedural language extensions to SQL
A "Partial" means that external functions only are supported

Secure

Requires username and password validation

Fail Safe

delete of 100 out of 100000 rows, commit ( if have it ) then power
off and on, check after power on - 999900 rows gets a "Yes"

Hot Backup

Can a consistent backup of the database be run backup while it is up
with transactions performed against it.

Database Performance Comparison - Data Warehouse

Database Bulk Load Summarize 3% Summarize 0.3% Summarize 0.3%
1M of 3M of 3M of 3M
1 dim 1 fact 2 dim 1 fact 3 dim 1 fact

Mysql 20 14 90 57
Postgresql 420 16 4 7
Oracle 65 5 3 3
Informix 170 8 5 6

Notes

Bulk Load

elapsed seconds to load 1000000 rows via whatever bulk load tool is
supplied.

Summarize 3%
1 dim + 1 fact

Measure elapsed seconds to display summarized count and one timelike
dimension attribute for basic star query
Access path can be via an index scan

Summarize 0.3%
2 dim + 1 fact

Measure elapsed seconds to display summarized count and one non timelike
dimesion attribute for less basic star query
Access path can be via index scans

Summarize 0.3%
3 dim + 1 fact

Measure elapsed seconds to display a summarized count and 1 non timelike
dimension attribute for more complex star query
Access path can be via index scans

Database Performance Comparison - Online

Database Create Create Query 1 Query 4 Query Summary
10K 1M of 10K of 1M 10% of 1M

Mysql 7 891 0 0 1
Postgresql 21 4430 0 0 2
Oracle 31 3694 0 0 2
Informix 0 0 10

Database Tpm Tpm Tpm Tpm
1 sess. 2 sess. 4 sess. 8 sess.

Mysql 59/58 59/115 59/229 58/425
Postgresql 48 90 169 233
Oracle 55 108 180 291
Informix

Notes

Unfortunately no Informix SDK was available, so there is no result for
the first two or last tests.

Create 10K

elapsed seconds for Php app to insert 10000 rows one by one

Create 1M

elapsed seconds for Php app to insert 1000000 rows one by one

Query 1

0 seconds means that no delay was measurable
Measure elapsed seconds to show master record 1 row located 70% though
the table. Access path can be via an index scan

Query 4

Measure elapsed seconds to display 4 detail rows for one of the master
records in previous test. Access path can be via index scans

Query Summary

Measure elapsed seconds to display a summarized sum and count
for 5% of 1000000 rows. This is a 2 table join . Access path can be via
index scans

Tpm n sessions

Transactions per minute for n sessions, achievable for lightweight Perl
DBI application. Two results for Mysql refer to two possible locking
schemes

Analysis
--------

Features

Oracle clearly has the most features. However it is Postgresql that is next in
line.

The features fail safe, transactions and security are seen as essential,
with row locking as highly desirable.

This means that at face value only Oracle and Postgresql satisfy the criteria.

Initially Postgresql did not force password entry and thus was not secure,
however it was discovered that access to the database is configured at install
time as trusted and has to be changed to require passwords.

It should be noted that Oracle needed a patch to be fail safe, and that this
was not advertised on the web site, thus is possible that Informix and Mysql
can also be similarly patched.

Repeated tests with Informix page level locks showed that readers were blocked at this point. This was viewed as extremely undesirable.

Mysql's lack of transactions was a killer for it, the complexity of having to
programmatically undo an n-table operation was viewed as prohibitive.
( It was noted that the Mysql to do list had atomic operations - pseudo
transactions, on it .)

In conclusion on the features front, Oracle and Postgresql emerge as the leaders.

Performance

1 Online operations

Initially Postgreql refused to use indexes to help with queries. A mail to one of the Postgresql Development Team traced this to an unusual pickiness with respect to the implied datatypes of constants in the where clause.

Informix had problems with the summary query, it would not go faster that 10s, however it seemed to perform ok for the 10000 and 1000000 query searches.

Mysql demonstrates the overhead associated with multiple versioning and
transactions. It was obviously the fastest raw speed terms. It was in
general 4-5 times faster than anything else.

Postgresql was in general about 20% slower than Oracle.

The multiple session transaction test is most interesting. The idea was to
mimic a Tpc A style banking application with some user think time during the
transaction (1 second ).
Clearly Mysql with its table level locks could not scale at all. However it has
application locks that are nameable, so can mimic row locks - as long as every
access uses them. If these were turned on then a dramatic turnaround was
observed.

Thus Mysql is fastest, and most scalable if applications locks can be used.
Oracle and Postgreql are similar in scalability, but Postgresql begins to tail off a little before Oracle does.

2 Data warehousing operations

Mysql has a very fast bulk load facility.
Oracle also has a very fast bulk load.
Infomix has a reasonably fast one.
Postgresql is noticeably slower than any of the others.

Mysql performed extremely poorly at the star type queries.
Oracle and Informix performed very well.
Postgresql performed very well in all but the first query - the simplest (ironically), but it scanned the most data. This points to Oracle and Informix having faster Nested Loop or Sort algorithms.

Both Oracle and Postgresql would experience a period of poor performance on a table immediately after it was bulk loaded - typically until it was vacuumed or analyzed.

In conclusion for this section Oracle, Informix are very good.
Postgresql is good but is hampered by slow bulk load and sorting of large datasets.
Mysql can get the data in fast but is poor at querying it.

Overall
-------

Informix performs mostly ok, but its locking scheme precludes it for serious on line use (it would have been interesting to test this).
Oracle performs well.
Mysql's lack of transactions would have been ok for data warehousing, but it could not do star queries. This rules it out.
Postgresql performed about 20% slower than Oracle, except for bulk loads and large dataset sorts. These things mean that it is suitable for data warehousing and on line operations, with the proviso that large data loads and some large summary queries may be unpleasantly slow.

Appendix

( database schemas and source for programs )

Schema and queries for on line tests

/* -------------------------------------------------------------------
file : createupdattables.sql
does : create tables for updat example...
notes : master has 10000 rows
detail has 1000000 rows 100 for each master row
------------------------------------------------------------------*/

create table master
(
mas_id int4,
mas_name varchar(100),
mas_amt float8
);

create table detail
(
det_id int4,
det_mas_id int4,
det_date datetime,
det_amt float8
);

create table masterlog
(
log_mas_id int4,
log_date datetime);

/* -----------------------------------------------------------------
file : createupdatindexes.sql
does : create indexes and keys for tables...
----------------------------------------------------------------- */

create unique index mas_pk on master using btree (mas_id);

create index det_pk on detail using btree (det_id);
create index det_fk on detail using btree (det_mas_id);

/* -----------------------------------------------------------------
file : queries1-3.sql
does : the queries...
----------------------------------------------------------------- */

select *
from master
where mas_id = 7000;

select *
from detail
where det_mas_id = 7000
and det_amt > 960;

select sum(mas_amt),count(*)
from detail,master
where mas_id > 8000
and mas_id < 9000
and mas_id = det_mas_id;

#!/usr/bin/perl
# -----------------------------------------------------------------
# file : updat.pm
# does : on line transactions test...
#
# notes : postgres version
# -----------------------------------------------------------------

sub dbconnect()
{
# connect with no autocommit...
#
$dbh = DBI->connect('DBI:Pg:dbname=dev1',$user,$pwd,{AutoCommit =>
0})
or die "Couldn't connect to database: " . DBI->errstr;
}

sub dbdisconnect()
{
# disconnect...
#
$dbh->disconnect;
}

sub dbparse()
{
# parse all statements here ( actually some databases do nothing
here...
#

# master select and update...
#
$sthmsel = $dbh->prepare("select * from master where mas_id = ? for
update")
or die "Couldn't prepare statement: " . $dbh->errstr;

$sthmupd = $dbh->prepare("update master set mas_amt = mas_amt + ?
where mas_id = ?")
or die "Couldn't prepare statement: " . $dbh->errstr;

# detail select and update...
#
$sthdsel = $dbh->prepare("select * from detail where det_mas_id = ?
and det_date > '1999-12-31' for update")
or die "Couldn't prepare statement: " . $dbh->errstr;

$sthdupd = $dbh->prepare("update detail set det_amt = det_amt + ?
where det_mas_id = ? and det_id =?")
or die "Couldn't prepare statement: " . $dbh->errstr;

# log insert...
#
$sthlins = $dbh->prepare("insert into masterlog values(?,datetime
'now')")
or die "Couldn't prepare statement: " . $dbh->errstr;
}

sub dbfree()
{
# free master and detail and log statements...
#
$sthmsel->finish;
$sthmupd->finish;
$sthdsel->finish;
$sthdupd->finish;
$sthlins->finish;
}

sub putlog()
{
# execute the log insert...
#
$sthlins->execute($masid);

}

sub getdetail()
{
# execute and fetch detail query...
#
$sthdsel->execute($masid);
my @data = $sthdsel->fetchrow_array();
my $detid = $data[0];

# execute detail update...
#
$sthdupd->execute($amt,$masid,$detid);

}

sub getmaster()
{

# execute and fetch master query...
#
$sthmsel->execute($masid);

my @data = $sthmsel->fetchrow_array();

# user typing allowamce
#
if ( $sleep == 0 )
{
sleep(1);
}

# get and update the detail...
#
getdetail;

# execute master update...
#
$sthmupd->execute($amt,$masid);

# log the transaction...
#
putlog;

# commit...
#
my $rc = $dbh->commit
or die $dbh->errstr;
}

sub init()
{
use DBI;

# two variables are "on" if set to zero
#
$debug = 1;
$sleep = 0;

$updatcnt = 0;
$updatlim = 100;

$amt = 10;
$maslim = 10000;
$masid = 0;

$begin = 0;
$end = 0;
$elapsed = 0;

$user = "updat";
$pwd = "updat";
$db = "dev1";

printf(" beginning $updatlim transactions...\n");
$begin = time;

# connect ...
#
dbconnect;

# parse all statements...
#
dbparse;

# loop as required...
#

while ( $updatcnt < $updatlim )
{
# get a random master id...
#
$masid = int ( rand $maslim ) + 1;
if ( $debug == 0 )
{
printf(" processing master $masid \n");
}
getmaster;
$updatcnt = $updatcnt + 1;

}

# calculate stats...
#
$end = time;
$elapsed = $end - $begin;
printf(" tranasctions = $updatlim\n");
printf(" elapsed = $elapsed\n");

# free all statement handles...
#
dbfree;

# disconnect...
#
dbdisconnect;
}

init;

Schema and queries for warehouse tests

/* -----------------------------------------------------------------
file : createwaretables.sql
does : create tables for ware example...
notes : dimension tables (dim0-2) have 900, 10000 and 1000
rows resp.
fact table (fact0) has 3000000 rows.
---------------------------------------------------------------- */

create table dim0
(
d0key int4,
d0f1 datetime,
d0f2 int4,
d0f3 int4,
d0f4 int4
);

create table dim1
(
d1key int4,
d1f1 varchar(20),
d1f2 varchar(20)
);

create table dim2
(
d2key int4,
d2f1 varchar(20),
d2f2 varchar(20)
);

create table fact0
(
d0key int4,
d1key int4,
d2key int4,
f1 int4,
f2 int4
);

/* -----------------------------------------------------------------
file : createwareindexes.sql
does : create indexes for ware example...
----------------------------------------------------------------- */

create unique index dim0_pk on dim0 using btree (d0key);
create unique index dim1_pk on dim1 using btree (d1key);
create unique index dim2_pk on dim2 using btree (d2key);
create index fact0_q1 on fact0 using btree (d0key);
create index fact0_q2 on fact0 using btree (d0key,d1key);
create index fact0_q3 on fact0 using btree (d0key,d1key,d2key);

/* -----------------------------------------------------------------
file : queries1-3.sql
does : star queries for warehouse...
notes : query 1 scans 100000 rows from fact0 and 30 rows
from dim0

query 2 scans 10000 rows from fact0 and
30 rows from dim0 and 10 rows from dim2

query 3 scans 10000 rows from fact0 and 30 rows
from dim0 and 10 rows from dim2 and 100 rows from dim1
----------------------------------------------------------------- */

select
d0.d0f1,
count(f.f1)
from dim0 d0,
fact0 f
where d0.d0key = f.d0key
and d0.d0f1 between '1996-05-01' and '1996-05-31'
group by d0.d0f1
;

select
d0.d0f1,
d2.d2f2,
count(f.f1)
from dim0 d0,
dim2 d2,
fact0 f
where d0.d0key = f.d0key
and d2.d2key = f.d2key
and d2.d2f2 = '90th att type'
and d0.d0f1 between '1996-05-01' and '1996-05-31'
group by d0.d0f1,d2.d2f2
;

select
d0.d0f1,
d1.d1f2,
d2.d2f2,
count(f.f1)
from dim0 d0,
dim1 d1,
dim2 d2,
fact0 f
where d0.d0key = f.d0key
and d1.d1key = f.d1key
and d2.d2key = f.d2key
and d2.d2f2 between '80th att type' and '90th att type'
and d1.d1f2 between '10th att type' and '50th att type'
and d0.d0f1 between '1996-05-01' and '1996-05-31'
group by d0.d0f1,d1.d1f2,d2.d2f2
;

Scripts to populate tables

Data Warehouse

#!/usr/bin/perl
# --------------------------------------------------------------------------
# file : popdim0.pm
# does : populate the dim0 timelike dimension...
# --------------------------------------------------------------------------

sub adddim()
{
# parse and execute the insert...
#
$sthins = $dbh->prepare("insert into dim0 values (?,('1999-05-01'::datetime + ?)::datetime,date_part('DAY',('1999-05-01'::datetime + ?)::datetime),date_part('MONTH',('1999-05-01'::datetime + ?)::datetime) )")
or die " could not prepare \n";

$sthins->execute($dimcnt,$dimcnt,$dimcnt,$dimcnt)
or die " failed to execute for $dimcnt\n";
}

sub attachdb()
{
# connect to the database...
#
$dbh = DBI->connect($datasource, $user, $pwd,{ AutoCommit => 0 })
or die "cannot connect to $datasource\n";

}

sub unattachdb()
{
# commit and disconnect...
#
$dbh->commit;
$dbh->disconnect();
}

sub init()
{
# setup and insert $dimlim rows for the timelike
# dimension...
#
#
use DBI;

$datasource = "DBI:Pg:dbname=dev1";
$user = "ware";
$pwd = "ware";
$dbh = 0;
$sthins = 0;

$dimlim = 900;
$dimcnt = 0;

attachdb();

while ( $dimcnt < $dimlim )
{
if ( $dimcnt%100 == 0 )
{
printf("processing ...$dimcnt\n");
}
adddim();
$dimcnt = $dimcnt + 1;
}

unattachdb();
}

init();

#!/usr/bin/perl
# --------------------------------------------------------------------------
# file : popdim1.pm
# does : populate the dim1 dimension...
# --------------------------------------------------------------------------

sub adddim()
{
# parse and execute the insert...
#
$sthins = $dbh->prepare("insert into dim1 values (?,? ||'th attribute',?%100 ||'th att type' )")
or die " could not prepare \n";

$sthins->execute($dimcnt,$dimcnt,$dimcnt)
or die " failed to execute for $dimcnt\n";
}

sub attachdb()
{
# connect to the database...
#
$dbh = DBI->connect($datasource, $user, $pwd,{ AutoCommit => 0 })
or die "cannot connect to $datasource\n";

}

sub unattachdb()
{
# commit and disconnect...
#
$dbh->commit;
$dbh->disconnect();
}

sub init()
{
# setup and insert $dimlim rows for the timelike
# dimension...
#
#
use DBI;

$datasource = "DBI:Pg:dbname=dev1";
$user = "ware";
$pwd = "ware";
$dbh = 0;
$sthins = 0;

$dimlim = 10000;
$dimcnt = 0;

attachdb();

while ( $dimcnt < $dimlim )
{
if ( $dimcnt%1000 == 0 )
{
printf("processing ...$dimcnt\n");
}
adddim();
$dimcnt = $dimcnt + 1;
}

unattachdb();
}

init();

#!/usr/bin/perl
# --------------------------------------------------------------------------
# file : popdim2.pm
# does : populate the dim2 dimension...
# --------------------------------------------------------------------------

sub adddim()
{
# parse and execute the insert...
#
$sthins = $dbh->prepare("insert into dim2 values (?,? ||'th attribute',?%100 ||'th att type' )")
or die " could not prepare \n";

$sthins->execute($dimcnt,$dimcnt,$dimcnt)
or die " failed to execute for $dimcnt\n";
}

sub attachdb()
{
# connect to the database...
#
$dbh = DBI->connect($datasource, $user, $pwd,{ AutoCommit => 0 })
or die "cannot connect to $datasource\n";

}

sub unattachdb()
{
# commit and disconnect...
#
$dbh->commit;
$dbh->disconnect();
}

sub init()
{
# setup and insert $dimlim rows for the timelike
# dimension...
#
#
use DBI;

$datasource = "DBI:Pg:dbname=dev1";
$user = "ware";
$pwd = "ware";
$dbh = 0;
$sthins = 0;

$dimlim = 1000;
$dimcnt = 0;

attachdb();

while ( $dimcnt < $dimlim )
{
if ( $dimcnt%100 == 0 )
{
printf("processing ...$dimcnt\n");
}
adddim();
$dimcnt = $dimcnt + 1;
}

unattachdb();
}

init();

#!/usr/bin/perl
# --------------------------------------------------------------------------
# file : popfact0.pm
# does : populate the fact0 fact...
# --------------------------------------------------------------------------

sub addfact()
{
# parse and execute the insert...
#
$sthins = $dbh->prepare("insert into fact0 values (?,?,?,100,100)")
or die " could not prepare \n";

$sthins->execute($d0key,$d1key,$d2key)
or die " failed to execute for $factcnt\n";
}

sub attachdb()
{
# connect to the database...
#
$dbh = DBI->connect($datasource, $user, $pwd,{ AutoCommit => 0 })
or die "cannot connect to $datasource\n";

}

sub unattachdb()
{
# disconnect...
#
$dbh->disconnect();
}

sub commitdb()
{
# commit...
#
$dbh->commit;
}

sub init()
{
# setup and insert $dimlim rows for the timelike
# dimension...
#
#
use DBI;

$datasource = "DBI:Pg:dbname=dev1";
$user = "ware";
$pwd = "ware";
$dbh = 0;
$sthins = 0;

# set up to add $dim0lim * $dim1lim * $dim2lim rows...
#
$dim0lim = 30;
$dim1lim = 1000;
$dim2lim = 100;
$dim0cnt = 1;
$dim1cnt = 1;
$dim2cnt = 1;
$factcnt = 1;
$begin = time();
$now = 0;
$elapsed = 0;

attachdb();

# do all the loops...
#
while ( $dim0cnt <= $dim0lim )
{
$d0key = 30 * $dim0cnt;
while ( $dim1cnt <= $dim1lim )
{
$d1key = 10 * $dim1cnt;
while ( $dim2cnt <= $dim2lim )
{
$d2key = 10 * $dim2cnt;

if ( $factcnt%10000 == 0 )
{
$now = time();
$elapsed = ($now - $begin)/ 60;
printf("processed ...$factcnt in $elapsed min\n");
commitdb();
}
addfact();
$factcnt = $factcnt + 1;

$dim2cnt = $dim2cnt + 1;
}
$dim1cnt = $dim1cnt + 1;
$dim2cnt = 1;
}
$dim0cnt = $dim0cnt + 1;
$dim1cnt = 1;
$dim2cnt = 1;
}

commitdb();
unattachdb();
}

init();

More scripts to populate tables

On line tables

<%
include("posglobals.phtm");
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>Example Database - Master</TITLE>
</HEAD>

<BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#000080"
ALINK="#FF0000"

<P>
<FONT SIZE = 5 COLOR="red"><BOLD><CENTER>Populate Master on <%printf("%s",$dbstring)%></CENTER></BOLD></FONT>
<HR>
<BR>
<%
/* connect to the database and if successful then
up a cursor for data
do not show errors if logon fails... */

$con = pg_pconnect("dbname=" . $dbstring . " user=" . $PHP_AUTH_USER . " password=" . $PHP_AUTH_PW);

if ( $con > 0 )
{
$rows = 0;
$rowlim = 10000;
$begin = time();

/* start the transaction... */

$cur = pg_exec($con,"begin");

/* insert the rows... */

for ( $rows = 0; $rows < $rowlim; $rows++ )
{
$cur = pg_exec($con,"insert into master values (" . $rows . "," . "'master " . $rows . "',100)");
}

/* commit the transaction... */

$cur = pg_exec($con,"commit");
pg_freeresult($cur);

$end = time();
if ( $rows == $rowlim)
{
$res = "successful";
}
else
{
$res = "not successful";
}

/* set up the table for formatting data... */
printf("<CENTER><TABLE BORDER=0 WIDTH=200>");
printf("<TR><TH BGCOLOR=#00DDDD>Variable</th><TH BGCOLOR=#00DDDD>Value</TH></TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>result</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%s</TD>",$res);
printf("</TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>rows</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%d</TD>",$rows);
printf("</TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>elapsed</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%d</TD>",$end - $begin);
printf("</TR>");

printf("</TABLE></CENTER>");

pg_close($con);
}
else
{
printf("<BR><CENTER><FONT SIZE = 4 COLOR=red>Unable to connect to the database</FONT><CENTER><BR>");
}
%>
</P>
<%
include("postail.phtm");
%>
</BODY>
</HTML>

<P>
<FONT SIZE = 5 COLOR="red"><BOLD><CENTER>Populate Detail on <%printf("%s",$dbstring)%></CENTER></BOLD></FONT>
<HR>
<BR>
<%
/* connect to the database and if successful then
up a cursor for data
do not show errors if logon fails... */
$con = @pg_pconnect("dbname=" . $dbstring . " user=" . $PHP_AUTH_USER . " password=" . $PHP_AUTH_PW);
if ( $con > 0 )
{
$masrowlim =10000;
$detrowlim = 100;
$cnt = 0;
$begin = time();
for ( $masrows = 1; $masrows < $masrowlim + 1; $masrows++ )
{
for ( $detrows = 1; $detrows < $detrowlim + 1; $detrows++ )
{
/* start a transaction.... */

if ( $cnt == 0 )
{
$cur = pg_exec($con,"begin");
}

/* do an insert and increemnt the counter.... */

$cur = pg_exec($con,"insert into detail values (" . $masrows * $detrows . ",". $masrows ."," . "datetime 'now'+ " . $detrows . "," . 10 * $detrows .")");
$cnt++;

/* if done enough the commit and reset the counter and
begin another one... */

if ( $cnt == 10000 )
{
$cnt = 1;
$cur = pg_exec($con,"commit");
$cur = pg_exec($con,"begin");
}

}
}

/* commit at the end... */

$cur = pg_exec($con,"commit");
pg_freeresult($cur);

$end = time();
$masrows--;
$detrows--;
if ( $masrows == $masrowlim)
{
$res = "successful";
}
else
{
$res = "not successful";
}

/* set up the table for formatting data... */
printf("<CENTER><TABLE BORDER=0 WIDTH=250>");
printf("<TR><TH BGCOLOR=#00DDDD>Variable</th><TH BGCOLOR=#00DDDD>Value</TH></TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>result</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%s</TD>",$res);
printf("</TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>rows</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%d</TD>",$masrows * $detrows);
printf("</TR>");

printf("<TR>");
printf("<TD BGCOLOR=#999999 FGCOLOR=green>elapsed</TD>");
printf("<TD BGCOLOR=#DDDDDD FGCOLOR=blue>%d</TD>",$end - $begin);
printf("</TR>");

printf("</TABLE></CENTER>");

pg_close($con);
}
else
{
printf("<BR><CENTER><FONT SIZE = 4 COLOR=red>Unable to connect to the database</FONT><CENTER><BR>");
}
%>
</P>
<%
include("postail.phtm");
%>
</BODY>
</HTML>

From bouncefilter Tue Nov 16 22:01:22 1999
Received: from web2103.mail.yahoo.com (web2103.mail.yahoo.com [128.11.68.247])
by hub.org (8.9.3/8.9.3) with SMTP id WAA43694
for <pgsql-general@postgresql.org>;
Tue, 16 Nov 1999 22:00:25 -0500 (EST)
(envelope-from mascarim@yahoo.com)
Message-ID: <19991117030020.29682.rocketmail@web2103.mail.yahoo.com>
Received: from [24.26.131.45] by web2103.mail.yahoo.com;
Tue, 16 Nov 1999 19:00:20 PST
Date: Tue, 16 Nov 1999 19:00:20 -0800 (PST)
From: Mike Mascari <mascarim@yahoo.com>
Subject: Re: [GENERAL] CREATE OPERATOR error
To: Brandon Ibach <bibach@infomansol.com>
Cc: pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Brandon Ibach <bibach@infomansol.com> wrote:

Quoting ^chewie <chewie@wookimus.net>:

On Tue, 16 Nov 1999, Brandon Ibach wrote:

BI> Can anybody explain what might be happening here?
BI>
BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
BI> abc-> procedure = vciceq, commutator = =* );
BI> ERROR: parser: parse error at or near "varchar"
BI>
BI> The function "vciceq" already exists, and works. I've tried a
BI> number of variations on the above with different spacing, with no
BI> success. Is there some syntax peculiarity I'm missing? This is
BI> on PostgreSQL 6.5.2 on a Linux x86 system (RedHat 5.1, kernel
BI> 2.0.34).

Isn't the operator '=*' a reserved operator for a right outer join?

That may be, but I just tried it with an operator name of =: and
got the same result, so that doesn't appear to be the problem here. :(

-Brandon :)

How about:

create operator =* (
leftarg = text,
rightarg = text,
procedure = vciceq,
commutator = =* );

with vciceq(text, text) being defined.

Mike Mascari
(mascarim@yahoo.com)

=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

From bouncefilter Wed Nov 17 01:22:26 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA73601;
Wed, 17 Nov 1999 01:22:20 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA00355;
Wed, 17 Nov 1999 02:22:25 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 17 Nov 1999 02:22:25 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-announce@postgresql.org
cc: pgsql-general@postgresql.org
Subject: Projects Database Online ...
Message-ID: <Pine.BSF.4.10.9911170218520.75865-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Okay, after procrastinating for too long, I've just redone the Projects
Database so that it follows similar formats to the Application Database
that I built the other day...

I'm slowly going through the old database (600+ records) and migrating
them over to the new one, cleaning it out as I go along...

The two Databases can be found at:

http://www.pgsql.com/app-index
http://www.pgsql.com/projects

The "visual format" will be worked on next, but the functionality is
there...if you entered a record in the old database (projects) and it
isn't in the new, its your choice...you can re-enter it (the new one asks
alot more information) or wait until I get to your record ...

Its still a work in progress...you'll notice that the Country list is
kinda short, etc...if your country isn't listed, let me know before you
add your record, as well as any other information that might be missing...

Thanks...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Nov 17 03:30:26 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA91743
for <pgsql-general@postgreSQL.org>;
Wed, 17 Nov 1999 03:29:47 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from ocis.ocis.net (IDENT:http@ocis.ocis.net [209.52.173.1])
by ocis.ocis.net (8.9.3/8.9.3) with SMTP id AAA03393
for pgsql-general@postgreSQL.org; Wed, 17 Nov 1999 00:29:46 -0800
Date: Wed, 17 Nov 1999 00:29:46 -0800
From: Jason Leach <jcl@mail.ocis.net>
Message-Id: <199911170829.AAA03393@ocis.ocis.net>
Subject: Java Ex.
To: undisclosed-recipients:;

hi,

Does anyone have a Java example of connecting to a DB and
executing a simple SQL command?

Thanks,
Jason

From bouncefilter Wed Nov 17 15:20:34 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA84319
for <pgsql-general@postgreSQL.org>;
Wed, 17 Nov 1999 15:19:54 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-24.dial.eunet.ch
[193.72.192.247])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id VAA15201
for <pgsql-general@postgreSQL.org>;
Wed, 17 Nov 1999 21:19:14 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id VAA01584
for <pgsql-general@postgreSQL.org>; Wed, 17 Nov 1999 21:19:12 +0100
Sender: herbie@eunet.ch
Message-ID: <383307BC.D8DA8C10@thinx.ch>
Date: Wed, 17 Nov 1999 20:53:33 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: postgres <pgsql-general@postgreSQL.org>
Subject: sql question
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have a sql problem which I can't solve. The following table is defined

create table AdressGroup
(
AdrGroup_Id INTEGER NOT NULL
DEFAULT NEXTVAL('adrverw_id_seq'),
Zeit DATETIME NOT NULL,
Group_Id INTEGER NOT NULL,
Adress_Id INTEGER NOT NULL
);

The table assigns adresses to adressgroups.

I'd like to select the adresses which belongs to one specific adressGroup and to no other group. If an adress has more than one entry in the AdressGroup
table it should not be in the projection.

I tried the following:

SELECT * FROM adressGroup
WHERE Group_Id = 6
AND EXISTS( SELECT AdrGroup_Id FROM adressGroup ag_alias
WHERE adressGroup.AdrGroup_Id = ag_alias.AdrGroup_Id
GROUP BY AdrGroup_Id HAVING COUNT(*) == 1 );

When I do this I get the following error:
ERROR: rewrite: aggregate column of view must be at rigth side in qual
ERROR: rewrite: aggregate column of view must be at rigth side in qual

Does anybody knows the solution? Thanks

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Herbert Liechti E-Mail: Herbert.Liechti@thinx.ch
ThinX networked business services Stahlrain 10, CH-5200 Brugg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From bouncefilter Wed Nov 17 15:22:34 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id PAA84804
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 15:22:12 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 19788 invoked by uid 417); 17 Nov 1999 20:50:39 -0000
Received: from p3564.nl.wish.net (HELO galaxy.galnet) (212.123.151.236)
by smtp.softhome.net with SMTP; 17 Nov 1999 20:50:39 -0000
Message-Id: <4.1.19991117211134.00918c40@pop.softhome.net>
X-Sender: j.roeleveld@pop.softhome.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Wed, 17 Nov 1999 21:21:52 +0100
To: pgsql-general@postgresql.org
From: "J. Roeleveld" <j.roeleveld@softhome.net>
Subject: Problem with CREATE RULE <something> ON DELETE (PostgreSQL
only executes the first expression)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

I have found what appears to be a bug in PostgreSQL, or is this a feature?
I don't think it's a feature, because the postgreSQL documentation state it
should work.

When creating delete-rules for views, i have found that only the first
expression is being executed, when
using multiple expressions.

I have managed to do this for Insert, and i think for Update as well...
although i haven't gotten around to testing that yet.

The following is the RULE-definition I use, it's for a View (
bedrijven_view ) which consists of
two tables ( adressen_table and bedrijven_table ).
When I change the sequence (eg. put the delete from bedrijven_table first)
it still only does the first statement.

CREATE RULE delete_bedrijven_view AS ON DELETE
TO bedrijven_view
DO INSTEAD (
DELETE FROM adressen_table
WHERE adres_id = get_adres_nummer(straatnaam,
huisnummer,postcode,land);
DELETE FROM bedrijven_table
WHERE firma_id = firma_id;
);

If you require more information, for instance a full list of statements
that can reproduce the problem,
please let me know, and I'll forward the bug-report I sent in yesterday
morning.

with kind regards,

Joost Roeleveld

PS. this is not a new problem, someone else reported this before, but he
hasn't found out how to solve
this problem either.

From bouncefilter Wed Nov 17 15:30:34 1999
Received: from portal1.visa.com (portal1.visa.com [198.80.42.2])
by hub.org (8.9.3/8.9.3) with SMTP id PAA85831
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 15:29:46 -0500 (EST)
(envelope-from knarayan@visa.com)
Received: by portal1.visa.com id MAA16517
(InterLock SMTP Gateway 4.2 for pgsql-general@postgresql.org);
Wed, 17 Nov 1999 12:29:45 -0800
Received: by portal1.visa.com (Protected-side Proxy Mail Agent-1);
Wed, 17 Nov 1999 12:29:45 -0800
Message-Id: <E3940A45EE1CD21196100001FA444AE702B0D18F@sw720x019.visa.com>
From: "Narayanan, Kannan" <knarayan@visa.com>
To: "'pgsql-general@postgresql.org'" <pgsql-general@postgresql.org>
Subject: How to select the millisecond/microsecond parts of the datetime c
olumn
Date: Wed, 17 Nov 1999 12:29:42 -0800
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

Hello,

Product version: Postgres 6.5.3

SELECT DATETIME('MILLISECOND', 'NOW'::DATETIME) always returns 0(ZERO) and
so does 'MICROSECOND'. However a reading of the manuals indicate that the
database supports much higher precision values. How do I retrieve the
additional precision values (beyond seconds) when I use the datetime field?
This is a requirement for a conversion project that I am working on. Could
someone help please.

Thanks
Kannan

From bouncefilter Wed Nov 17 15:41:34 1999
Received: from portal1.visa.com (portal1.visa.com [198.80.42.2])
by hub.org (8.9.3/8.9.3) with SMTP id PAA87956
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 15:40:47 -0500 (EST)
(envelope-from knarayan@visa.com)
Received: by portal1.visa.com id MAA20283
(InterLock SMTP Gateway 4.2 for pgsql-general@postgresql.org);
Wed, 17 Nov 1999 12:40:46 -0800
Received: by portal1.visa.com (Protected-side Proxy Mail Agent-1);
Wed, 17 Nov 1999 12:40:46 -0800
Message-Id: <E3940A45EE1CD21196100001FA444AE702B0D191@sw720x019.visa.com>
From: "Narayanan, Kannan" <knarayan@visa.com>
To: "'pgsql-general@postgresql.org'" <pgsql-general@postgresql.org>
Subject: FW: How to select the millisecond/microsecond parts of the dateti
me column
Date: Wed, 17 Nov 1999 12:40:40 -0800
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

Hello,

Product version: Postgres 6.5.3

SELECT DATETIME('MILLISECOND', 'NOW'::DATETIME) always returns 0(ZERO) and
so does 'MICROSECOND'. However a reading of the manuals indicate that the
database supports much higher precision values. How do I retrieve the
additional precision values (beyond seconds) when I use the datetime
field? This is a requirement for a conversion project that I am working
on. Could someone help please.

Thanks
Kannan

From bouncefilter Wed Nov 17 17:55:35 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA12866
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 17:54:37 -0500 (EST)
(envelope-from markir@hnz.co.nz)
Received: from mail.iconz.co.nz (oldmail.iconz.co.nz [202.14.100.36])
by trends.net (8.8.8/8.8.8) with ESMTP id RAA17218
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 17:54:21 -0500 (EST)
Received: from [192.173.20.11] (mail.hnz.co.nz [192.173.20.11])
by mail.iconz.co.nz (8.9.3/8.9.3) with SMTP id LAA154790942879203
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 11:53:23 +1300 (NZDT)
Received: from hiscorpxy01.hnz.co.nz by [192.173.20.11]
via smtpd (for mail.iconz.co.nz [210.48.22.36]) with SMTP;
17 Nov 1999 22:48:50 UT
Received: FROM hufin0.hnz.co.nz BY hiscorpxy01.hnz.co.nz ;
Thu Nov 18 11:50:46 1999 +1300
Received: from hudev0.hnz.co.nz (hudev0 [10.24.10.46]) by hufin0.hnz.co.nz
with ESMTP (8.8.6 (PHNE_14041)/8.7.1) id LAA12667 for
<pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 11:51:18 +1300 (NZDT)
Received: (from markir@localhost) by hudev0.hnz.co.nz (8.7.6/8.7.1) id
LAA12758 for pgsql-general@postgresql.org;
Thu, 18 Nov 1999 11:51:02 +1300 (NZDT)
Date: Thu, 18 Nov 1999 11:51:02 +1300 (NZDT)
From: Mark Kirkwood <markir@hnz.co.nz>
Message-Id: <199911172251.LAA12758@hudev0.hnz.co.nz>
subject: Slow Sort and Group By for Star Query
To: undisclosed-recipients:;

Dear List,

I have been attempting to get this simple "star" query to execute in less
than 12 secs :

select d0.d0f1,
count(f.f1)
from dim0 d0,
fact0 f
where d0.d0key = f.d0key
and d0.d0f1 between '1996-05-01' and '1996-05-31'
group by d0.d0f1 ;

this scans 100000 rows from fact0 ( 3000000 row table indexed on d0key)
and 31 rows from dim0 ( 900 rows indexed on d0key as well )
- see my posting on "4 databases" if you want more detail on the data
in these tables....

It gives the result :

d0f1 | count
-----------------------------+------
Thu May 30 00:00:00 1996 NZST|100000

( Note that only 1 of the 31 dim0 rows actually have corrosponding fact0 ones )

The query plan for this guy is :

Aggregate (cost=134804.38 rows=2289334 width=20)
-> Group (cost=134804.38 rows=2289334 width=20)
-> Sort (cost=134804.38 rows=2289334 width=20)
-> Nested Loop (cost=134804.38 rows=2289334 width=20)
-> Seq Scan on dim0 d0 (cost=36.70 rows=101 width=12)
-> Index Scan using fact0_q1 on fact0 f (cost=1334.33 rows=3000000 width=8)

After some fooling about I tried this query :

select max(d0.d0f1),
count(f.f1)
from dim0 d0,
fact0 f
where d0.d0key = f.d0key
and d0.d0f1 between '1996-05-01' and '1996-05-31' ;

which executes in 2 sec and gives the same result.

The query plan for this one is :

Aggregate (cost=134804.38 rows=2289334 width=20)
-> Nested Loop (cost=134804.38 rows=2289334 width=20)
-> Seq Scan on dim0 d0 (cost=36.70 rows=101 width=12)
-> Index Scan using fact0_q1 on fact0 f (cost=1334.33 rows=3000000 width=8)

therefore nested loop evaluation of the original query probably takes about
2 secs, and it is the sort / group by that takes the remaining 10 secs.

So can the sort / group by algorithm be improved ?

Cheers

Mark

From bouncefilter Wed Nov 17 18:05:36 1999
Received: from mail.iconz.co.nz (oldmail.iconz.co.nz [202.14.100.36])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA14541
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 18:04:32 -0500 (EST)
(envelope-from markir@hnz.co.nz)
Received: from [192.173.20.11] (mail.hnz.co.nz [192.173.20.11])
by mail.iconz.co.nz (8.9.3/8.9.3) with SMTP id MAA199410942879889
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 12:04:50 +1300 (NZDT)
Received: from hiscorpxy01.hnz.co.nz by [192.173.20.11]
via smtpd (for mail.iconz.co.nz [210.48.22.36]) with SMTP;
17 Nov 1999 23:00:17 UT
Received: FROM hufin0.hnz.co.nz BY hiscorpxy01.hnz.co.nz ;
Thu Nov 18 12:02:13 1999 +1300
Received: from hudev0.hnz.co.nz (hudev0 [10.24.10.46]) by hufin0.hnz.co.nz
with ESMTP (8.8.6 (PHNE_14041)/8.7.1) id MAA14436 for
<pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 12:02:45 +1300 (NZDT)
Received: (from markir@localhost) by hudev0.hnz.co.nz (8.7.6/8.7.1) id
MAA12792 for pgsql-general@postgresql.org;
Thu, 18 Nov 1999 12:02:29 +1300 (NZDT)
Date: Thu, 18 Nov 1999 12:02:29 +1300 (NZDT)
From: Mark Kirkwood <markir@hnz.co.nz>
Message-Id: <199911172302.MAA12792@hudev0.hnz.co.nz>
subject: RE: Using functions with indexes
To: undisclosed-recipients:;

Hi Alain

try this :

create function mylower( varchar) returns varchar as '
declare
lowered alias for $1;
begin
return lower(lowered);
end;
' language 'plpgsql';

create index mytext_s1 on mytext ( mylower(col) varchar_ops);

( assuming table mytext has column "col" )

You will need to have the Language plpgsql installed, if you have not do :

create function plpgsql_call_handler () returns opaque as
'/usr/local/pgsql/lib/plpgsql.so' language 'C';

create trusted procedural language 'plpgsql'
handler plpgsql_call_handler
lancompiler 'PL/pgSQL';

I found that using language sql to create "mylower" gave an error
at index create time - something about cannot use sql in this context..

Cheers

Mark

From bouncefilter Wed Nov 17 18:27:36 1999
Received: from c180a.mtalo.ton.tut.fi (qmailr@c180a.mtalo.ton.tut.fi
[193.166.90.125]) by hub.org (8.9.3/8.9.3) with SMTP id SAA17046
for <pgsql-general@postgresql.org>;
Wed, 17 Nov 1999 18:27:02 -0500 (EST)
(envelope-from oikarine@c180a.mtalo.ton.tut.fi)
Received: (qmail 5384 invoked by uid 500); 17 Nov 1999 23:27:00 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 17 Nov 1999 23:27:00 -0000
Date: Thu, 18 Nov 1999 01:26:59 +0200 (EET)
From: Juuso Oikarinen <oikarine@c180a.mtalo.ton.tut.fi>
To: pgsql-general@postgresql.org
Subject: indices not being used
Message-ID: <Pine.LNX.4.10.9911180118120.5337-100000@area51.ton.tut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

hello

I looked through a lot of previous messages, found many related
messages, but didn't find a solution to my problem.

I have a simple table of three fields,
timestamp datetime, reading1 real, and reading2 real, and
80k rows.

I have tried to create btree and hash indexes for the field timestamp, and
yes, have vacuumed it after that.

Explain still always tells me that it uses a sequential scan
for example for this simple query:

select max(timestamp) from readings;

Whis takes way too long, it takes many seconds. I would think indices
could speed this kind of simple queries tremendously.. I just don't
get postgresql to use them :(

Any suggestions?

My version of psql is 6.4.2.

rgds

Juuso Oikarinen http://www.students.tut.fi/~oikarine

Hiroshima '45 - Czernobyl '86 - Windows '95

From bouncefilter Thu Nov 18 01:34:05 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA69589
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 01:33:20 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA09915
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 02:33:26 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 18 Nov 1999 02:33:25 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
Subject: Projects Database grows ...
Message-ID: <Pine.BSF.4.10.9911180228060.75865-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I spent a good part of tonight migrating data from the old to new
database, so we are up to 66 projects that are listed...

I've also started to work on adding stats to the page, so that you can see
the break down of Operating System used, PostgreSQL Version used and
Country...

http://www.pgsql.com/projects

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Thu Nov 18 08:03:10 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA27621
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 08:02:18 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-22.dial.eunet.ch
[193.72.192.245])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id OAA17335
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 14:02:01 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id OAA01439
for <pgsql-general@postgreSQL.org>; Thu, 18 Nov 1999 14:02:16 +0100
Sender: herbie@eunet.ch
Message-ID: <3833F1E1.861CA6AB@thinx.ch>
Date: Thu, 18 Nov 1999 13:32:33 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: postgres <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] sql question
References: <C125682C.007DBA95.00@applications.sip.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Alain.Tesio@sip.fr wrote:

SELECT * FROM adressGroup
WHERE Group_Id = 6
AND EXISTS( SELECT AdrGroup_Id FROM adressGroup ag_alias
WHERE adressGroup.AdrGroup_Id = ag_alias.AdrGroup_Id
GROUP BY AdrGroup_Id HAVING COUNT(*) = 1);

One last try : your query looks pretty strange, maybe you should design it again
from scratch :
if I understand well, you want the rows in adressGroup with :

- Group_Id=6
- adrGroup_Id being unique

So why not :

SELECT * FROM adressGroup
WHERE Group_Id = 6
GROUP BY AdrGroup_Id HAVING COUNT(*)=1

No, when you say group_id = 6 then you have already the adresses which belongs to this
group and the result of the 'group by having' statement is always 1. That's not the solution. Consider the following situation.
The user sent a letter to the persons which belongs to the adressgroups 1,2 and 3.
Now he like to send the same letter to the persons which belongs
to adressgroup 6. But It can be that persons in group 6 belongs
either to group 1, 2 or 3. So the user wants only those adresses which belongs to adressgroup 6 and do not count to any other group. That's way I tried
the statement with the Exists clause.

Greetings Herbie

From bouncefilter Thu Nov 18 07:42:10 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA24436;
Thu, 18 Nov 1999 07:41:45 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
HAA22556;
Thu, 18 Nov 1999 07:41:38 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911181241.HAA22556@candle.pha.pa.us>
Subject: Book completed through chapter 6
To: PostgreSQL-announce <announce@postgreSQL.org>,
PostgreSQL-general <pgsql-general@postgreSQL.org>
Date: Thu, 18 Nov 1999 07:41:38 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have completed through chapter 6 of my book, "PostgreSQL:
Introduction and Concepts." Of course, this is only the first draft.
It can be viewed at:

http://www.postgresql.org/docs/awbook.html

There are major improvements in this version. I have added sections to
chapter 4 dealing with DEFAULT and functions/operators. The figure
placement and font usage is improved.

Chapter 6 covers using multiple tables and joins. This was a very
difficult chapter for me to write.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 18 09:43:12 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA78516;
Thu, 18 Nov 1999 09:42:31 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
JAA29292;
Thu, 18 Nov 1999 09:42:24 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911181442.JAA29292@candle.pha.pa.us>
Subject: Publisher looking for Reviewers
In-Reply-To: <000201bf31d2$204eedc0$a646f6d1@prenhall.com> from Paul Becker at
"Nov 18, 1999 09:07:56 am"
To: PostgreSQL-announce <announce@postgreSQL.org>,
PostgreSQL-general <pgsql-general@postgreSQL.org>
Date: Thu, 18 Nov 1999 09:42:24 -0500 (EST)
Reply-To: paul.becker@awl.com, pgman@candle.pha.pa.us
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Addison Wesley is seeking potential reviewers of manuscript material dealing
with PostgreSQL topics. The review process is used to ensure and improve the
quality of manuscripts before they are published in book form. Honorariums
will be paid for all review services. Reviewers may choose to remain
anonymous. If you are interested in reviewing please contact Paul Becker.
His address coordinates:

Email address: paul.becker@awl.com
Phone number: 914-268-8003

Please indicate from the following topics your area of special interest:

Introduction to PostqreSQL
PostgreSQL Administration
PostgreSQL Performance and Tuning
PostgreSQL Interface Programming
PostgreSQL Application Programming
Extending PostgreSQL from the Inside
PostgreSQL Internals
Other PostgreSQL

Please include a brief statement of your qualifications in these areas.

We look forward to hearing from you.

From bouncefilter Thu Nov 18 11:36:14 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA95091
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 11:35:21 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.9]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Thu, 18 Nov 1999 10:27:45 -0600
Sender: ed
Message-ID: <38342B46.C65ADF61@austin.rr.com>
Date: Thu, 18 Nov 1999 10:37:26 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: sql question
References: <199911180404.XAA46562@hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Date: Wed, 17 Nov 1999 20:53:33 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Subject: sql question

I have a sql problem which I can't solve. The following table is defined

create table AdressGroup
(
AdrGroup_Id INTEGER NOT NULL
DEFAULT NEXTVAL('adrverw_id_seq'),
Zeit DATETIME NOT NULL,
Group_Id INTEGER NOT NULL,
Adress_Id INTEGER NOT NULL
);

The table assigns adresses to adressgroups.

I'd like to select the adresses which belongs to one specific adressGroup and to no other group. If an adress has more than one entry in the AdressGroup
table it should not be in the projection.

I tried the following:

SELECT * FROM adressGroup
WHERE Group_Id = 6
AND EXISTS( SELECT AdrGroup_Id FROM adressGroup ag_alias
WHERE adressGroup.AdrGroup_Id = ag_alias.AdrGroup_Id
GROUP BY AdrGroup_Id HAVING COUNT(*) == 1 );

When I do this I get the following error:
ERROR: rewrite: aggregate column of view must be at rigth side in qual
ERROR: rewrite: aggregate column of view must be at rigth side in qual

Does anybody knows the solution? Thanks

Not sure about the error above, other than the apparent typos with "adressGroup", but I think you can get what you're after with this:

SELECT *
FROM AdressGroup ag
WHERE ag.Group_Id = 6 AND NOT EXISTS (
SELECT AdrGroup_Id
FROM AddressGroup ag2
WHERE ag2.AdrGroup_Id = ag.AdrGroup_Id AND ag2.Group_Id <> 6);

Hope that helps.

From bouncefilter Thu Nov 18 12:31:14 1999
Received: from noc.unc.edu.ar (noc.unc.edu.ar [170.210.2.129])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA04141
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 12:30:24 -0500 (EST)
(envelope-from montes@noc.unc.edu.ar)
Received: from unc.edu.ar (localhost [127.0.0.1])
by noc.unc.edu.ar (8.9.1b+Sun/8.9.1) with ESMTP id OAA15685
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 14:30:15 -0300 (ARG)
Sender: montes@noc.unc.edu.ar
Message-ID: <383437A6.41CCC1D5@unc.edu.ar>
Date: Thu, 18 Nov 1999 14:30:15 -0300
From: Miguel Montes <montes@noc.unc.edu.ar>
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Problems with datetime
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi
I'm using postgres to track events. I need to insert date and time
of these events, and i'm having trouble when the seconds are 00.
Here is an example with psql

miguel=> create table tmp (d datetime);
CREATE
miguel=> insert into tmp values ('1999-11-18 13:00:00');
INSERT 20585 1
miguel=> select * from tmp;
d
-------------------------------
Thu Nov 18 13:00:60.00 1999 ART
(1 row)

13:00:00 has changed to 13:00:00. Now if I try to insert this value I
get: ERROR: Bad datetime external representation 'Thu Nov 18
13:00:60.00 1999 ART'

I'm using Postgresql 6.5.1, as it comes with Linux Mandrake 6.1.
Thanks in advance
Miguel Montes

From bouncefilter Thu Nov 18 15:08:15 1999
Received: from osprey.astro.umass.edu (root@osprey.astro.umass.edu
[128.119.51.182]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA22938
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 15:07:34 -0500 (EST)
(envelope-from weinberg@osprey.astro.umass.edu)
Received: from osprey.astro.umass.edu (weinberg@localhost [127.0.0.1])
by osprey.astro.umass.edu (8.9.3/8.9.3/Debian/GNU) with ESMTP id
PAA18109; Thu, 18 Nov 1999 15:07:31 -0500
Message-Id: <199911182007.PAA18109@osprey.astro.umass.edu>
X-Mailer: exmh version 2.0.2 2/24/98 (debian)
To: pgsql-general@postgreSQL.org
cc: weinberg@osprey.astro.umass.edu
Subject: How to efficiently update many records at once
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 18 Nov 1999 15:07:31 -0500
From: Martin Weinberg <weinberg@osprey.astro.umass.edu>

I have two tables with different information indexed by a unique key.
I want to update the contents of one table if an entry exists in
a second table.

Some playing with explain suggests that the optimum strategy using
UPDATE is:

update table1 set x=1 from table2 where key in
(select key from table2 where table1.key=table2.key);

This *does work* but can double the size of the database (until
the next vacuum). Is there an efficient way to do this in situ?

The problem is that my database is 100GB and only have 132GB
of space.

Sorry if this is a SQL/DBMS FAQ . . . I couldn't find any guidance
in the books and newsgroups.

--Martin

===========================================================================

Martin Weinberg Phone: (413) 545-3821
Dept. of Physics and Astronomy FAX: (413) 545-2117/0648
530 Graduate Research Tower
University of Massachusetts
Amherst, MA 01003-4525

From bouncefilter Thu Nov 18 15:52:16 1999
Received: from mail1.cybersol.com ([207.142.110.12])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA29149
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 15:52:15 -0500 (EST)
(envelope-from faqir@andrews.edu)
Received: from riker ([208.46.50.66]) by mail1.cybersol.com
(Post.Office MTA v3.5.3 release 223 ID# 0-57990U2200L100S0V35)
with SMTP id com for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 15:52:01 -0500
Message-Id: <3.0.3.32.19991118154423.00b68c90@143.207.5.12>
X-Sender: faqir@143.207.5.12
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 18 Nov 1999 15:44:23 -0500
To: pgsql-general@postgreSQL.org
From: Faqir Abu Tahir <faqir@andrews.edu>
Subject:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi all,

According to a dbi mailing list buddy's instructions I set the env vars
like so in my /etc/profile

PGDATA=/usr/lib/pgsql
PGLIB=/usr/lib/pgsql
export PGDATA PGLIB

But still the problem exists...I can't connect to the pgsql monitor
program. I need to start the post master before I can successfully enter
the command
%> pgsql

running the postmaster gives me the following error:

[faqir@picard faqir]$ postmaster
/usr/bin/postmaster does not find the database system. Expected to find it
in t
he PGDATA directory "/usr/lib/pgsql", but unable to open file with pathname
"/us
r/lib/pgsql/base/template1/pg_class".

No data directory -- can't proceed.

All help is appreciated. Even it is just brainstorming type:)

With Thanks,

Sincerely,
Tahir

From bouncefilter Thu Nov 18 15:59:19 1999
Received: from mail1.cybersol.com ([207.142.110.12])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA29920
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 15:58:16 -0500 (EST)
(envelope-from tahir@cybersol.com)
Received: from riker ([208.46.50.56]) by mail1.cybersol.com
(Post.Office MTA v3.5.3 release 223 ID# 0-57990U2200L100S0V35)
with SMTP id com for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 15:58:14 -0500
Message-Id: <3.0.3.32.19991118155037.009944e0@143.207.5.12>
X-Sender: faqir@143.207.5.12
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 18 Nov 1999 15:50:37 -0500
To: pgsql-general@postgreSQL.org
From: tahir@cybersol.com (Faqir, Tahir)
Subject: postmaster problem
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi all,

According to a dbi mailing list buddy's instructions I set the env vars
like so in my /etc/profile

PGDATA=/usr/lib/pgsql
PGLIB=/usr/lib/pgsql
export PGDATA PGLIB

But still the problem exists...I can't connect to the pgsql monitor
program. I need to start the post master before I can successfully enter
the command
%> pgsql

running the postmaster gives me the following error:

No data directory -- can't proceed.

All help is appreciated. Even it is just brainstorming type:)

With Thanks,

Sincerely,
Tahir

PS...by the way why is postmaster used or needed?

From bouncefilter Thu Nov 18 15:54:16 1999
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA29299
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 15:54:03 -0500 (EST)
(envelope-from strohmayer@itd.nrl.navy.mil)
Received: from itd.nrl.navy.mil (fw1-5540.itd.nrl.navy.mil [132.250.80.6])
by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id PAA06591;
Thu, 18 Nov 1999 15:53:49 -0500 (EST)
Received: from osa (osa.fw5540.net [10.0.2.26])
by itd.nrl.navy.mil (8.9.0/8.9.0) with ESMTP id PAA29453;
Thu, 18 Nov 1999 15:53:29 -0500 (EST)
Message-Id: <4.2.0.58.19991118154606.00a52e00@pop>
X-Sender: strohmay@pop
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Thu, 18 Nov 1999 15:59:42 -0500
To: Martin Weinberg <weinberg@osprey.astro.umass.edu>,
pgsql-general@postgresql.org
From: Beth Strohmayer <strohmayer@itd.nrl.navy.mil>
Subject: Re: [GENERAL] How to efficiently update many records at once
In-Reply-To: <199911182007.PAA18109@osprey.astro.umass.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:07 PM 11/18/1999 , Martin Weinberg wrote:

I have two tables with different information indexed by a unique key.
I want to update the contents of one table if an entry exists in
a second table.

Some playing with explain suggests that the optimum strategy using
UPDATE is:

update table1 set x=1 from table2 where key in
(select key from table2 where table1.key=table2.key);

This *does work* but can double the size of the database (until
the next vacuum). Is there an efficient way to do this in situ?

The problem is that my database is 100GB and only have 132GB
of space.

Martin,

You could try using a simple Join clause:

update table1
set x=1
from table2
where table2.key = table1.key;

or the Exists clause:

update table1
set x=1
from table2
where exists (select * from table2 where table2.key = table1.key); (In this
one I'm not sure if the from table2 is needed in the update section.)

Have not had a chance to test these, sorry! Hope they help.

Beth :-)
_______________________________________________
/ Beth L Strohmayer / Software Engineer _____)
/ ITT Industries, Systems Division (_____|______________________
/ @ Naval Research Laboratory, Code 5542 | \
\ 4555 Overlook Ave. SW | Phone: (202) 404-3798 \
\ Washington, DC 20375 | Fax: (202) 404-7942 \
\_________________________________________| /
| strohmayer@itd.nrl.navy.mil /
|____________________________/

From bouncefilter Thu Nov 18 16:04:16 1999
Received: from osprey.astro.umass.edu (root@osprey.astro.umass.edu
[128.119.51.182]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA30843
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 16:03:43 -0500 (EST)
(envelope-from weinberg@osprey.astro.umass.edu)
Received: from osprey.astro.umass.edu (weinberg@localhost [127.0.0.1])
by osprey.astro.umass.edu (8.9.3/8.9.3/Debian/GNU) with ESMTP id
QAA18379; Thu, 18 Nov 1999 16:03:25 -0500
Message-Id: <199911182103.QAA18379@osprey.astro.umass.edu>
X-Mailer: exmh version 2.0.2 2/24/98 (debian)
To: Beth Strohmayer <strohmayer@itd.nrl.navy.mil>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to efficiently update many records at once
In-reply-to: Your message of "Thu, 18 Nov 1999 15:59:42 EST."
<4.2.0.58.19991118154606.00a52e00@pop>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 18 Nov 1999 16:03:25 -0500
From: Martin Weinberg <weinberg@osprey.astro.umass.edu>

Beth,

Thanks for the reply. I did test both of these and they work
but more slowly. The behavior of the database is the same:
updates appear to be appended to the database until the next
vacuum.

--M

Beth Strohmayer wrote on Thu, 18 Nov 1999 15:59:42 EST

At 03:07 PM 11/18/1999 , Martin Weinberg wrote:

I have two tables with different information indexed by a unique key.
I want to update the contents of one table if an entry exists in
a second table.

Some playing with explain suggests that the optimum strategy using
UPDATE is:

update table1 set x=1 from table2 where key in
(select key from table2 where table1.key=table2.key);

This *does work* but can double the size of the database (until
the next vacuum). Is there an efficient way to do this in situ?

The problem is that my database is 100GB and only have 132GB
of space.

Martin,

You could try using a simple Join clause:

update table1
set x=1
from table2
where table2.key = table1.key;

or the Exists clause:

update table1
set x=1
from table2
where exists (select * from table2 where table2.key = table1.key); (In this
one I'm not sure if the from table2 is needed in the update section.)

Have not had a chance to test these, sorry! Hope they help.

Beth :-)
_______________________________________________
/ Beth L Strohmayer / Software Engineer _____)
/ ITT Industries, Systems Division (_____|______________________
/ @ Naval Research Laboratory, Code 5542 | \
\ 4555 Overlook Ave. SW | Phone: (202) 404-3798 \
\ Washington, DC 20375 | Fax: (202) 404-7942 \
\_________________________________________| /
| strohmayer@itd.nrl.navy.mil /
|____________________________/

From bouncefilter Thu Nov 18 16:41:16 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA39654
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 16:40:16 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-2.dial.eunet.ch
[193.72.192.225])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id WAA18740;
Thu, 18 Nov 1999 22:39:26 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id WAA04961;
Thu, 18 Nov 1999 22:39:20 +0100
Sender: herbie@eunet.ch
Message-ID: <38346B06.61F74C93@thinx.ch>
Date: Thu, 18 Nov 1999 22:09:27 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: postgres <pgsql-general@postgreSQL.org>
CC: Ed Loehr <ELOEHR@austin.rr.com>
Subject: Re: [GENERAL] Re: sql question
References: <199911180404.XAA46562@hub.org> <38342B46.C65ADF61@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ed Loehr wrote:

From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Subject: sql question

I have a sql problem which I can't solve. The following table is defined

create table AdressGroup
(
AdrGroup_Id INTEGER NOT NULL
DEFAULT NEXTVAL('adrverw_id_seq'),
Zeit DATETIME NOT NULL,
Group_Id INTEGER NOT NULL,
Adress_Id INTEGER NOT NULL
);

The table assigns adresses to adressgroups.

I'd like to select the adresses which belongs to one specific adressGroup and to no other group. If an adress has more than one entry in the AdressGroup
table it should not be in the projection.

I tried the following:

SELECT * FROM adressGroup
WHERE Group_Id = 6
AND EXISTS( SELECT AdrGroup_Id FROM adressGroup ag_alias
WHERE adressGroup.AdrGroup_Id = ag_alias.AdrGroup_Id
GROUP BY AdrGroup_Id HAVING COUNT(*) = 1 );

When I do this I get the following error:
ERROR: rewrite: aggregate column of view must be at rigth side in qual
ERROR: rewrite: aggregate column of view must be at rigth side in qual

Does anybody knows the solution? Thanks

Not sure about the error above, other than the apparent typos with "adressGroup", but I think you can get what you're after with this:

SELECT *
FROM AdressGroup ag
WHERE ag.Group_Id = 6 AND NOT EXISTS (
SELECT AdrGroup_Id
FROM AddressGroup ag2
WHERE ag2.AdrGroup_Id = ag.AdrGroup_Id AND ag2.Group_Id <> 6);

The query does not produce the estimated result :-/( It returns all records from
adressgroup 6. It seems that the problem can not be solved in a single sql-statement.
I assume that the above statement joins the table with the alias table with the
subset of adress group 6.
Probably I do it with a temporary table:

Create temp table tempGroup(adrGroup_id integer, groupcounter integer);
INSERT INTO tempGroup
SELECT adrGroup_Id, count(*) FROM adrGroup GROUP BY 1 HAVING COUNT(*) = 1);
SELECT * from adrGroup, tempGroup
WHERE adrGroup.adrGroup_id = tempGroup.adrGroup_id
AND adrGroup.group_id = 7;

This is working but without the desired performance :-(

Thanks anyway
Herbie

From bouncefilter Thu Nov 18 16:45:16 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA39987
for <pgsql-general@postgreSQL.org>;
Thu, 18 Nov 1999 16:43:59 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-3.dial.eunet.ch
[193.72.192.226])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id WAA18748;
Thu, 18 Nov 1999 22:43:08 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id WAA05092;
Thu, 18 Nov 1999 22:43:02 +0100
Sender: herbie@eunet.ch
Message-ID: <38346BE5.E05AB612@thinx.ch>
Date: Thu, 18 Nov 1999 22:13:10 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Faqir, Tahir" <tahir@cybersol.com>,
postgres <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] postmaster problem
References: <3.0.3.32.19991118155037.009944e0@143.207.5.12>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Faqir, Tahir" wrote:

running the postmaster gives me the following error:

[faqir@picard faqir]$ postmaster
/usr/bin/postmaster does not find the database system. Expected to find it
in t
he PGDATA directory "/usr/lib/pgsql", but unable to open file with pathname
"/usr/lib/pgsql/base/template1/pg_class".

No data directory -- can't proceed.

Did you run initdb? --> See INSTALL readme

18. Create the database installation from your
Postgres superuser account (typically account
postgres). Do not do the following as root! This
would be a major security hole. Type
$ initdb

From bouncefilter Fri Nov 19 10:32:32 1999
Received: from pusher.go.service-transport.com
(IDENT:qmailr@DIALUP59.TNCOO.USIT.NET [216.80.129.187])
by hub.org (8.9.3/8.9.3) with SMTP id KAA18893
for <pgsql-general@postgreSQL.org>;
Fri, 19 Nov 1999 10:32:02 -0500 (EST)
(envelope-from shawn.pursley@service-transport.com)
Received: (qmail 18612 invoked from network); 19 Nov 1999 00:36:09 -0000
Received: from cs01.go.service-transport.com (HELO shawn) (10.0.1.3)
by pusher.go.service-transport.com with SMTP; 19 Nov 1999 00:36:09 -0000
Message-ID: <00b701bf321d$6f313740$0301000a@go.servicetransport.com>
From: "Shawn Pursley" <shawn.pursley@service-transport.com>
To: <pgsql-general@postgreSQL.org>
Subject: Trying to SELECT via web server using PHP
Date: Thu, 18 Nov 1999 16:28:21 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_009E_01BF31E1.EDA3C980"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_009E_01BF31E1.EDA3C980
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greetings,

I've got pgsql running fine from the command line, but I'm having =
problems using PHP to do a select...suggestions?

results in:
Warning: PostgresSQL query failed: ERROR: employees: Permission denied. =
in /home/httpd/html/connect2.php3 on line 6

Warning: 0 is not a PostgresSQL link index in =
/home/httpd/html/connect2.php3 on line 8

Warning: 0 is not a PostgresSQL link index in =
/home/httpd/html/connect2.php3 on line 9

If I change the host, the thing really blows a gasket.

TIA,
Shawn Pursley(shawn.pursley@service-transport.com)
Network Administrator
Service Transport

------=_NextPart_000_009E_01BF31E1.EDA3C980
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2722.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Greetings,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>I've got pgsql running fine from the command line, =
but I'm=20
having problems using PHP to do a select...suggestions?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2><html><BR><body><BR><?php<BR>$conn =
=3D=20
pg_Connect("host=3Dlocalhost port=3D5432 =
dbname=3Dcustomers");<BR>$result =3D=20
pg_exec($conn, 'select * from employees');<BR>echo $result;<BR>pg_exec=20
($database, "commit");<BR>pg_exec ($database,=20
"end");<BR>?><BR></body><BR></html></FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>results in:</FONT></DIV>
<DIV><FONT size=3D2><B>Warning</B>: PostgresSQL query failed: ERROR: =
employees:=20
Permission denied. in <B>/home/httpd/html/connect2.php3</B> on line=20
<B>6</B><BR><BR><B>Warning</B>: 0 is not a PostgresSQL link index in=20
<B>/home/httpd/html/connect2.php3</B> on line =
<B>8</B><BR><BR><B>Warning</B>: 0=20
is not a PostgresSQL link index in <B>/home/httpd/html/connect2.php3</B> =
on line=20
<B>9</B><BR></FONT></DIV>
<DIV><FONT size=3D2>If I change the host, the thing really blows a=20
gasket.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>TIA,</FONT></DIV>
<DIV><FONT size=3D2>Shawn Pursley(<A=20
href=3D"mailto:shawn.pursley@service-transport.com">shawn.pursley@service=
-transport.com</A>)<BR>Network=20
Administrator<BR>Service Transport<BR><BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_009E_01BF31E1.EDA3C980--

From bouncefilter Thu Nov 18 19:16:20 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA86863
for <pgsql-general@postgresql.org>;
Thu, 18 Nov 1999 19:15:48 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.9]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Thu, 18 Nov 1999 18:08:13 -0600
Sender: ed
Message-ID: <38349732.5F1E85BD@austin.rr.com>
Date: Thu, 18 Nov 1999 18:17:54 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Herbert Liechti <Herbert.Liechti@thinx.ch>
CC: postgres <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Re: sql question
References: <199911180404.XAA46562@hub.org> <38342B46.C65ADF61@austin.rr.com>
<38346B06.61F74C93@thinx.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Herbert Liechti wrote:

Ed Loehr wrote:

From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Subject: sql question

I have a sql problem which I can't solve. The following table is defined

create table AdressGroup
(
AdrGroup_Id INTEGER NOT NULL
DEFAULT NEXTVAL('adrverw_id_seq'),
Zeit DATETIME NOT NULL,
Group_Id INTEGER NOT NULL,
Adress_Id INTEGER NOT NULL
);

The table assigns adresses to adressgroups.

I'd like to select the adresses which belongs to one specific adressGroup and to no other group. If an adress has more than one entry in the AdressGroup
table it should not be in the projection.

I tried the following:

SELECT * FROM adressGroup
WHERE Group_Id = 6
AND EXISTS( SELECT AdrGroup_Id FROM adressGroup ag_alias
WHERE adressGroup.AdrGroup_Id = ag_alias.AdrGroup_Id
GROUP BY AdrGroup_Id HAVING COUNT(*) = 1 );

When I do this I get the following error:
ERROR: rewrite: aggregate column of view must be at rigth side in qual
ERROR: rewrite: aggregate column of view must be at rigth side in qual

Does anybody knows the solution? Thanks

Not sure about the error above, other than the apparent typos with "adressGroup", but I think you can get what you're after with this:

SELECT *
FROM AdressGroup ag
WHERE ag.Group_Id = 6 AND NOT EXISTS (
SELECT AdrGroup_Id
FROM AddressGroup ag2
WHERE ag2.AdrGroup_Id = ag.AdrGroup_Id AND ag2.Group_Id <> 6);

The query does not produce the estimated result :-/( It returns all records from
adressgroup 6. It seems that the problem can not be solved in a single sql-statement.
I assume that the above statement joins the table with the alias table with the
subset of adress group 6.
Probably I do it with a temporary table:

Create temp table tempGroup(adrGroup_id integer, groupcounter integer);
INSERT INTO tempGroup
SELECT adrGroup_Id, count(*) FROM adrGroup GROUP BY 1 HAVING COUNT(*) = 1);
SELECT * from adrGroup, tempGroup
WHERE adrGroup.adrGroup_id = tempGroup.adrGroup_id
AND adrGroup.group_id = 7;

This is working but without the desired performance :-(

I meant to use Address_Id where I used adrGroup_id. Sorry 'bout that. Try this, it seems to work:

SELECT *
FROM AddressGroup ag1
WHERE NOT EXISTS (
SELECT *
FROM AddressGroup ag2
WHERE ag1.Address_Id = ag2.Address_Id AND
ag1.Group_Id <> ag2.Group_Id);

A working demonstration is below.

Cheers,
Ed

mydb=> create sequence adrverw_id_seq;
CREATE
mydb=> create table AddressGroup
mydb-> (
mydb-> AdrGroup_Id INTEGER NOT NULL DEFAULT NEXTVAL('adrverw_id_seq'),
mydb-> Zeit DATETIME NOT NULL,
mydb-> Group_Id INTEGER NOT NULL,
mydb-> Address_Id INTEGER NOT NULL
mydb-> );
CREATE
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',5,1);
NOTICE: adrverw_id_seq.nextval: sequence was re-created
NOTICE: adrverw_id_seq.nextval: sequence was re-created
INSERT 3669904 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,1);
INSERT 3669905 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,2);
INSERT 3669906 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,3);
INSERT 3669907 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',7,3);
INSERT 3669908 1
mydb=>
mydb=> SELECT * FROM AddressGroup;
adrgroup_id|zeit |group_id|address_id
-----------+----------------------------+--------+----------
1|Thu Nov 18 18:10:50 1999 CST| 5| 1
2|Thu Nov 18 18:10:50 1999 CST| 6| 1
3|Thu Nov 18 18:10:50 1999 CST| 6| 2
4|Thu Nov 18 18:10:50 1999 CST| 6| 3
5|Thu Nov 18 18:10:50 1999 CST| 7| 3
(5 rows)

mydb=>
mydb=> SELECT *
mydb-> FROM AddressGroup ag1
mydb-> WHERE NOT EXISTS (
mydb-> SELECT *
mydb-> FROM AddressGroup ag2
mydb-> WHERE ag1.Address_Id = ag2.Address_Id AND
mydb-> ag1.Group_Id <> ag2.Group_Id);
adrgroup_id|zeit |group_id|address_id
-----------+----------------------------+--------+----------
3|Thu Nov 18 18:10:50 1999 CST| 6| 2
(1 row)

From bouncefilter Fri Nov 19 02:41:28 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA47074
for <pgsql-general@postgreSQL.org>;
Fri, 19 Nov 1999 02:41:13 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-15.dial.eunet.ch
[193.72.192.238])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id IAA19997;
Fri, 19 Nov 1999 08:40:54 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id IAA00408;
Fri, 19 Nov 1999 08:40:47 +0100
Sender: herbie@eunet.ch
Message-ID: <3834F70F.FB590B95@thinx.ch>
Date: Fri, 19 Nov 1999 08:06:56 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Loehr <ELOEHR@austin.rr.com>, postgres <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: sql question
References: <199911180404.XAA46562@hub.org> <38342B46.C65ADF61@austin.rr.com>
<38346B06.61F74C93@thinx.ch> <38349732.5F1E85BD@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ed Loehr wrote:

Create temp table tempGroup(adrGroup_id integer, groupcounter integer);
INSERT INTO tempGroup
SELECT adrGroup_Id, count(*) FROM adrGroup GROUP BY 1 HAVING COUNT(*) = 1);
SELECT * from adrGroup, tempGroup
WHERE adrGroup.adrGroup_id = tempGroup.adrGroup_id
AND adrGroup.group_id = 7;

This is working but without the desired performance :-(

I meant to use Address_Id where I used adrGroup_id. Sorry 'bout that. Try this, it seems to work:

SELECT *
FROM AddressGroup ag1
WHERE NOT EXISTS (
SELECT *
FROM AddressGroup ag2
WHERE ag1.Address_Id = ag2.Address_Id AND
ag1.Group_Id <> ag2.Group_Id);

A working demonstration is below.

Cheers,
Ed

mydb=> create sequence adrverw_id_seq;
CREATE
mydb=> create table AddressGroup
mydb-> (
mydb-> AdrGroup_Id INTEGER NOT NULL DEFAULT NEXTVAL('adrverw_id_seq'),
mydb-> Zeit DATETIME NOT NULL,
mydb-> Group_Id INTEGER NOT NULL,
mydb-> Address_Id INTEGER NOT NULL
mydb-> );
CREATE
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',5,1);
NOTICE: adrverw_id_seq.nextval: sequence was re-created
NOTICE: adrverw_id_seq.nextval: sequence was re-created
INSERT 3669904 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,1);
INSERT 3669905 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,2);
INSERT 3669906 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',6,3);
INSERT 3669907 1
mydb=> insert into AddressGroup(Zeit,Group_Id,Address_Id) values ('now',7,3);
INSERT 3669908 1
mydb=>
mydb=> SELECT * FROM AddressGroup;
adrgroup_id|zeit |group_id|address_id
-----------+----------------------------+--------+----------
1|Thu Nov 18 18:10:50 1999 CST| 5| 1
2|Thu Nov 18 18:10:50 1999 CST| 6| 1
3|Thu Nov 18 18:10:50 1999 CST| 6| 2
4|Thu Nov 18 18:10:50 1999 CST| 6| 3
5|Thu Nov 18 18:10:50 1999 CST| 7| 3
(5 rows)

mydb=>
mydb=> SELECT *
mydb-> FROM AddressGroup ag1
mydb-> WHERE NOT EXISTS (
mydb-> SELECT *
mydb-> FROM AddressGroup ag2
mydb-> WHERE ag1.Address_Id = ag2.Address_Id AND
mydb-> ag1.Group_Id <> ag2.Group_Id);
adrgroup_id|zeit |group_id|address_id
-----------+----------------------------+--------+----------
3|Thu Nov 18 18:10:50 1999 CST| 6| 2
(1 row)

It is working ;-) Thanks

Herbie

From bouncefilter Fri Nov 19 04:03:27 1999
Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA59213
for <pgsql-general@postgreSQL.org>;
Fri, 19 Nov 1999 04:03:02 -0500 (EST)
(envelope-from mirko@rccr.cremona.it)
Received: from next.rccr.cremona.it (modem-2-7.rccr.cremona.it [192.168.2.27])
by rccr1.rccr.cremona.it (8.9.3/8.9.3) with ESMTP id KAA09465
for <pgsql-general@postgreSQL.org>; Fri, 19 Nov 1999 10:02:23 +0100
Received: (from mirko@localhost) by next.rccr.cremona.it (8.8.4/8.8.4)
id KAA01580 for pgsql-general@postgreSQL.org;
Fri, 19 Nov 1999 10:06:45 +0100 (MET)
Message-Id: <199911190906.KAA01580@next.rccr.cremona.it>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v118.2)
X-Nextstep-Mailer: Mail 3.3 (Enhance 2.1)
Received: by NeXT.Mailer (1.118.2)
From: Mirko Viviani <mirko.viviani@rccr.cremona.it>
Date: Fri, 19 Nov 99 10:06:45 +0100
To: pgsql-general@postgreSQL.org
Subject: Problems with pg_dump...
Reply-To: mirko.viviani@rccr.cremona.it

Ciao...

I have noticed some problems with pg_dump and 6.5.3 (maybe already you know)

1. A "" varchar in dumped with a NULL value.
2. Is it not possible to dump also the original DateStyle ?

Thank you.

---
Bye,
Mirko <mirko.viviani@rccr.cremona.it> (NeXTmail, MIME)
<mirko@yourbox.net>

From bouncefilter Fri Nov 19 08:45:30 1999
Received: from maria.ctv.es (maria.ctv.es [212.25.129.25])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA02574
for <pgsql-general@postgresql.org>;
Fri, 19 Nov 1999 08:45:14 -0500 (EST)
(envelope-from grupoitem@ctv.es)
Received: from ctv.es (ctv21225137018.ctv.es [212.25.137.18])
by maria.ctv.es (8.9.3/8.9.1) with ESMTP id OAA07684
for <pgsql-general@postgresql.org>;
Fri, 19 Nov 1999 14:44:33 +0100 (MET)
X-Envelope-To: <pgsql-general@postgresql.org>
Message-ID: <3835547E.A7EBC845@ctv.es>
Date: Fri, 19 Nov 1999 14:45:34 +0100
From: Jose Antonio Serra =?iso-8859-1?Q?P=E9rez?= <grupoitem@ctv.es>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

unsubscribe
end

From bouncefilter Fri Nov 19 08:49:31 1999
Received: from smtp1.jazzfree.com ([212.106.192.136])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA02815
for <pgsql-general@postgresql.org>;
Fri, 19 Nov 1999 08:48:51 -0500 (EST)
(envelope-from comscan@jazzfree.com)
Received: from jaserra (212.25.137.18) by smtp1.jazzfree.com (NPlex 4.0.054)
id 383452D700007750 for pgsql-general@postgresql.org;
Fri, 19 Nov 1999 14:45:22 +0100
Message-ID: <000501bf3294$dcf11940$03016464@jaserra>
From: =?iso-8859-1?Q?Pablo_Sentis_Casta=F1o?= <comscan@jazzfree.com>
To: <pgsql-general@postgresql.org>
Subject:
Date: Fri, 19 Nov 1999 14:49:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

subscribe
end

From bouncefilter Fri Nov 19 09:55:33 1999
Received: from oxmail.ox.ac.uk (oxmail2.ox.ac.uk [163.1.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA11804
for <pgsql-general@postgresql.org>;
Fri, 19 Nov 1999 09:54:59 -0500 (EST)
(envelope-from moray.mcconnachie@computing-services.oxford.ac.uk)
Received: from heraldgate1.oucs.ox.ac.uk
([163.1.2.49] helo=frontend1.herald.ox.ac.uk ident=exim)
by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 11opR9-0003vA-00
for pgsql-general@postgresql.org; Fri, 19 Nov 1999 14:54:55 +0000
Received: from moraypc.oucs.ox.ac.uk ([163.1.14.118] helo=moraypc)
by frontend1.herald.ox.ac.uk with smtp (Exim 2.02 #1)
id 11opR9-0000OQ-00
for pgsql-general@postgreSQL.org; Fri, 19 Nov 1999 14:54:55 +0000
Message-ID: <017101bf329e$099c4100$760e01a3@oucs.ox.ac.uk>
From: "Moray McConnachie" <moray.mcconnachie@computing-services.oxford.ac.uk>
To: "PostgreSQL-general" <pgsql-general@postgresql.org>
References: <199911181241.HAA22556@candle.pha.pa.us>
Subject: Rules & cycles
Date: Fri, 19 Nov 1999 14:54:53 -0000
Organization: Oxford University
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Is it possible to avoid a rule calling itself, as it were?

i.e.

CREATE TABLE test (testnumber float8,testid serial primary key);

CREATE FUNCTION adjust(float8) RETURNS '
SELECT dpow(1.14,$1) AS result;'
LANGUAGE 'SQL';

CREATE RULE testtest AS ON INSERT TO test
DO INSTEAD INSERT INTO test (testnumber) VALUES
(adjust(new.testnumber));

INSERT INTO test VALUES (2);

now gets into an endless loop, which postgres intelligently breaks out
of with an ERROR:

What I want is just to make that substitution once!

If possible I want to do this without rewriting my application to use
a view of the table rather than the table itself...

Yours,
Moray

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk
----- Original Message -----
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: PostgreSQL-announce <announce@postgreSQL.org>; PostgreSQL-general
<pgsql-general@postgreSQL.org>
Sent: Thursday, November 18, 1999 12:41 PM
Subject: [GENERAL] Book completed through chapter 6

I have completed through chapter 6 of my book, "PostgreSQL:
Introduction and Concepts." Of course, this is only the first

draft.

It can be viewed at:

http://www.postgresql.org/docs/awbook.html

There are major improvements in this version. I have added sections

chapter 4 dealing with DEFAULT and functions/operators. The figure
placement and font usage is improved.

Chapter 6 covers using multiple tables and joins. This was a very
difficult chapter for me to write.
--
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania

19026

************

From bouncefilter Sat Nov 20 02:06:13 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA44920
for <pgsql-general@postgreSQL.org>;
Sat, 20 Nov 1999 02:05:21 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (dial-132.ocis.net [209.52.175.104])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id XAA06611
for <pgsql-general@postgreSQL.org>; Fri, 19 Nov 1999 23:05:13 -0800
Message-ID: <3835666C.DE3E58EE@mail.ocis.net>
Date: Fri, 19 Nov 1999 23:02:04 +0800
From: Jason <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: PG for Win.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

Could somone point me to the Win32 version of P.G server please.

Thanks,

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

From bouncefilter Fri Nov 19 11:36:33 1999
Received: from srv.ctlno.com (srv.ctlno.com [204.252.218.112])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA28951;
Fri, 19 Nov 1999 11:35:46 -0500 (EST) (envelope-from matt@ctlno.com)
Received: by srv.ctlno.com with Internet Mail Service (5.0.1457.3)
id <XG858AY8>; Fri, 19 Nov 1999 11:24:46 -0600
Message-ID: <183FA749499ED311B6550000F87E206C07E1@srv.ctlno.com>
From: Matthew <matt@ctlno.com>
To: PostgreSQL-general <pgsql-general@postgresql.org>,
"'pgsql-admin@postgresql.org'" <pgsql-admin@postgresql.org>
Subject: data problem
Date: Fri, 19 Nov 1999 11:24:43 -0600
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain

I'm running postgresql 6.5.1 on Redhat 6.0. I am trying to move a
database to a new box running 6.5.3. So I tried a 'pg_dump db_name >
db_name.out' so that I could restore the database to the new server.
The pg_dump command failed with the following error:

pqWait() -- connection not open
PQendcopy: resetting connection
SQL query to dump the contents of Table 'taxbilldocs' did not execute
correctly.
After we read all the table contents from the backend, PQendcopy()
failed. Ex
planation from backend: 'pqWait() -- connection not open
'.
The query was: 'COPY "taxbilldocs" TO stdout;
'.

It always happens on the same table. I went into psql to see if I could
see anything wrong. if I do a 'select * from taxbilldocs where docid
like '111%';' or any other query taht returns a limited result set it
succedes. However if I do a 'select * from taxbilldocs' it fails with
the following error:

Backend message type 0x44 arrived while idle
Backend message type 0x44 arrived while idle
We have lost the connection to the backend, so further processing is
impossible.
Terminating.

I don't know what to do. Is there a tool out there for integrity
checking / fixing of pgsql data?

Any help would be greatly appreciated.

Thanks,

Matt O'Connor

From bouncefilter Fri Nov 19 16:30:36 1999
Received: from mocha.baileylink.net (mocha.baileylink.net [63.71.213.4])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA70118;
Fri, 19 Nov 1999 16:29:46 -0500 (EST)
(envelope-from banghe@baileylink.net)
Received: from baileylink.net (xindu.baileylink.net [63.71.216.27])
by mocha.baileylink.net (Netscape Mail Server v2.02) with ESMTP
id AAA12208; Fri, 19 Nov 1999 15:30:14 -0600
Message-ID: <3835C3DA.D620E65C@baileylink.net>
Date: Fri, 19 Nov 1999 15:40:42 -0600
From: banghe@baileylink.net (Xing Banghe)
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en,zh,zh-CN,zh-TW
MIME-Version: 1.0
To: Matthew <matt@ctlno.com>
CC: PostgreSQL-general <pgsql-general@postgreSQL.org>,
"'pgsql-admin@postgresql.org'" <pgsql-admin@postgreSQL.org>
Subject: Re: [ADMIN] data problem
References: <183FA749499ED311B6550000F87E206C07E1@srv.ctlno.com>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit

Here is a suggestion to identy your problem.

Create a very simple table with some reocrds on your old postgres, then
pgdump, and restory on your new postgres. See is there a problem? If no,
then
there must have some functions used in your old database which are different
from in the new version. If it is yes, then maybe the problem is postgres
user setting.

-- Banghe

Matthew wrote:

I'm running postgresql 6.5.1 on Redhat 6.0. I am trying to move a
database to a new box running 6.5.3. So I tried a 'pg_dump db_name >
db_name.out' so that I could restore the database to the new server.
The pg_dump command failed with the following error:

pqWait() -- connection not open
PQendcopy: resetting connection
SQL query to dump the contents of Table 'taxbilldocs' did not execute
correctly.
After we read all the table contents from the backend, PQendcopy()
failed. Ex
planation from backend: 'pqWait() -- connection not open
'.
The query was: 'COPY "taxbilldocs" TO stdout;
'.

It always happens on the same table. I went into psql to see if I could
see anything wrong. if I do a 'select * from taxbilldocs where docid
like '111%';' or any other query taht returns a limited result set it
succedes. However if I do a 'select * from taxbilldocs' it fails with
the following error:

Backend message type 0x44 arrived while idle
Backend message type 0x44 arrived while idle
We have lost the connection to the backend, so further processing is
impossible.
Terminating.

I don't know what to do. Is there a tool out there for integrity
checking / fixing of pgsql data?

Any help would be greatly appreciated.

Thanks,

Matt O'Connor

************

From bouncefilter Fri Nov 19 15:23:34 1999
Received: from Namesrv.Mountain.Net (root@Namesrv.Mountain.Net [198.77.1.1])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA62048
for <pgsql-general@hub.org>; Fri, 19 Nov 1999 15:23:15 -0500 (EST)
(envelope-from dckinder@mountain.net)
Received: from duncan (AM6-2.Wheeling-WV.Mountain.Net [198.77.41.102])
by Namesrv.Mountain.Net (8.9.3/8.9.0) with SMTP id PAA14783
for <pgsql-general@hub.org>; Fri, 19 Nov 1999 15:23:09 -0500 (EST)
Message-ID: <000701bf32e6$5d417120$02010101@duncan>
From: "Duncan Kinder" <dckinder@mountain.net>
To: "PostgreSQL General" <pgsql-general@hub.org>
Subject: postgresadmin difficulty
Date: Fri, 19 Nov 1999 15:32:32 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

I have just installed postgresadmin into a RedHat 6.0 box .

I get the following error when attempting to log on:

<error>
Warning: Unable to connect to PostgresSQL server: FATAL 1: Database
dbname=template1 does not exist in pg_database in lib.inc.php3 on line 125

Fatal error: Call to unsupported or undefined function pg_die() in
lib.inc.php3 on line 125
</error>

I would appreciate any feedback.
Regards,

Duncan C. Kinder
dckinder@mountain.net

From bouncefilter Sat Nov 20 08:32:17 1999
Received: from dolomite.mint.net (dolomite.mint.net [216.227.128.33])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA88603
for <pgsql-general@hub.org>; Sat, 20 Nov 1999 08:32:13 -0500 (EST)
(envelope-from bsneed@mint.net)
Received: from mint.net (ddialup-r-192.mint.net [216.227.145.212])
by dolomite.mint.net (8.9.3/8.9.3) with ESMTP id IAA27310
for <pgsql-general@hub.org>; Sat, 20 Nov 1999 08:32:01 -0500
Sender: root@dolomite.mint.net
Message-ID: <3836A2EF.AAE7CB46@mint.net>
Date: Sat, 20 Nov 1999 08:32:31 -0500
From: Bill Sneed <bsneed@mint.net>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@hub.org
Subject: Re:Trying to SELECT via web server using PHP
References: <199911200402.XAA20590@hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings,

I've got pgsql running fine from the command line, but I'm having =
problems using PHP to do a select...suggestions?

<html>
<body>
<?php
$conn =3D pg_Connect("host=3Dlocalhost port=3D5432 dbname=3Dcustomers");
$result =3D pg_exec($conn, 'select * from employees');
echo $result;
pg_exec ($database, "commit");
pg_exec ($database, "end");
?>
</body>
</html>

results in:
Warning: PostgresSQL query failed: ERROR: employees: Permission denied. =
in /home/httpd/html/connect2.php3 on line 6

Warning: 0 is not a PostgresSQL link index in =
/home/httpd/html/connect2.php3 on line 8

Warning: 0 is not a PostgresSQL link index in =
/home/httpd/html/connect2.php3 on line 9

If I change the host, the thing really blows a gasket.

There may be a couple of things wrong here:

(1) You've granted "nobody" read rights to the table(s)? Don't forget
that user "nobody" is default user of Apache -- and perhaps other
Web servers as well.

(2) My pg_connect statements are all of the form:
pg_connect("localhost","5432","","","library");
Some of the parameters can be omitted but I believe the quotes &
commas are needed.

(3) You are "echoing" your output into a table with a "while"? If not
all you'll get --at best-- is one entry.

Hope that helps .....

....Bill Sneed, Prospect, Maine....

From bouncefilter Sat Nov 20 09:26:18 1999
Received: from meryl.csd.uu.se (meryl.csd.uu.se [130.238.12.42])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA96037
for <pgsql-general@hub.org>; Sat, 20 Nov 1999 09:26:15 -0500 (EST)
(envelope-from e99re41@csd.uu.se)
Received: from berch.csd.uu.se (e99re41@berch.csd.uu.se [130.238.15.82])
by meryl.csd.uu.se (8.8.5/8.8.5) with SMTP id PAA25278;
Sat, 20 Nov 1999 15:26:04 +0100 (MET)
Date: Sat, 20 Nov 1999 15:26:03 +0100 (MET)
From: Peter Eisentraut <e99re41@csd.uu.se>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Bill Sneed <bsneed@mint.net>
cc: pgsql-general@hub.org
Subject: Re: [GENERAL] Re:Trying to SELECT via web server using PHP
In-Reply-To: <3836A2EF.AAE7CB46@mint.net>
Message-ID: <Pine.GSO.3.96.991120151716.5882A-100000@berch.csd.uu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 20 Nov 1999, Bill Sneed wrote:

(1) You've granted "nobody" read rights to the table(s)? Don't forget
that user "nobody" is default user of Apache -- and perhaps other
Web servers as well.

This is diverging a little bit, but since it comes up quite a lot, I'll
say it again: It is absolutely insane to grant user "nobody" any table
access rights! It is also a perhaps unfortunate circumstance that the
Apache project just silently sets the default user to user "nobody".

Reasoning: A number of system daemons and other programs use the user
"nobody" when they want to be extremely secure and want to make sure they
don't have access to anything. Granting that user access to anything is
therefore wrong.

If you need your webserver to do all kinds of things on your server,
invent a different username, such as "httpd", and run the webserver as
that. Before you know it, your "nobody" also owns files, directories, suid
programs, if you don't pay attention it might even have catalog update
privileges in PostgreSQL. Then some guy comes along and sends email to
kmem@yourdomain, the MDA wisely switches to nobody as a preventive
measure, and all hell breaks loose once the mail gets into your procmail
filters. Just an example.

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Sun Nov 21 01:35:29 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA95701
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 01:34:59 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (dial-185.ocis.net [209.52.174.136])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id WAA19443
for <pgsql-general@postgreSQL.org>; Sat, 20 Nov 1999 22:34:57 -0800
Message-ID: <3836B0DA.58903D09@mail.ocis.net>
Date: Sat, 20 Nov 1999 22:31:54 +0800
From: Jason <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: PostreSQL <pgsql-general@postgreSQL.org>
Subject: Temp table vs sub query.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Would you use a temporary table rather than a sub query if you needed to
perform multiple queries on the same (already retrieved) data? I am
sure you could use a sub query initially to fetch the data for the temp
table. I'm just curious under what circumstances you would use temp
tables. Would the disk cache not be good enough to depend on?

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

From bouncefilter Sun Nov 21 14:15:38 1999
Received: from crimecheck.DILIGENCE.COM ([206.252.234.193])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA73087
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 14:15:21 -0500 (EST)
(envelope-from tim@diligence.com)
Received: from tim.lantel.com ([206.252.242.28])
by crimecheck.DILIGENCE.COM (Post.Office MTA v3.5.3 release 223
ID# 0-56960U300L2S100V35) with SMTP id COM
for <pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 12:14:16 -0700
Message-Id: <3.0.1.32.19991120121645.008b0e70@mail.diligence.com>
X-Sender: tim@mail.diligence.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Sat, 20 Nov 1999 12:16:45 -0700
To: pgsql-general@postgreSQL.org
From: Tim Uckun <tim@diligence.com>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

On the other hand, I have been using MS-SQL 7 for several months now, for
another project, and am not at all happy with it -- it has crashed on me
several times (because of some flaky OCXs), even though I was only doing
database design and not doing production work, and I am frustrated by the
lack of user-defined functions that I have taken for granted in
PostgreSQL.

I think this is an excellant discussion that really needs to be posted in
the FAQ. I searches through the FAQ and the docs looking for a feature list
and or a comparison with other major databases and I saw verly little info.
Specifically there should be matrix of features with MS SQL7.0 Oracle,
Informix, Sybase, and Interbase. If at all possible benchmarks should be
posted or at least some phrasing stating which are faster at what features.
It would be very helpful for a potential Postgreas user to know what they
are getting into.

Maybe it's not fair to compare Postgres to Oracle especially given the
costs involved but it could be useful in a cost benefit analysis (sure
Oracle has feature X but Do I really need it and how much do I want to pay
for it).

Another thing that is needed is some sort of a front end tool like access
to generate forms, reports, tables etc. I know that a programmer could whip
something up using TK/GTK or java but I am thinking about an end user.

Finally: Until I can replace Access I need to have postgress to play nice
with my windows desktops so I need really good ODBC/ADO support.
----------------------------------------------
Tim Uckun
Mobile Intelligence Unit.
----------------------------------------------
"There are some who call me TIM?"
----------------------------------------------

From bouncefilter Sun Nov 21 19:48:42 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA43272
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 19:48:31 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (dial-226.ocis.net [209.52.174.177])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id QAA08899
for <pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 16:48:29 -0800
Message-ID: <3837B126.DF95D1F4@mail.ocis.net>
Date: Sun, 21 Nov 1999 16:45:26 +0800
From: Jason <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: PostreSQL <pgsql-general@postgreSQL.org>
Subject: Debian w/ DBI/DBD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I think I have DBI and DBD installed OK, and postgres seems to be
working OK. But, I can not access DBI from a perl script. I get a
DBI/Pg.pm not found, then asked if I have it installed. Is there some
magical trick to this under Debian 2.1, or have I missed a package along
the way.

Thanks,
Jason

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

From bouncefilter Sun Nov 21 07:14:33 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id HAA30466
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 07:14:01 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp21.kross.klever.net
[209.203.65.21]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id FAA05056 for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 05:11:41 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <3837E22B.45135127@ironmountainsystems.com>
Date: Sun, 21 Nov 1999 04:14:35 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

From bouncefilter Sun Nov 21 19:08:41 1999
Received: from smtp.access1.net (smtp.access1.net [206.13.101.40])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA36372
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 19:08:07 -0500 (EST)
(envelope-from ccthomas@access1.net)
Received: from bsdbox.SAMBA [205.253.113.14] by smtp.access1.net
(SMTPD32-5.01) id A919C1030192; Sun, 21 Nov 1999 16:06:49 PDT
Sender: root
Message-ID: <3837E260.2781E494@access1.net>
Date: Sun, 21 Nov 1999 07:15:28 -0500
From: Courtney Thomas <ccthomas@access1.net>
X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 2.2.5-RELEASE i386)
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: what JDBC/ODBC choices are there ?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings !

What seems to be the consensus concerning the best choices regarding
JDBC(s) and ODBC(s) ?

Thanks,

Courtney

From bouncefilter Sun Nov 21 07:46:33 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id HAA33216
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 07:46:14 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp21.kross.klever.net
[209.203.65.21]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id FAA06165 for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 05:43:53 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <3837E9B7.21B7C45C@ironmountainsystems.com>
Date: Sun, 21 Nov 1999 04:46:47 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Is PostgreSQL ready for mission critical applications?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Question: Is PostgreSQL ready for mission critical applications?
----------------------------------------------------

This has to be a FAQ, but I cannot seem to get a good answer.

I have just returned from a very interesting Comdex where I spend a few
hours in the Linux area asking for opinions on this issue.

Most people were unsure and suggested that MySQL has a great reputation
for stability and may be a better choice. Since I want transaction
support, MySQL is not an option for me. In fact, I really wanted the
DBMS to support referential integrity as well, PostgreSQL doesn't :-(

Several people reminded me that MySQL is faster than PostgreSQL.
However, performance is far less important to me than the basic
question of stability. The database must be stable enough to run
almost 24x7 and must never suffer from data corruption or from
mysterious crashes.

Is anyone out there actually using PostgreSQL for a mission critical
application?

Is PostgreSQL ready for prime time?

Help!

PS Many thanks to the MySQL advocate at the KDE stand who provided a
compelling argument that my
particular application did not need transactions. Further thought
convinced me that they are a requirement.
Sorry I didn't get your name - yours was an insightful discussion.

Also, thanks to Michele Webster at the Applix booth for a lively
discussion regarding this issue and for the suggestion that I post the
question at the PostgreSQL site.

From bouncefilter Sun Nov 21 09:59:35 1999
Received: from mercury.shreve.net (IDENT:root@mercury.shreve.net
[208.206.76.23]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA44658
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 09:59:24 -0500 (EST)
(envelope-from kheflin@shreve.net)
Received: from mercury.shreve.net (IDENT:kheflin@mercury.shreve.net
[208.206.76.23])
by mercury.shreve.net (8.9.3/8.9.3) with ESMTP id IAA07943;
Sun, 21 Nov 1999 08:58:57 -0600
Date: Sun, 21 Nov 1999 08:58:57 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
To: Stephen Birch <sbirch@ironmountainsystems.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Is PostgreSQL ready for mission critical applications?
In-Reply-To: <3837E9B7.21B7C45C@ironmountainsystems.com>
Message-ID: <Pine.LNX.4.10.9911210850530.5678-100000@mercury.shreve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 21 Nov 1999, Stephen Birch wrote:

Several people reminded me that MySQL is faster than PostgreSQL.
However, performance is far less important to me than the basic
question of stability. The database must be stable enough to run
almost 24x7 and must never suffer from data corruption or from
mysterious crashes.

Is anyone out there actually using PostgreSQL for a mission critical
application?

Is PostgreSQL ready for prime time?

We've using Postgresql for nothing but mission critical work. Never have
any problems with it. Don't have any complaints about the speed. We were
running 6.3.2 for a long time, and recently upgraded to 6.5.x
Supposedly the newer version has some speed benefits, but again, we've
never had any problems with speed to begin with.

We chose postgresql over mysql about 3 years ago, due to the more complete
sql support. Other than that, I just liked it better.

Postgresql handles the authentication for our dial-up users.. we have over
6000 users dialing into our network.

The same server also handles request for some dynamic web pages which
request information from postgresql.. sometimes with over a million hits
per hour.

All in all we've got about 100 different DBs on the server. All mission
critical as far as I'm concerned, some more than others obviously.

I've also received some great and timely help through the postgresql
mailing lists.

Good luck

Kevin

--------------------------------------------------------------------
Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
VP/Production | 333 Texas St #175 | FAX:318.221.6612
kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
--------------------------------------------------------------------

From bouncefilter Sun Nov 21 13:01:37 1999
Received: from binky.de.uu.net (binky.de.uu.net [192.76.144.28])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA64824
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 13:01:15 -0500 (EST)
(envelope-from CHUETTL@ahorn.sgh.uunet.de)
Received: from huettl (pec-18-23.tnt2.b.uunet.de [149.225.18.23])
by binky.de.uu.net (5.5.5/5.5.5) with ESMTP id TAA03487
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 19:00:44 +0100 (MET)
Received: from Spooler by huettl (Mercury/32 v2.16); 21 Nov 99 19:01:19 +0100
Received: from spooler by ahorn.sgh.uunet.de (Mercury/32 v2.16);
21 Nov 99 17:14:50 +0100
From: "Carsten Huettl" <CHUETTL@ahorn.sgh.uunet.de>
Organization: ahorn.Net
To: pgsql-general@postgresql.org, pgsql-novice@postgresql.org
Date: Sun, 21 Nov 1999 17:13:51 +0200
Subject: insert data via odbc
Priority: normal
X-mailer: Pegasus Mail for Win32 (v3.12a)
Message-ID: <94A0386D2C70@ahorn.sgh.uunet.de>

Hello,

I created a db with ms access and bound 2 tables from an psql db.
Now I want to insert data from the access db but there is no option
to insert data in the mask I create.
Isn't it posible to insert data via the current odbc driver or what am I
doing wrong?

tia
C.

--
Carsten Huettl - <http://www.ahorn-Net.de>
pgp-key on request

From bouncefilter Sun Nov 21 11:04:36 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA50484
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 11:03:38 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11pZSi-0007Pj-00; Sun, 21 Nov 1999 17:03:36 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11pZSP-0004dX-00
for pgsql-general@postgresql.org; Sun, 21 Nov 1999 17:03:17 +0100
Date: Sun, 21 Nov 1999 17:03:16 +0100
From: Jochen Topf <jochen@remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
Message-ID: <19991121170316.A17799@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?
[...]

I can *not* recommend using PostgreSQL for a mission critical application. I
have used PostgreSQL for a reasonably sized project, where it is used as
the central database for an ISP for administration of all users, accounts,
hosts, ip numbers, accounting, etc. The decision for PostgreSQL was based
on cost and features. Like you, I needed transactions and other goodies
like triggers and notifications, that no other freely available database
can provide.

I was very pleased with PostgreSQL in the beginning, but that changed after
a while. PostgreSQL is not really stable, in fact it is very easy to crash
the backend process that is handling the connection to your client and quite
often the other backends shut down, too. I have seen many random errors, for
instance sometimes loading a new stored procedure will crash the database,
while it works the next time. Sometimes databases grow over every bound
making the system slower and slower, the vaccum process needs hours to do
its work and nothing except a dump and rebuild of the database helps.

The most frustrating thing is that most bugs are not repeatable or at least
not repeatable in a small test script that I could send in with a bug report.
Looking at the bug reports that come through the mailing list, there are a
lots of the type: X works here but not in this similar situation. This is
IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5
to 6.5.1 or something like that) helped a little bit but on the other hand
some query optimizations that worked before didn't work anymore.

So all this leads to my conclusion: The system is not ready for prime time.
If you only use some basic functionality it might be ok, but if you (like
me) use everything from transactions to triggers, notification, user defined
types, stored procedurs and rules, you will probabely not be happy with it.

There is a very active developer community and I still have hope that
PostgreSQL will make it at some point (otherwise I wouldn't be following the
mailing list).

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Sun Nov 21 11:23:36 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA52139
for <pgsql-general@postgresql.org>;
Sun, 21 Nov 1999 11:23:27 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11pZlu-0007TH-00; Sun, 21 Nov 1999 17:23:26 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11pZlg-0004fZ-00
for pgsql-general@postgreSQL.org; Sun, 21 Nov 1999 17:23:12 +0100
Date: Sun, 21 Nov 1999 17:23:12 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
Message-ID: <19991121172312.A17948@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?
[...]

There is a very active developer community and I still have hope that
PostgreSQL will make it at some point (otherwise I wouldn't be following the
mailing list).

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Sun Nov 21 12:03:37 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA55985
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 12:03:17 -0500 (EST)
(envelope-from alessio@albourne.com)
Received: from albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with ESMTP
id TAA05210; Sun, 21 Nov 1999 19:06:57 +0200 (EET)
Sender: alessio@albourne.com
Message-ID: <383825C9.F12223D4@albourne.com>
Date: Sun, 21 Nov 1999 19:03:05 +0200
From: Alessio Bragadini <alessio@albourne.com>
Organization: APL Financial Services (Overseas) Ltd.
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: it, en, sv
MIME-Version: 1.0
To: Stephen Birch <sbirch@ironmountainsystems.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Is PostgreSQL ready for mission critical applications?
References: <3837E9B7.21B7C45C@ironmountainsystems.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephen Birch wrote:

Question: Is PostgreSQL ready for mission critical applications?

Several people reminded me that MySQL is faster than PostgreSQL.

On this issue I simply stick with the defition I received at University:
a DBMS (DataBase Management System) does transactions. Period. MySQL is
not a DBMS, then, but something like DBM.

--
Alessio F. Bragadini alessio@albourne.com
APL Financial Services http://www.sevenseas.org/~alessio
Nicosia, Cyprus phone: +357-2-750652

You are welcome, sir, to Cyprus. -- Shakespeare's "Othello"

From bouncefilter Sun Nov 21 12:04:37 1999
Received: from access1.lan2wan.com (root@access1.lan2wan.com [205.177.8.10])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA56045
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 12:03:57 -0500 (EST)
(envelope-from bmccoy@lan2wan.com)
Received: from dragosani.lan2wan.com (pm1-27.lan2wan.com [205.177.8.67]) by
access1.lan2wan.com (8.9.1/8.9.1) with ESMTP id MAA24628 for
<pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 12:12:08 -0500 (EST)
Received: from localhost (bmccoy@localhost)
by dragosani.lan2wan.com (8.8.7/8.8.7) with ESMTP id MAA18444
for <pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 12:04:01 -0500
X-Authentication-Warning: dragosani.lan2wan.com: bmccoy owned process doing
-bs
Date: Sun, 21 Nov 1999 12:04:01 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
To: pgsql-general@postgreSQL.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
In-Reply-To: <19991121172312.A17948@eldorado.remote.org>
Message-ID: <Pine.LNX.4.04.9911211146330.18253-100000@dragosani.lan2wan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?

I think it is. In my office, we are converting hundreds of thousands of
digitized documents (each of which is comprised of multiple TIFF images)
into PDF documents. This has been going on since April or so. We are
using Postgres 6.4 under Linux (PPro 200 w/128 megs of RAM), with the
original images stored on Novell servers. This is almost a 24x7 process,
as we are constantly running conversion batches and going through QC
processes before the images are backed up and put into offline storage. We
are using Perl for the application front end (as CGI), and Image Alchemy
for the conversion, and Postgres for the batch maintenance. This system
absolutely required transaction support, especially in the QC process.
On top of this, we are using the same server to run a simple search engine
based around Postgres to retrieve adverse drug reaction reports -- this
database has several million rows across several tables, using a PHP3
frontend. Here, though, speed is not the consideration but reliable
performance is. PostgreSQL has been very stable and I have no reason to
question its reliability. We are going to be moving our drug reaction
database over onto its own server soon and providing public (although
secure) access in the near future -- it will be using a mod_perl frontend,
along with the the PostgreSQL fulltext module.

So I think PostgreSQL is quite solid and reliable. The only thing I think
that is sorely needed in PostgreSQL is referential integrity constraints
like foreign keys (although this can be emulated with triggers).

On the other hand, I have been using MS-SQL 7 for several months now, for
another project, and am not at all happy with it -- it has crashed on me
several times (because of some flaky OCXs), even though I was only doing
database design and not doing production work, and I am frustrated by the
lack of user-defined functions that I have taken for granted in
PostgreSQL.

Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
"Gotcha, you snot-necked weenies!"
-- Post Bros. Comics

From bouncefilter Sun Nov 21 13:56:38 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id NAA70364
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 13:55:50 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 25885 invoked by uid 417); 21 Nov 1999 19:24:45 -0000
Received: from p3404.nl.wish.net (HELO galaxy.galnet) (212.123.151.76)
by smtp.softhome.net with SMTP; 21 Nov 1999 19:24:45 -0000
Message-Id: <4.1.19991121194641.0091b100@pop.softhome.net>
X-Sender: j.roeleveld@pop.softhome.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sun, 21 Nov 1999 19:48:02 +0100
To: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
From: "J. Roeleveld" <j.roeleveld@softhome.net>
Subject: Re: [GENERAL] insert data via odbc
In-Reply-To: <94A0386D2C70@ahorn.sgh.uunet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 16:13 Sunday 21-11-99 , Carsten Huettl wrote:

Hello,

I created a db with ms access and bound 2 tables from an psql db.
Now I want to insert data from the access db but there is no option
to insert data in the mask I create.
Isn't it posible to insert data via the current odbc driver or what am I
doing wrong?

Have you unselected the 'read-only' options in the ODBC-driver?
this is standard set to Read-Only.

Joost

From bouncefilter Sun Nov 21 14:50:39 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id OAA77283
for pgsql-general@postgresql.org; Sun, 21 Nov 1999 14:50:05 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "news" <oscar@enschede.frowijn.nl>
X-Newsgroups: comp.databases.postgresql.questions
Subject: Btrieve and Postgres
Date: Sun, 21 Nov 1999 20:51:08 +0100
Organization: SURFnet BV
Lines: 8
Message-ID: <819ics$j6d$1@news.surfnet.nl>
X-Trace: news.surfnet.nl 943213788 19661 192.87.16.130 (21 Nov 1999 19:49:48
GMT)
X-Complaints-To: usenet@news.surfnet.nl
X-Newsreader: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
To: pgsql-questions@postgresql.org

Hi,

Is there a possibility to export Btrieve DB files into postgres ??

Thanks in advance !
Oscar

From bouncefilter Sun Nov 21 15:29:39 1999
Received: from mc1.mcnet.ch (mail.mcnet.ch [193.5.163.9])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA81084
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 15:29:19 -0500 (EST)
(envelope-from webmaster@expansite.com)
Received: from 193.5.163.9 (fr-dial-28.mcnet.ch [195.130.185.28])
by mc1.mcnet.ch (8.9.3/8.9.3) with SMTP id VAA49768
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 21:29:18 +0100 (CET)
Message-Id: <199911212029.VAA49768@mc1.mcnet.ch>
To: pgsql-general@postgreSQL.org
Subject:
From: Bart Zylowski <webmaster@expansite.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Date: Sun, 21 Nov 1999 21:32:24 +0100
X-Mailer: Musashi 3.1-fr

unsubscribe

From bouncefilter Sun Nov 21 16:36:40 1999
Received: from mail1.panix.com (mail1.panix.com [166.84.0.212])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA91476
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 16:35:47 -0500 (EST)
(envelope-from tomg@mailhost.nrnet.org)
Received: from mailhost.nrnet.org (mailhost.nrnet.org [166.84.192.39])
by mail1.panix.com (Postfix) with ESMTP id 88CCB30F5A
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 16:35:44 -0500 (EST)
Received: from localhost (tomg@localhost)
by mailhost.nrnet.org (8.8.7/8.8.4) with SMTP
id QAA15421 for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 16:37:10 -0500
Date: Sun, 21 Nov 1999 16:37:10 -0500 (EST)
From: Thomas Good <tomg@mailhost.nrnet.org>
To: "PostgreSQL::General List" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <19991121172312.A17948@eldorado.remote.org>
Message-ID: <Pine.LNX.3.96.991121162830.15406A-100000@mailhost.nrnet.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 21 Nov 1999, Jochen Topf wrote:

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?
[...]

I was very pleased with PostgreSQL in the beginning, but that changed after
a while. PostgreSQL is not really stable, in fact it is very easy to crash
the backend process that is handling the connection to your client and quite
often the other backends shut down, too. I have seen many random errors, for
instance sometimes loading a new stored procedure will crash the database,
while it works the next time. Sometimes databases grow over every bound
making the system slower and slower, the vaccum process needs hours to do
its work and nothing except a dump and rebuild of the database helps.

Odd...I have a large group of users who *hammer* on my postgres database
daily. I have twelve years worth of records in one local database...
despite all sorts of errors made by users (and electricians) we have
been fortunate, corruption wise.

We switched over from FoxPro about a year ago. Dropped PROGRESS soon
after. All of our character mode and web interface apps were ported
over and the performance is better than what we had previously. I also
tested Oracle, Sybase and Informix and opted for Postgres.

I haven't had cause to regret it. Occasionally (when I hastily write
sloppy queries that contain ORDER BY clauses) I have to clean up some
stale pg_sort files but aside from this (my error) postgres runs well.
I not only can recommend it for mission critical apps, I generally do
even if the affirmation is unsolicited. ;-)

------- North Richmond Community Mental Health Center -------

Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056

/* Member: Computer Professionals For Social Responsibility */

From bouncefilter Sun Nov 21 17:19:40 1999
Received: from access1.lan2wan.com (root@access1.lan2wan.com [205.177.8.10])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA95632
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 17:19:29 -0500 (EST)
(envelope-from bmccoy@lan2wan.com)
Received: from dragosani.lan2wan.com (pm1-11.lan2wan.com [205.177.8.51]) by
access1.lan2wan.com (8.9.1/8.9.1) with ESMTP id RAA01611 for
<pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 17:27:48 -0500 (EST)
Received: from localhost (bmccoy@localhost)
by dragosani.lan2wan.com (8.8.7/8.8.7) with ESMTP id RAA19138
for <pgsql-general@postgreSQL.org>; Sun, 21 Nov 1999 17:19:40 -0500
X-Authentication-Warning: dragosani.lan2wan.com: bmccoy owned process doing
-bs
Date: Sun, 21 Nov 1999 17:19:00 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
To: Tim Uckun <tim@diligence.com>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <3.0.1.32.19991120120953.008c6e60@mail.diligence.com>
Message-ID: <Pine.LNX.4.04.9911211716090.19078-100000@dragosani.lan2wan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
ReSent-Date: Sun, 21 Nov 1999 17:19:29 -0500 (EST)
ReSent-From: "Brett W. McCoy" <bmccoy@lan2wan.com>
ReSent-To: pgsql-general@postgreSQL.org
ReSent-Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
ReSent-Message-ID: <Pine.LNX.4.04.9911211719290.19078@dragosani.lan2wan.com>

I think this is an excellant discussion that really needs to be posted in
the FAQ. I searches through the FAQ and the docs looking for a feature list
and or a comparison with other major databases and I saw verly little info.
Specifically there should be matrix of features with MS SQL7.0 Oracle,
Informix, Sybase, and Interbase. If at all possible benchmarks should be
posted or at least some phrasing stating which are faster at what features.
It would be very helpful for a potential Postgreas user to know what they
are getting into.

There is something like that on the PostgreSQL website, although it needs
updating. Also, MS-SQL is not included, nor is MySQL.

Another thing that is needed is some sort of a front end tool like access
to generate forms, reports, tables etc. I know that a programmer could whip
something up using TK/GTK or java but I am thinking about an end user.

Actually, there is a tool now distributed with PostgreSQL called pgAccess
which is similar in spirit to MS-Access, although it still needs some
work. There's also a nice utility called PgAdmin, a Windows applicaiton
that uses ODBC and is similar in functionality to SQl 7's Enterprise
Manager. I agree, though, that PostgreSQL needs some good front-end
tools now to rival SQL 7.

Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
Economics is extremely useful as a form of employment for economists.
-- John Kenneth Galbraith

From bouncefilter Sun Nov 21 18:52:41 1999
Received: from mx20.rmci.net (halcyon.rmci.net [205.162.184.63])
by hub.org (8.9.3/8.9.3) with SMTP id SAA34449
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 18:52:08 -0500 (EST)
(envelope-from webweaver@rmci.net)
Received: (qmail 25730 invoked from network); 21 Nov 1999 23:52:03 -0000
Received: from customer-208-14-165-67.rmci.net (HELO chilly-willy)
(208.14.165.67)
by halcyon.rmci.net with SMTP; 21 Nov 1999 23:52:03 -0000
Message-Id: <3.0.6.32.19991121165406.00836100@rmci.net>
X-Sender: webweaver@rmci.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sun, 21 Nov 1999 16:54:06 -0700
To: "Brett W. McCoy" <bmccoy@lan2wan.com>, pgsql-general@postgreSQL.org
From: Ken Gunderson <webweaver@rmci.net>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <Pine.LNX.4.04.9911211146330.18253-100000@dragosani.lan2wan .com>
References: <19991121172312.A17948@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:04 PM 11/21/99 -0500, Brett W. McCoy wrote:

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?

I think it is. In my office, we are converting hundreds of thousands of

<snip>

database has several million rows across several tables, using a PHP3
frontend. Here, though, speed is not the consideration but reliable
performance is. PostgreSQL has been very stable and I have no reason to
question its reliability. We are going to be moving our drug reaction
database over onto its own server soon and providing public (although
secure) access in the near future -- it will be using a mod_perl frontend,
along with the the PostgreSQL fulltext module.

<snip>

I am curious as to why you are choosing to use mod_perl instead of php3,
especially since you've already been using php3?? And especially with
php4/zend just around the corner. Not trying to start a flame war here, I
just really want to know.

Ciao-- Ken
http://www.y2know.org/safari

Failure is not an option- it comes bundled with your Microsoft product.

From bouncefilter Sun Nov 21 20:55:56 1999
Received: from solaris1.mysolution.com (adachi.mysolution.com [216.37.18.104])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA50711
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 20:55:35 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id UAA18730;
Sun, 21 Nov 1999 20:45:43 -0500 (EST)
Message-ID: <002d01bf348d$5bbfe900$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: "Jochen Topf" <pgsql-general@mail.remote.org>,
<pgsql-general@postgreSQL.org>
References: <19991121172312.A17948@eldorado.remote.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Date: Sun, 21 Nov 1999 21:00:01 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

I second this. I am sure you will not be able to get a good idea of the
database for some people have no problems with it and some do. My main
concern for the database used in a mission critical application is that
1) It requires a VERY skilled DBA in both Unix and PostgreSQL
2) There are few tools that make for ease of development and
administration.
3) Documentation is no where near as detailed or all encompassing as a
database like Oracle.
4) There are certain instances when the database requires a rebuild from
scratch or tape that are not related to hardware failure or disk corruption.
.5) There are no transaction logs or redo logs that allow you to recover
the database to a point in time or handle hot online backups.
6) It does not scale up to multi processor/multi threading very well (As I
understand it).
7) A vacuum has to be run often (at a regular interval) taking up valuable
system resources...locking tables and sometimes just failing utterly.

Although I will say I have been very happy with it as far as what I use it
for which is web site/e-commerce development. Usually mirroring or
distributed off of another internal coporate server :)

----- Original Message -----
From: Jochen Topf <pgsql-general@mail.remote.org>
To: <pgsql-general@postgreSQL.org>
Sent: Sunday, November 21, 1999 11:23 AM
Subject: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?
[...]

I can *not* recommend using PostgreSQL for a mission critical application.

have used PostgreSQL for a reasonably sized project, where it is used as
the central database for an ISP for administration of all users, accounts,
hosts, ip numbers, accounting, etc. The decision for PostgreSQL was based
on cost and features. Like you, I needed transactions and other goodies
like triggers and notifications, that no other freely available database
can provide.

I was very pleased with PostgreSQL in the beginning, but that changed

after

a while. PostgreSQL is not really stable, in fact it is very easy to crash
the backend process that is handling the connection to your client and

quite

often the other backends shut down, too. I have seen many random errors,

for

instance sometimes loading a new stored procedure will crash the database,
while it works the next time. Sometimes databases grow over every bound
making the system slower and slower, the vaccum process needs hours to do
its work and nothing except a dump and rebuild of the database helps.

The most frustrating thing is that most bugs are not repeatable or at

least

not repeatable in a small test script that I could send in with a bug

report.

Looking at the bug reports that come through the mailing list, there are a
lots of the type: X works here but not in this similar situation. This is
IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5
to 6.5.1 or something like that) helped a little bit but on the other hand
some query optimizations that worked before didn't work anymore.

So all this leads to my conclusion: The system is not ready for prime

time.

If you only use some basic functionality it might be ok, but if you (like
me) use everything from transactions to triggers, notification, user

defined

types, stored procedurs and rules, you will probabely not be happy with

it.

There is a very active developer community and I still have hope that
PostgreSQL will make it at some point (otherwise I wouldn't be following

the

mailing list).

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

************

From bouncefilter Sun Nov 21 21:29:43 1999
Received: from access1.lan2wan.com (root@access1.lan2wan.com [205.177.8.10])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA54939
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 21:28:44 -0500 (EST)
(envelope-from bmccoy@lan2wan.com)
Received: from dragosani.lan2wan.com (pm1-8.lan2wan.com [205.177.8.48]) by
access1.lan2wan.com (8.9.1/8.9.1) with ESMTP id VAA07753;
Sun, 21 Nov 1999 21:37:10 -0500 (EST)
Received: from localhost (bmccoy@localhost)
by dragosani.lan2wan.com (8.8.7/8.8.7) with ESMTP id VAA19754;
Sun, 21 Nov 1999 21:29:01 -0500
X-Authentication-Warning: dragosani.lan2wan.com: bmccoy owned process doing
-bs
Date: Sun, 21 Nov 1999 21:29:01 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
To: Ken Gunderson <webweaver@rmci.net>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <3.0.6.32.19991121165406.00836100@rmci.net>
Message-ID: <Pine.LNX.4.04.9911212125190.19078-100000@dragosani.lan2wan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 21 Nov 1999, Ken Gunderson wrote:

I am curious as to why you are choosing to use mod_perl instead of php3,
especially since you've already been using php3?? And especially with
php4/zend just around the corner. Not trying to start a flame war here, I
just really want to know.

Because I am using several Perl modules that aren't available in PHP3
(some of which are ones I've written). Don't get me wrong, I like PHP3
(especially because it uses the perl regular expression engine), but there
are some things in Perl I want to use, and I am more familiar with Perl as
well.

Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
Your worship is your furnaces
which, like old idols, lost obscenes,
have molten bowels; your vision is
machines for making more machines.
-- Gordon Bottomley, 1874

From bouncefilter Sun Nov 21 23:56:45 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA78210
for <pgsql-general@postgreSQL.org>;
Sun, 21 Nov 1999 23:55:58 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA44268;
Mon, 22 Nov 1999 00:55:58 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 00:55:58 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Jochen Topf <pgsql-general@mail.remote.org>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <19991121172312.A17948@eldorado.remote.org>
Message-ID: <Pine.BSF.4.10.9911220051150.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 21 Nov 1999, Jochen Topf wrote:

Stephen Birch <sbirch@ironmountainsystems.com> writes:
Question: Is PostgreSQL ready for mission critical applications?
[...]

I can *not* recommend using PostgreSQL for a mission critical application. I
have used PostgreSQL for a reasonably sized project, where it is used as
the central database for an ISP for administration of all users, accounts,
hosts, ip numbers, accounting, etc. The decision for PostgreSQL was based
on cost and features. Like you, I needed transactions and other goodies
like triggers and notifications, that no other freely available database
can provide.

Odd, I've been using PostgreSQL since v1.x for exactly this same reason,
and we haven't had any problems with the database crashing since v6.x was
released. Then again, the radius server opens/closes its connections as
required, instead of relynig on one persistent connection, so maybe that
helps, but that's just "application programming" vs backend...

Also, PostgreSQL is the *key* element to the virtual email system that I
built around Cyrus IMAPd several months back...if PostgreSQL was "flakey",
I'd have users losing email left, right and center...basically, *all* mail
delivery, and user authentication, relies on PostgreSQL being up 24/7
*period*...and I consider that one to be even more mission critical then
the accounting system above.

I'm stuck at something like 6.4 for the accounting app, and 6.5.0 right
now for the virtual email system, so I'm not even running the more up to
date 6.5.3 yet...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 22 00:10:45 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA80687
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 00:10:28 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA44502;
Mon, 22 Nov 1999 01:10:27 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 01:10:27 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Kane Tao <khtao@yahoo.com>
cc: Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <002d01bf348d$5bbfe900$040101c0@p2400arcane>
Message-ID: <Pine.BSF.4.10.9911220057160.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 21 Nov 1999, Kane Tao wrote:

I second this. I am sure you will not be able to get a good idea of the
database for some people have no problems with it and some do. My main
concern for the database used in a mission critical application is that
1) It requires a VERY skilled DBA in both Unix and PostgreSQL

why? compared to what I've seen of Oracle, PostgreSQL is pretty
brain-dead to operate...

2) There are few tools that make for ease of development and
administration.

can't really comment here as I do everything in perl *shrug*

3) Documentation is no where near as detailed or all encompassing as a
database like Oracle.

again, can't comment here as I've always found what I was looking
for...specific examples?

4) There are certain instances when the database requires a rebuild from
scratch or tape that are not related to hardware failure or disk
corruption.

version of PostgreSQL?

my email system database was created on July 9th of this year, and
I've never had to reload it from tape or otherwise, and its used by
sendmail 24/7 for email delivery. (v6.5.0)

my account system database was created on March 3th of this year,
and has been running without a reboot/restart since June 7th, which was
the last reboot of that machine...never reloaded that system either, and
its an older 6.4.0 system.

5) There are no transaction logs or redo logs that allow you to recover
the database to a point in time or handle hot online backups.

being worked on...but you are right, not currently available.

6) It does not scale up to multi processor/multi threading very well (As I
understand it).

actually, postgresql would run better on a multi-cpu FreeBSD
machine then MySQL would, to be honest. FreeBSD's SMP doesn't have the
ability to 'change cpu on a thread-by-thread basis', so the fact that
MySQL uses threads would actually be a drawback vs advantage (all threads
of the started processes would be stuck on the same CPU, even if the other
CPU was idle)...PostgreSQL, each forked instance would go to the more idle
CPU, since its a new process...

7) A vacuum has to be run often (at a regular interval) taking up
valuable system resources...locking tables and sometimes just
failing utterly.

why does it have to be run often? it depends on you
application/database. if you are changing your database around *alot*
(alot of update/deletes), yes, since you have to force it to do its own
garbage collection...the next release will remove the table locking
required, since Vadim's MVCC implementation removes the requirement for it
to do so. I do not beleive that this is something that is in v6.5.3, but
believe its already in there for v7...don't quote me on that, I've been
wrong before...

essentially, one of the ideas that's been toyed with (but I'm not
sure if anyone has worked on) is the concept of getting rid of the
requiremetn for a vacuum altogether. with the new MVCC code, the concept
of a table lock has essentially been removed, so a 'vacuum' *could* be
done periodically by the system itself...sort of like the auto-disk
defragmentation code that is in alot of the Unix file systems ...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 22 02:05:56 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id CAA93280
for pgsql-general@postgresql.org; Mon, 22 Nov 1999 02:05:13 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "Oscar Frowijn" <frowijn@itc.nl>
X-Newsgroups: comp.databases.postgresql.general
Subject: Import functions ?
Date: Mon, 22 Nov 1999 08:06:06 +0100
Organization: SURFnet BV
Lines: 12
Message-ID: <81apuu$1fa$1@news.surfnet.nl>
X-Trace: news.surfnet.nl 943254302 1514 192.87.16.130 (22 Nov 1999 07:05:02
GMT)
X-Complaints-To: usenet@news.surfnet.nl
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
To: pgsql-general@postgresql.org

Hi,

Is there a way to import Btrieve DB files right into Postgres ??

Or does someone know how to dump a Btrieve DB to flast ascii so that I can
import it into postgres ?

Thanks in advance !

Oscar

From bouncefilter Mon Nov 22 03:21:47 1999
Received: from kiln.isn.net (root@kiln.isn.net [198.167.161.1])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA04986
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 03:21:01 -0500 (EST)
(envelope-from ctassell@isn.net)
Received: from niki (ryan01.isn.net [198.167.161.71])
by kiln.isn.net (8.9.3/8.9.3) with ESMTP id EAA14294;
Mon, 22 Nov 1999 04:22:40 -0400
Message-Id: <4.2.0.58.19991122040848.009ab6c0@mailer.isn.net>
X-Sender: ctassell@mailer.isn.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Mon, 22 Nov 1999 04:12:51 -0400
To: Jason <jcl@mail.ocis.net>, PostreSQL <pgsql-general@postgreSQL.org>
From: Charles Tassell <ctassell@isn.net>
Subject: Re: [GENERAL] Debian w/ DBI/DBD
In-Reply-To: <3837B126.DF95D1F4@mail.ocis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

If you installed Postgres from source instead of getting a prebuilt
package, you probably have to, as root, go into your src/interfaces/perl5
dir and type "make install" This is because the perl include dirs are
usually only writable by root, so when you do a "make install" as the
postgres user, the Pg module can't be installed.

If you installed a package, I dunno. Try getting the source and doing a
"./configure --with-perl; cd interfaces/perl5; make install" as root.

At 04:45 AM 11/21/99, Jason wrote:

hi,

I think I have DBI and DBD installed OK, and postgres seems to be
working OK. But, I can not access DBI from a perl script. I get a
DBI/Pg.pm not found, then asked if I have it installed. Is there some
magical trick to this under Debian 2.1, or have I missed a package along
the way.

Thanks,
Jason

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

************

From bouncefilter Tue Nov 23 00:09:01 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA39690
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 00:08:24 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (dial-232.ocis.net [209.52.174.66])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id VAA14020
for <pgsql-general@postgreSQL.org>; Mon, 22 Nov 1999 21:08:22 -0800
Message-ID: <38390AFB.D781F984@mail.ocis.net>
Date: Mon, 22 Nov 1999 17:20:59 +0800
From: Jason <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: PostreSQL <pgsql-general@postgreSQL.org>
Subject: Flexability.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

With respect to the thread about is Pg ready for prime time. It
obviously is. All of the DBs have there place. We at work started with
Access, and now need to move to SQL Server (postgres if I can convince
them); just because the company needs a quick fix and will have no DBA
once I'm done. Maybe in a year or two they will go for Sybase or
Oracle. Who knows. Anyway, my real point was, Oracle is the most
flexible DB out there. But that flexibility is expensive and a little
too much for a small to mid sized company. Even for a large company
that does not deal in 'information' it's not worth it. But when
information becomes a commodity, you absolutely need the power of a
robust database, and need DBAs to run it. Then the cost of the DB and
the people are well worth it. If you don't need Oracle there is no need
to spend the money for it, + the salary for an Oracle DBA. And here is
where Pg fits in.

Postgres is definitely lacking in the doc department. My only comment
to that is, perhaps some of you who have been using it for ages and ages
should get together and write an intermediate book to complement the
book that is on the way. Maybe sell it to O'Reilly.

Anyway. Pg is an fantastic db in my opinion.

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

From bouncefilter Mon Nov 22 04:56:48 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA14399
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 04:56:13 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11pqCi-0000ze-00; Mon, 22 Nov 1999 10:56:12 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11pqBW-00055G-00
for pgsql-general@postgreSQL.org; Mon, 22 Nov 1999 10:54:58 +0100
Date: Mon, 22 Nov 1999 10:54:57 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
Message-ID: <19991122105457.A19519@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

The Hermit Hacker <scrappy@hub.org> wrote:
: Odd, I've been using PostgreSQL since v1.x for exactly this same reason,
: and we haven't had any problems with the database crashing since v6.x was
: released. Then again, the radius server opens/closes its connections as
: required, instead of relynig on one persistent connection, so maybe that
: helps, but that's just "application programming" vs backend...

: Also, PostgreSQL is the *key* element to the virtual email system that I
: built around Cyrus IMAPd several months back...if PostgreSQL was "flakey",
: I'd have users losing email left, right and center...basically, *all* mail
: delivery, and user authentication, relies on PostgreSQL being up 24/7
: *period*...and I consider that one to be even more mission critical then
: the accounting system above.

Seems, we are in the same business. :-) But do you never vacuum? Do you never,
ever do something which blocks the database for more than a second or so? I
would never trust any database (not PostgreSQL and not Oracle and not any
other database) to be so reliable, they are just to complex and there are
just too many situations where they would not be reachable or block the
access for too long. An email system I build has nearly 2 million POP accesses
per day. That is more than a thausend authentications per minute (actually the
accesses are not evenly spread around the day, so this is a very rough
calculation). Even if the database is fast enough to handle this, it would
mean that a one minute breakdown of the database, for any reason, would make
1000 customers unhappy. That is not something I could sleep well with...

But coming back to the original question about the reliability of PostgreSQL.
Am I the only one using the "advanced features", like plpgsql procedures,
triggers, rules, etc.? Most of the problems I have encountered lie with these
kind of things and not with basic functionality. If you just use your
PostgreSQL as a kind of Berkeley DB with SQL, you will probabely not have too
many problems. Maybe these parts are tested more thoroughly? Many people seem
to use databases only as a directory service. If most of your accesses to
the database are reading not writing, if you never do any joins, no subselects,
no triggers and no other fancy stuff, then you are not really using the things
a RDBMS is for. And if PostgreSQL is only good enough for this kind of work,
it is not doing its job.

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Mon Nov 22 05:20:49 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA19007
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 05:20:14 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id SAA17430
for <pgsql-general@postgreSQL.org>; Mon, 22 Nov 1999 18:20:15 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma017428; Mon, 22 Nov 99 18:20:12 +0800
Message-Id: <3.0.5.32.19991122182051.0084c7a0@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 22 Nov 1999 18:20:51 +0800
To: PostreSQL <pgsql-general@postgreSQL.org>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] logging stuff in the right sequence.
In-Reply-To: <4.2.0.58.19991122040848.009ab6c0@mailer.isn.net>
References: <3837B126.DF95D1F4@mail.ocis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

I'm trying to set up logging tables and need a bit of help.

I would like to ensure that things are stored so that they can be retrieved
in the correct sequence.

The example at http://www.postgresql.org/docs/postgres/rules17277.htm
says:
CREATE TABLE shoelace_log (
sl_name char(10), -- shoelace changed
sl_avail integer, -- new available value
log_who name, -- who did it
log_when datetime -- when
);

CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
WHERE NEW.sl_avail != OLD.sl_avail
DO INSERT INTO shoelace_log VALUES (
NEW.sl_name,
NEW.sl_avail,
getpgusername(),
'now'::text
);

However is there a guarantee that datetime is sufficient for correct order
if an item is updated by different people one after the other at almost the
same time?

I would prefer something like

CREATE TABLE shoelace_log (
log_sequence serial -- sequence of events
sl_name char(10), -- shoelace changed
sl_avail integer, -- new available value
log_who name, -- who did it
log_when datetime, -- when
);

CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
WHERE NEW.sl_avail != OLD.sl_avail
DO INSERT INTO shoelace_log VALUES (
NEW.sl_name,
NEW.sl_avail,
getpgusername(),
'now'::text
);

However I notice there isn't a column name specification in the DO INSERT
INTO, how would I format the INSERT INTO statement so that log_sequence is
not clobbered? Can I use the normal INSERT into format and specify the
columns? I haven't managed to get it to work that way. Would defining the
sequence at the end of the table help? That would be untidy tho ;).

Can/should I use now() instead of 'now'::text?

The serial type is an int4. Hmm, there actually may be more than 2 billion
updates to keep track off :). But I suppose we could cycle the logs and
resequence.

Cheerio,

Link.

From bouncefilter Mon Nov 22 08:30:50 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id IAA40576
for pgsql-general@postgresql.org; Mon, 22 Nov 1999 08:30:16 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: Rudolf ter Haar <terhaar@dutw38.wbmt.tudelft.nl>
X-Newsgroups: comp.databases.postgresql.questions
Subject: importing and exporting large objects
Date: Mon, 22 Nov 1999 14:36:49 +0100
Organization: Delft University of Technology
Lines: 20
Message-ID: <383946F0.39B798B6@dutw38.wbmt.tudelft.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.tudelft.nl 943277400 28820 130.161.19.134 (22 Nov 1999 13:30:00
GMT)
X-Complaints-To: usenet@news.tudelft.nl
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: en
To: pgsql-questions@postgresql.org

Hi there,

I have the following situation:

Postgres server on a linux / Unix box up and running

and

A PC running windows 98
On the PC I have some files.
I'd like to save those files into the database instead of saving in the
filesystem.

What is the general approach in these cases ???
How do you import a file into a database field ???

Kind regards

Rudolf ter haar

From bouncefilter Mon Nov 22 08:40:50 1999
Received: from nefertiti.pasteur.fr (nefertiti.pasteur.fr [157.99.64.20])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA41375
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 08:39:59 -0500 (EST)
(envelope-from bortz@pasteur.fr)
Received: from ezili.sis.pasteur.fr (ezili.sis.pasteur.fr [157.99.60.56])
by nefertiti.pasteur.fr (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id
dAMDdnL28895; Mon, 22 Nov 1999 14:39:49 +0100 (MET)
Received: from pasteur.fr (localhost [127.0.0.1])
by ezili.sis.pasteur.fr (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id
OAA25296; Mon, 22 Nov 1999 14:39:51 +0100
Message-Id: <199911221339.OAA25296@ezili.sis.pasteur.fr>
X-Authentication-Warning: ezili.sis.pasteur.fr: Host localhost [127.0.0.1]
claimed to be pasteur.fr
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
From: Stephane Bortzmeyer <bortzmeyer@pasteur.fr>
To: Jason <jcl@mail.ocis.net>
cc: PostreSQL <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Debian w/ DBI/DBD
In-reply-to: <3837B126.DF95D1F4@mail.ocis.net>
(Jason <jcl@mail.ocis.net>'s message of
Sun, 21 Nov 1999 16:45:26 +0800)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 Nov 1999 14:39:47 +0100
Sender: bortz@pasteur.fr

On Sunday 21 November 1999, at 16 h 45, the keyboard of Jason
<jcl@mail.ocis.net> wrote:

I think I have DBI and DBD installed OK, and postgres seems to be
working OK. But, I can not access DBI from a perl script. I get a
DBI/Pg.pm not found,

Install the 'libdbd-pg-perl' package.

From bouncefilter Mon Nov 22 08:46:50 1999
Received: from qube.dsdeurne.nl (185.144.dialin.mxs.nl [143.179.144.185])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA42338
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 08:46:37 -0500 (EST)
(envelope-from w.aarts@dsdeurne.nl)
Received: from dsdeurne.nl (dsd21.dsdeurne.nl [10.254.211.60])
by qube.dsdeurne.nl (8.9.2/8.9.2) with ESMTP id OAA02277
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 14:44:02 +0100 (CET)
Message-ID: <383948E0.5465E126@dsdeurne.nl>
Date: Mon, 22 Nov 1999 14:45:04 +0100
From: Wim Aarts <w.aarts@dsdeurne.nl>
Organization: DSDeurne Automatisering
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: PostgreSQL Question <pgsql-general@postgresql.org>
Subject: What would be a good way to append some text to the end of a text
field?
Content-Type: multipart/mixed; boundary="------------F140422667F1C8E4D0B32956"

This is a multi-part message in MIME format.
--------------F140422667F1C8E4D0B32956
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Now I use php3 to read the text from the database then I append some
text to it and finaly I do an update on the text field.
Is it possible to use an SQL statement to do this directly in the
database?

Thanks Wim.

I use: Posgresql 6.5.3 Linux 5.2 PHP3

--------------F140422667F1C8E4D0B32956
Content-Type: text/x-vcard; charset=us-ascii;
name="w.aarts.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Wim Aarts
Content-Disposition: attachment;
filename="w.aarts.vcf"

begin:vcard
n:Aarts;Wim
tel;cell:06-20598154
tel;fax:0493-351319
tel;work:0493-351320
x-mozilla-html:TRUE
url:www.dsdeurne.nl
org:DSDeurne Automatisering bv;Development
adr:;;Dr. Hub v. Doorneweg 14;Deurne;;5750 AG;Nederland
version:2.1
email;internet:w.aarts@dsdeurne.nl
title:ir
note;quoted-printable:Algemeen e-mail adres:=0D=0Amail@dsdeurne.nl
fn:Wim Aarts
end:vcard

--------------F140422667F1C8E4D0B32956--

From bouncefilter Mon Nov 22 10:12:51 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id KAA55014
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 10:12:34 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 11881 invoked by uid 417); 22 Nov 1999 15:41:33 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 22 Nov 1999 15:41:33 -0000
Message-ID: <00cd01bf34fb$d080c980$8602a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-general" <pgsql-general@postgresql.org>
Subject: Rule plan string to big, HELP!
Date: Mon, 22 Nov 1999 16:11:08 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Hi,

I keep running into problems with:

ERROR: DefineQueryRewrite: rule plan string too big.

Does anyone have any insights into this? And how to fix this?

Hoping for help,

Joost Roeleveld

ps. I am willing to post _all_ Create-queries I use if anyone thinks he/she
can
fix it in my case.

From bouncefilter Mon Nov 22 10:34:52 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id KAA91975
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 10:34:00 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 13890 invoked by uid 417); 22 Nov 1999 16:02:36 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 22 Nov 1999 16:02:36 -0000
Message-ID: <011c01bf34fe$c18c5400$8602a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-general" <pgsql-general@postgresql.org>
Subject: Rule plan string to big, HELP!
Date: Mon, 22 Nov 1999 16:32:14 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Hi,

I keep running into problems with:

ERROR: DefineQueryRewrite: rule plan string too big.

Does anyone have any insights into this? And how to fix this?

Hoping for help,

Joost Roeleveld

ps. I am willing to post _all_ Create-queries I use if anyone thinks he/she
can fix it in my case.

pps. sending this again, because it's not showing up as being sent....

From bouncefilter Mon Nov 22 10:30:52 1999
Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA91717
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 10:30:43 -0500 (EST)
(envelope-from jaco@gospelsjop.com)
Received: from gospelsjop.com ([212.83.89.116]) by relay01.chello.nl
(InterMail v4.01.00 201-232-112) with ESMTP
id <19991122153702.VMCM10258.relay01@gospelsjop.com>
for <pgsql-general@postgreSQL.org>; Mon, 22 Nov 1999 16:37:02 +0100
Sender: jaco
Message-ID: <383962C9.3D739AC9@gospelsjop.com>
Date: Mon, 22 Nov 1999 16:35:38 +0100
From: Jaco de Groot <jaco@gospelsjop.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i486)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: drop/rename table and transactions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Every now and then I get the following error:

cannot write block 0 of tablename [username] blind

If this happens, all my database connections get this error when trying
to access the database and I need to restart postgresql. The problem
causing this error needs to be something like this:

create table table2 (col1 text);
insert into table2 (col1) values ('some data');
begin work;
drop table table1;
alter table table2 rename to table1;
commit;

I've been playing with some statements to repeat the error, but I
haven't
been able to succesfully repeat the error (only once, but doing the
same didn't cause the error again). Maybe it has something to do with
using multiple connections.

Trying some statements I found an other error, using these statements:

create table table1 (col1 text);
begin work;
drop table table1;
alter table table2 rename to table1;
create table table2 (col1 text);
commit;
select * from table1;

Caused:

couldn't open table1: No such file or directory

I'm using postgresql-6.5.2-1.i386.rpm.

Is the posgresql development team aware of these errors and will
they be fixed?

Gr. Jaco

From bouncefilter Mon Nov 22 10:43:52 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA95644
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 10:43:45 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11pvcy-000LECC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Mon, 22 Nov 1999 09:43:40 -0600 (CST)
Date: Mon, 22 Nov 1999 09:43:40 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: Wim Aarts <w.aarts@dsdeurne.nl>
Cc: PostgreSQL Question <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] What would be a good way to append some text to the end
of a text field?
Message-ID: <19991122094340.B8160@wallace.ece.rice.edu>
References: <383948E0.5465E126@dsdeurne.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <383948E0.5465E126@dsdeurne.nl>;
from Wim Aarts on Mon, Nov 22, 1999 at 02:45:04PM +0100

On Mon, Nov 22, 1999 at 02:45:04PM +0100, Wim Aarts wrote:

Now I use php3 to read the text from the database then I append some
text to it and finaly I do an update on the text field.
Is it possible to use an SQL statement to do this directly in the
database?

Like this?

test=> create table test_text (word_id int, words text);
CREATE
test=> insert into test_text values (1, 'some text');
INSERT 684150 1
test=> insert into test_text values (2, 'some other text');
INSERT 684151 1
test=> select * from test_text;
word_id|words
-------+---------------
1|some text
2|some other text
(2 rows)

test=> update test_text set words = textcat(words,', and text added later') where word_id=1;
UPDATE 1
test=> select * from test_text;word_id|words
-------+-------------------------------
2|some other text
1|some text, and text added later
(2 rows)

test=>

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

From bouncefilter Mon Nov 22 10:57:52 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id KAA98085
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 10:57:49 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 17490 invoked by uid 417); 22 Nov 1999 16:26:49 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 22 Nov 1999 16:26:49 -0000
Message-ID: <015201bf3502$23b2f280$8602a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-general" <pgsql-general@postgresql.org>
Cc: <j.roeleveld@softhome.net>
Subject: Rule plan string to big, HELP!
Date: Mon, 22 Nov 1999 16:56:26 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Hi,

I keep running into problems with:

ERROR: DefineQueryRewrite: rule plan string too big.

Does anyone have any insights into this? And how to fix this?

Hoping for help,

Joost Roeleveld

ps. I am willing to post _all_ Create-queries I use if anyone thinks he/she
can fix it in my case.

pps. sending this again, because it's not showing up as being sent....

From bouncefilter Mon Nov 22 11:16:52 1999
Received: from qube.dsdeurne.nl (36.144.dialin.mxs.nl [143.179.144.36])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA01530
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 11:16:29 -0500 (EST)
(envelope-from w.aarts@dsdeurne.nl)
Received: from dsdeurne.nl (dsd21.dsdeurne.nl [10.254.211.60])
by qube.dsdeurne.nl (8.9.2/8.9.2) with ESMTP id RAA12175;
Mon, 22 Nov 1999 17:13:50 +0100 (CET)
Message-ID: <38396BFA.83F9EF60@dsdeurne.nl>
Date: Mon, 22 Nov 1999 17:14:50 +0100
From: Wim Aarts <w.aarts@dsdeurne.nl>
Organization: DSDeurne Automatisering
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: PostgreSQL Question <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] What would be a good way to append some text to the end
of a text field?
References: <383948E0.5465E126@dsdeurne.nl>
<19991122094340.B8160@wallace.ece.rice.edu>
Content-Type: multipart/mixed; boundary="------------118C07D0AF54F0C081F190A4"

This is a multi-part message in MIME format.
--------------118C07D0AF54F0C081F190A4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks Ross,

Sorry I didn't come with an example but I meant something like:

test=> create table test_text (word_id int, words text);
CREATE
test=> insert into test_text values (1, 'some text');
INSERT 684150 1
test=> UPDATE test_text SET words = words + 'some more text' WHERE word_id = 1;

Resulting in:
test=> SELECT * FROM test_text;
word_id|words
-------+---------------
1|some text some more text

Hope this explains my question.

Thanks.

"Ross J. Reedstrom" wrote:

On Mon, Nov 22, 1999 at 02:45:04PM +0100, Wim Aarts wrote:

Now I use php3 to read the text from the database then I append some
text to it and finaly I do an update on the text field.
Is it possible to use an SQL statement to do this directly in the
database?

Like this?

test=> create table test_text (word_id int, words text);
CREATE
test=> insert into test_text values (1, 'some text');
INSERT 684150 1
test=> insert into test_text values (2, 'some other text');
INSERT 684151 1
test=> select * from test_text;
word_id|words
-------+---------------
1|some text
2|some other text
(2 rows)

test=> update test_text set words = textcat(words,', and text added later') where word_id=1;
UPDATE 1
test=> select * from test_text;word_id|words
-------+-------------------------------
2|some other text
1|some text, and text added later
(2 rows)

test=>

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

--------------118C07D0AF54F0C081F190A4
Content-Type: text/x-vcard; charset=us-ascii;
name="w.aarts.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Wim Aarts
Content-Disposition: attachment;
filename="w.aarts.vcf"

begin:vcard
n:Aarts;Wim
tel;cell:06-20598154
tel;fax:0493-351319
tel;work:0493-351320
x-mozilla-html:TRUE
url:www.dsdeurne.nl
org:DSDeurne Automatisering;Development
adr:;;Dr. Hub v. Doorneweg 14;Deurne;;5750 AG;Nederland
version:2.1
email;internet:w.aarts@dsdeurne.nl
title:ir
note;quoted-printable:Algemeen e-mail adres:=0D=0Amail@dsdeurne.nl
fn:Wim Aarts
end:vcard

--------------118C07D0AF54F0C081F190A4--

From bouncefilter Mon Nov 22 11:29:53 1999
Received: from qube.dsdeurne.nl (69.144.dialin.mxs.nl [143.179.144.69])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA03412
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 11:29:25 -0500 (EST)
(envelope-from w.aarts@dsdeurne.nl)
Received: from dsdeurne.nl (dsd21.dsdeurne.nl [10.254.211.60])
by qube.dsdeurne.nl (8.9.2/8.9.2) with ESMTP id RAA12270;
Mon, 22 Nov 1999 17:26:38 +0100 (CET)
Message-ID: <38396EF9.A7ED9F85@dsdeurne.nl>
Date: Mon, 22 Nov 1999 17:27:38 +0100
From: Wim Aarts <w.aarts@dsdeurne.nl>
Organization: DSDeurne Automatisering
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: PostgreSQL Question <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] What would be a good way to append some text to the end
of a text field?
References: <383948E0.5465E126@dsdeurne.nl>
<19991122094340.B8160@wallace.ece.rice.edu>
Content-Type: multipart/mixed; boundary="------------1BAC5450129CC64E20C1FE4E"

This is a multi-part message in MIME format.
--------------1BAC5450129CC64E20C1FE4E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sorry Ross,

I replied to early, the second example covers it.....Oops

Wim.

"Ross J. Reedstrom" wrote:

On Mon, Nov 22, 1999 at 02:45:04PM +0100, Wim Aarts wrote:

Now I use php3 to read the text from the database then I append some
text to it and finaly I do an update on the text field.
Is it possible to use an SQL statement to do this directly in the
database?

Like this?

test=> create table test_text (word_id int, words text);
CREATE
test=> insert into test_text values (1, 'some text');
INSERT 684150 1
test=> insert into test_text values (2, 'some other text');
INSERT 684151 1
test=> select * from test_text;
word_id|words
-------+---------------
1|some text
2|some other text
(2 rows)

test=> update test_text set words = textcat(words,', and text added later') where word_id=1;
UPDATE 1
test=> select * from test_text;word_id|words
-------+-------------------------------
2|some other text
1|some text, and text added later
(2 rows)

test=>

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

--------------1BAC5450129CC64E20C1FE4E
Content-Type: text/x-vcard; charset=us-ascii;
name="w.aarts.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Wim Aarts
Content-Disposition: attachment;
filename="w.aarts.vcf"

--------------1BAC5450129CC64E20C1FE4E--

From bouncefilter Mon Nov 22 12:34:53 1999
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
by hub.org (8.9.3/8.9.3) with SMTP id MAA24926
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 12:34:41 -0500 (EST) (envelope-from khtao@yahoo.com)
Received: from miyuki1.mysolution.com (HELO p2400arcane) (216.37.18.145)
by smtp.mail.yahoo.com with SMTP; 22 Nov 1999 09:33:57 -0800
X-Apparently-From: <khtao@yahoo.com>
Message-ID: <005b01bf3510$77632b80$040101c0@p2400arcane>
From: "K.Tao" <khtao@yahoo.com>
To: "The Hermit Hacker" <scrappy@hub.org>
Cc: "Jochen Topf" <pgsql-general@mail.remote.org>,
<pgsql-general@postgresql.org>
References: <Pine.BSF.4.10.9911220057160.14653-100000@thelab.hub.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Date: Mon, 22 Nov 1999 12:38:42 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Well I do apologize as all my experiences are in the use of pre 6.5
versions...I assume there have no longer been any reports of databases
having to be rebuilt or restored from tape from the way you are talking ;)

Although I still feel that the level of expertise for an admin on a Unix
platform running PostgreSQL is much higher than lets say Oracle on NT. One
example is if you cancel out of a admin process like vacuum while in pgsql.
U have to have enough exp to know what files to go and delete to be able to
get pgsql back up and running.

I do think that the commercial support program moves PostgreSQL much closer
to being a database I would choose. I havent had the requirement for that
support, but I am sure if I had a large system utilizing PostgreSQL I would
not hesitate to pay to make sure 24x7 I can get the database back up and
runniog within 15 mins of it going down :)

I also do like the sound of getting rid of vacuum and its table locks.
Anythng to make the database more self administering and self recovering is
good ;)

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

From bouncefilter Mon Nov 22 14:25:57 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA44528;
Mon, 22 Nov 1999 14:25:00 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp87.kross.klever.net
[209.203.65.87]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id MAA10462; Mon, 22 Nov 1999 12:22:36 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <38399881.513D4947@ironmountainsystems.com>
Date: Mon, 22 Nov 1999 11:24:49 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
References: <3.0.1.32.19991120121645.008b0e70@mail.diligence.com>
Content-Type: multipart/alternative;
boundary="------------F63D31D4F8A45BDC36C9B5F2"

--------------F63D31D4F8A45BDC36C9B5F2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have been surprised by the response to this question. I was hoping that the
responses would be more consistent, after all when software is unreliable it
is generally known by all users.

Although one would expect a subjective bias to the opinions, the answers
provided in the thread are highly polarized. Jochen Topf gave a frightening
description of an unreliable database which gave unpredictable results. For
example:

The most frustrating thing is that most bugs are not repeatable or at least
not repeatable in a small test script that I could send in with a bug report.
Looking at the bug reports that come through the mailing list, there are a
lots of the type: X works here but not in this similar situation. This is
IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5
to 6.5.1 or something like that) helped a little bit but on the other hand
some query optimizations that worked before didn't work anymore.

This is pretty scary.

However, I then read another reply only to find that Brett McCoy is converting
"hundreds of thousands of documents" with no PostgresSQL problems at all.
Brett indicates that:

So I think PostgreSQL is quite solid and reliable. The only thing I think
that is sorely needed in PostgreSQL is referential integrity constraints
like foreign keys (although this can be emulated with triggers).

In fact, the lack of referential integrity constraints happens to be my
biggest concern - assuming the database is reliable, something that is proving
hard to determine.

Reading on, I see that "The Hermit Hacker" (love the name) also finds the
database to be reliable:

Odd, I've been using PostgreSQL since v1.x for exactly this same reason,
and we haven't had any problems with the database crashing since v6.x was
released. Then again, the radius server opens/closes its connections as
required, instead of relynig on one persistent connection, so maybe that
helps, but that's just "application programming" vs backend...

There is a subtle implication that perhaps Jochen's problems are self
inflicted. In a later email, Jochen responds and asks if he is the only one
using "advanced features" and suggests that they may be the cause of his
problems. However, his list of "advanced features" is a little scary since
that are the very features that makes PostgreSQL so attractive in the first
place - and I fully intend to use them!

So which is is guys, is this database dependable for commercial use - or is an
academic oddity, worth watching but not using?

Any other success or failure stories would be really helpful....

Is PostgresSQL ready for prime time, or is it limpware?

Steve

-------------------------------------------------

PS This thread was started in pgsql-general, I cross posted to pgsql-novice as
I am sure that some readers of that group would be interested in this topic.
If you want to comment, please reply to pgsql-general@postgreSQL.org, I don't
want to fork the thread!

--------------F63D31D4F8A45BDC36C9B5F2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I have been surprised by the response to this question.  I was hoping
that the responses would be more consistent, after all when software is
unreliable it is generally known by all users.
<p>Although one would expect a subjective bias to the opinions, the answers
provided in the thread are highly polarized.   Jochen Topf gave
a frightening description of an unreliable database which gave unpredictable
results.  For example:
<blockquote TYPE=CITE>
<pre>The most frustrating thing is that most bugs are not repeatable or at least
not repeatable in a small test script that I could send in with a bug report.
Looking at the bug reports that come through the mailing list, there are a
lots of the type: X works here but not in this similar situation. This is
IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5
to 6.5.1 or something like that) helped a little bit but on the other hand
some query optimizations that worked before didn't work anymore.</pre>
</blockquote>

<p><br>This is pretty scary.
<p>However, I then read another reply only to find that Brett McCoy is
converting "hundreds of thousands of documents" with no PostgresSQL problems
at all.  Brett indicates that:
<blockquote TYPE=CITE>
<pre>So I think PostgreSQL is quite solid and reliable.  The only thing I think
that is sorely needed in PostgreSQL is referential integrity constraints
like foreign keys (although this can be emulated with triggers).</pre>
</blockquote>

<p><br>In fact, the lack of referential integrity constraints happens to
be my biggest concern - assuming the database is reliable, something that
is proving hard to determine.
<p>Reading on, I see that "The Hermit Hacker" (love the name) also finds
the database to be reliable:
<blockquote TYPE=CITE>
<pre>Odd, I've been using PostgreSQL since v1.x for exactly this same reason,
and we haven't had any problems with the database crashing since v6.x was
released.  Then again, the radius server opens/closes its connections as
required, instead of relynig on one persistent connection, so maybe that
helps, but that's just "application programming" vs backend...</pre>
</blockquote>

<p><br>There is a subtle implication that perhaps Jochen's problems are
self inflicted.  In a later email, Jochen responds and asks if he
is the only one using "advanced features" and suggests that they may be
the cause of his problems.  However, his list of "advanced features"
is a little scary since that are the very features that makes PostgreSQL
so attractive in  the first place - and I fully intend to use them!
<p>So which is is guys, is this database dependable for commercial use
- or is an academic oddity, worth watching but not using?
<p>Any other success or failure stories would be really helpful....
<p>Is PostgresSQL ready for prime time, or is it limpware?
<p>Steve
<p>-------------------------------------------------
<p>PS This thread was started in pgsql-general, I cross posted to pgsql-novice
as I am sure that some readers of that group would be interested in this
topic.  If you want to comment, please reply to pgsql-general@postgreSQL.org,
I don't want to fork the thread!
<br> </html>

--------------F63D31D4F8A45BDC36C9B5F2--

From bouncefilter Mon Nov 22 14:28:55 1999
Received: from solaris1.mysolution.com (ns.mysolution.com [216.37.18.100])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA46521
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 14:28:14 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id OAA12936
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 14:18:24 -0500 (EST)
Message-ID: <002701bf3520$6bbc6e80$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: <pgsql-general@postgreSQL.org>
Subject: Fw: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Date: Mon, 22 Nov 1999 14:32:44 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

From: K.Tao <khtao@yahoo.com>
To: The Hermit Hacker <scrappy@hub.org>
Cc: Jochen Topf <pgsql-general@mail.remote.org>;
<pgsql-general@postgreSQL.org>
Sent: Monday, November 22, 1999 12:38 PM
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?

Well I do apologize as all my experiences are in the use of pre 6.5
versions...I assume there have no longer been any reports of databases
having to be rebuilt or restored from tape from the way you are talking ;)

Although I still feel that the level of expertise for an admin on a Unix
platform running PostgreSQL is much higher than lets say Oracle on NT.

One

example is if you cancel out of a admin process like vacuum while in

pgsql.

U have to have enough exp to know what files to go and delete to be able

get pgsql back up and running.

I do think that the commercial support program moves PostgreSQL much

closer

to being a database I would choose. I havent had the requirement for that
support, but I am sure if I had a large system utilizing PostgreSQL I

would

not hesitate to pay to make sure 24x7 I can get the database back up and
runniog within 15 mins of it going down :)

I also do like the sound of getting rid of vacuum and its table locks.
Anythng to make the database more self administering and self recovering

good ;)

From bouncefilter Mon Nov 22 16:55:00 1999
Received: from mail1.panix.com (mail1.panix.com [166.84.0.212])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA71029
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 16:54:26 -0500 (EST)
(envelope-from tomg@admin.nrnet.org)
Received: from mailhost.nrnet.org (mailhost.nrnet.org [166.84.192.39])
by mail1.panix.com (Postfix) with ESMTP
id 01B8A30F39; Mon, 22 Nov 1999 16:52:35 -0500 (EST)
Received: from admin.nrnet.org (uucp@localhost)
by mailhost.nrnet.org (8.8.7/8.8.4) with UUCP
id QAA01212; Mon, 22 Nov 1999 16:19:13 -0500
Received: from localhost (tomg@localhost)
by admin.nrnet.org (8.9.1/8.9.1) with ESMTP id QAA03511;
Mon, 22 Nov 1999 16:19:35 -0500
Date: Mon, 22 Nov 1999 16:19:34 -0500 (EST)
From: Thomas Good <tomg@admin.nrnet.org>
To: Stephen Birch <sbirch@ironmountainsystems.com>
Cc: The Hermit Hacker <scrappy@hub.org>,
PostgreSQL List <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <38399881.513D4947@ironmountainsystems.com>
Message-ID: <Pine.LNX.4.05.9911221604390.3119-100000@admin.nrnet.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 22 Nov 1999, Stephen Birch wrote:

I have been surprised by the response to this question. I was hoping that the
responses would be more consistent, after all when software is unreliable it
is generally known by all users.

Steve - I tried to post an answer earlier (and it was verbose as is my
tendency!) but apparently it bounced. I will cc the list, you and
scrappy on this note.

I converted my shop from FoxPro and PROGRESS (on UnixWare) to Postgres on
Linux/BSD this past year. 12 years worth of data. My users are clinical
staff *not* computer ppl (in fact they are computer-phobic) and have made
myriad mistakes in entering and retrieving data via network and dialup
connections. Our electricians have swapped feeder cables while my boxes
were online - ouch. And I have made dubious errors in programming as I
learned perl, CGI and DBI. But throughout it all, PG has suffered all of
our blunders and our predilection for the text data type.

Social Workers love to talk, even in their clinical progress notes.
But PG rolls with the punches and everyday I find new reasons to love this
database. Performance is good (better on UnixWare and BSD than Linux)
and I am really happy that the Pg SQL is less idiosyncratic than Oracle.

Perl has become a 4GL of sorts for me (replacing PROGRESS) and my > 140
character apps are now being ported to CGI for a netscape interface.
They work well...

I can't say enuf about how much I like postgres and - how much my users
like it. They suffered with PROGRESS (slooooow) and FoxPro (corruption).
I run Oracle on Linux and have tried Sybase and Informix too. I'll stick
with Postgres. MySQL and mSQL are too much like flat file db's (concurrency
control matters here) for me to even consider using them (I did try mSQL
and didn't much care for it...)

I use Pg ver 6.3.2 which is *rock* solid altho I'm told 6.5.x is faster.
I may upgrade at some point but I feel very comfortable with 6.3.2 as I
know it runs a wide array of mission critical apps with good speed and
and good reliability. The tech support from the likes of Vadim and
Bruce (and volunteers like Herouth M and Brett) is also something I've
gotten used to...I often waffle between which unix I like best but I
know which database I prefer.

Cheers,
Tom

------- North Richmond Community Mental Health Center -------

Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056

/* Member: Computer Professionals For Social Responsibility */

From bouncefilter Mon Nov 22 18:07:57 1999
Received: from gw.aerojetpd.com (gort.aerojet.com [198.211.213.51])
by hub.org (8.9.3/8.9.3) with SMTP id SAA83334;
Mon, 22 Nov 1999 18:07:07 -0500 (EST)
(envelope-from patrick.wolf@Aerojet.com)
Received: by gw.aerojetpd.com (940816.SGI.8.6.9/940406.SGI)
id PAA16310; Mon, 22 Nov 1999 15:07:06 -0800
Received: from mihub.aerojetpd.com(144.217.13.36) by gw.aerojetpd.com via smap
(V1.3) id sma016199; Mon Nov 22 15:06:07 1999
Received: from apd-mail2.aerojetpd.com ([144.217.20.213])
by neon.aerojetpd.com (Netscape Mail Server v2.02) with ESMTP
id AAA28083; Mon, 22 Nov 1999 15:06:06 -0800
Received: by APD-MAIL2 with Internet Mail Service (5.5.2448.0)
id <XHHV7WRC>; Mon, 22 Nov 1999 15:06:01 -0800
Message-ID: <63A19D0F08E6D211AD740008C7B1C47B05FD51@APD-MAIL1>
From: patrick.wolf@Aerojet.com (WOLF, PATRICK)
To: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: RE: [NOVICE] Re: [GENERAL] Re: Is PostgreSQL ready for mission cr
iticalapplications?
Date: Mon, 22 Nov 1999 15:05:54 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

All I can do is offer my own testimonial:

I'm using postgreSQL 6.5.x on 3 different RedHat Linux Intel systems. All
have been working fine to my inexperienced eye. I'm running small databases
on all of them. The most complex has about 25 tables with maybe 250 - 300
fields total. I'm using MS Access with ODBC for most of the work. Some I'm
doing using the perl Pg library and I'm writing cgi scripts to generate html
pages. Nothing is too terribly complicated. I've got about 20,000 columns
in various tables on that database. The other two probably don't even have
a few hundred entries yet, I've just started with those.

I've had less problems using PostgreSQL than using the commercial database
that I'm porting everything from. And the upgrade costs are much less.

Pat

-----Original Message-----
From: Stephen Birch [mailto:sbirch@ironmountainsystems.com]
Sent: Monday, November 22, 1999 12:25 PM
To: pgsql-general@postgreSQL.org; pgsql-novice@postgreSQL.org
Subject: [NOVICE] Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?

I have been surprised by the response to this question. I was hoping that
the responses would be more consistent, after all when software is
unreliable it is generally known by all users.

Although one would expect a subjective bias to the opinions, the answers
provided in the thread are highly polarized. Jochen Topf gave a
frightening description of an unreliable database which gave unpredictable
results. For example:

The most frustrating thing is that most bugs are not repeatable or at least

not repeatable in a small test script that I could send in with a bug
report.

Looking at the bug reports that come through the mailing list, there are a

lots of the type: X works here but not in this similar situation. This is

IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5

to 6.5.1 or something like that) helped a little bit but on the other hand

some query optimizations that worked before didn't work anymore.

This is pretty scary.

However, I then read another reply only to find that Brett McCoy is
converting "hundreds of thousands of documents" with no PostgresSQL problems
at all. Brett indicates that:

So I think PostgreSQL is quite solid and reliable. The only thing I think

that is sorely needed in PostgreSQL is referential integrity constraints

like foreign keys (although this can be emulated with triggers).

In fact, the lack of referential integrity constraints happens to be my
biggest concern - assuming the database is reliable, something that is
proving hard to determine.

Reading on, I see that "The Hermit Hacker" (love the name) also finds the
database to be reliable:

Odd, I've been using PostgreSQL since v1.x for exactly this same reason,

and we haven't had any problems with the database crashing since v6.x was

released. Then again, the radius server opens/closes its connections as

required, instead of relynig on one persistent connection, so maybe that

helps, but that's just "application programming" vs backend...

So which is is guys, is this database dependable for commercial use - or is
an academic oddity, worth watching but not using?

Any other success or failure stories would be really helpful....

Is PostgresSQL ready for prime time, or is it limpware?

Steve

-------------------------------------------------

PS This thread was started in pgsql-general, I cross posted to pgsql-novice
as I am sure that some readers of that group would be interested in this
topic. If you want to comment, please reply to
pgsql-general@postgreSQL.org, I don't want to fork the thread!

From bouncefilter Mon Nov 22 19:02:57 1999
Received: from cuaima.ica.luz.ve (vegeta@cuaima.ica.luz.ve [150.185.194.30])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA91080
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 19:02:43 -0500 (EST)
(envelope-from vegeta@cuaima.ica.luz.ve)
Received: from localhost (vegeta@localhost)
by cuaima.ica.luz.ve (8.8.8/8.8.8) with ESMTP id UAA08820
for <pgsql-general@postgresql.org>; Mon, 22 Nov 1999 20:06:33 -0400
Date: Mon, 22 Nov 1999 20:06:33 -0400 (VET)
From: Vegeta <vegeta@cuaima.ica.luz.ve>
To: pgsql-general@postgresql.org
Subject: A Question about Large Object (fwd)
Message-ID: <Pine.LNX.4.05.9911222002550.8818-100000@cuaima.ica.luz.ve>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello.

I'm trying to store a jpeg file into a table created as follow:

CREATE TABLE vegeta (
name text,
photo oid
);

I can insert a jpeg file from pgsql (locally) but I cannot do this from
an application written in Visual Basic using an ODBC driver (V06-40-0006).

I read psqlodbc FAQs (Can I use large objects or OLE?) but I'd prefer not
to deal with clean-up tasks.

Someone could tell me any suggestion?

Thanks in advance!

Vegeta.

From bouncefilter Mon Nov 22 19:57:58 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA98696
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 19:57:12 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id TAA03857
for pgsql-general@postgreSQL.org; Mon, 22 Nov 1999 19:56:56 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911230056.TAA03857@candle.pha.pa.us>
Subject: European SANE conference needs speakers
To: PostgreSQL-general <pgsql-general@postgreSQL.org>
Date: Mon, 22 Nov 1999 19:56:56 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The 2nd International SANE Conference needs speakers.

I was approached to give a talk on PostgreSQL, and have submitted
a request to be a speaker.

The conference is in Maastricht, The Netherlands. I realize many of
you could also speak about PostgreSQL and are closer to the Netherlands.

If you are interested in speaking, you can get more information at:

http://www.nluug.nl/sane/

You will have to make your submission soon because the deadline was
today.

If anyone has comments about the conference, I would be interested.
Please e-mail me directly.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 22 20:07:58 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA00240
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 20:07:09 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id VAA52313
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 21:07:25 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 21:07:24 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
Subject: Hers's one with the COPY command ...
Message-ID: <Pine.BSF.4.10.9911222102080.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have a table created as:

=============
DROP TABLE referer_raw_data;
CREATE TABLE referer_raw_data (
counter_id int4,
referer_url_domain varchar(256),
referer_counter int4,
date_added datetime default now());
=============

I wish to copy a stream of data to it as:

5\thttp://thissite\t3\t...

where the date *isn't* part of the copy, since I want to set it as the
date that the record was added...is this possible? now, from the docs, I
realize that it will ignore the default, which I'm okay with, but is there
a way of passing it now(), or something similar, to set the data?

basically, I want to stream web data to the backend as fast as the backend
will take it, with COPY TO being faster then INSERT INTO, but don't want
to have to "create a date" to insert at the same time...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 22 20:22:58 1999
Received: from 21cn.com ([202.104.32.242])
by hub.org (8.9.3/8.9.3) with SMTP id UAA02619
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 20:22:39 -0500 (EST)
(envelope-from sciman-devd@21cn.com)
From: sciman-devd@21cn.com
Received: from 21cn.com([10.1.3.100]) by 21cn.com(JetMail 2.3.2.1)
with SMTP id /aimcque/jmail.rcv/8/jm123839ec59;
Tue, 23 Nov 1999 01:21:14 -0000
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Message-ID: <JR008876907955.18496@mail2.21cn.com>
Date: Tue, 23 Nov 1999 09:20:44 +0800 (CST)
To: pgsql-general@postgresql.org
Cc: performance
Subject:
X-Priority: 3

i love postgresql very much and i want to use her in my application for customer but i could not know her precision performance compared with Oracle ,Sybase or Informix.who could tell me? Thanks in advance!
----------------------------------------------
��ӭʹ�� 21CN ��ʼ�ϵͳhttp://www.21cn.com
Thank you for using 21CN Email system

From bouncefilter Mon Nov 22 20:23:58 1999
Received: from 21cn.com ([202.104.32.242])
by hub.org (8.9.3/8.9.3) with SMTP id UAA02667
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 20:23:12 -0500 (EST)
(envelope-from sciman-devd@21cn.com)
From: sciman-devd@21cn.com
Received: from 21cn.com([10.1.3.100]) by 21cn.com(JetMail 2.3.2.1)
with SMTP id /aimcque/jmail.rcv/7/jm213839ec9a;
Tue, 23 Nov 1999 01:22:20 -0000
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Message-ID: <J0008876907782.18496@mail2.21cn.com>
Date: Tue, 23 Nov 1999 09:22:17 +0800 (CST)
To: pgsql-general@postgresql.org
Cc:
Subject: performance
X-Priority: 3

From bouncefilter Mon Nov 22 20:37:58 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA04856
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 20:37:06 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id VAA52542;
Mon, 22 Nov 1999 21:37:11 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 21:37:10 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "K.Tao" <khtao@yahoo.com>
cc: Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <005b01bf3510$77632b80$040101c0@p2400arcane>
Message-ID: <Pine.BSF.4.10.9911222133270.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 22 Nov 1999, K.Tao wrote:

Well I do apologize as all my experiences are in the use of pre 6.5
versions...I assume there have no longer been any reports of databases
having to be rebuilt or restored from tape from the way you are talking ;)

Although I still feel that the level of expertise for an admin on a
Unix platform running PostgreSQL is much higher than lets say Oracle
on NT. One example is if you cancel out of a admin process like
vacuum while in pgsql. U have to have enough exp to know what files to
go and delete to be able to get pgsql back up and running.

Actually, I believe the pg_vlock file is planned for removal in v7.0 ...
just checked the current source tree, and this hasn't happened yet, but
there was talk on -hackers about removing it since MVCC invalidates the
requirement of locking all tables in a database while doing the vacuum...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 22 21:33:00 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA12172;
Mon, 22 Nov 1999 21:32:39 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id WAA56436;
Mon, 22 Nov 1999 22:32:37 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 22:32:31 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Stephen Birch <sbirch@ironmountainsystems.com>
cc: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <38399881.513D4947@ironmountainsystems.com>
Message-ID: <Pine.BSF.4.10.9911222148291.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Everyone has their own experiences, and difficulties...there are X
platforms out there that PostgreSQL supports, multiply that by however
many different hardware pieces that be thrown the standard box, and you'll
get that many different experiences...would i use it in a mission critical
box? yes, I do on several. have I ever had problems...to be honest,
yes...most of them at the application level.

take a look at:

http://www.pgsql.com/projects/projects.cgi?sort=name

There are ppl there working on projects such as:

Arctic and Antarctic Research Center
- Scripps Institution of Oceanography / Frank Delahoyde

CFAR Molecular Biology Core
- University of California San Diego / David J. Looney

Online Community Newspaper
- Alex Wilson Coldstream Ltd / Anil Amarakoon

Camping-USA!
- Camping-USA! / Vince Vielhaber

POS System for Retail Shop
- PIPSE Information System Co. / Yewon Heo

Postgres Mail Database
- National Center for Supercomputing Applications / Duane Moore

Software2Go Online Store
- Software2Go, LLC / Eric Schnoebelen

Univ Texas @ Arlington - Engineering Distance Learning Site
- Univ Texas @ Arlington / Charlie Lindahl

Utility Billing
- City Of Lake Lotawana / A. Van Hook

And that is just a select listing of all the projects currently listed,
and doesn't include several hundred that I'm still enterign into the new
system...

Each one of those is mission critical to the person using it, and, in some
cases, I'd say to the ppl that they affect (Utility Billing and POS System
are the two that come to mind there)...

Any bugs/limitation of the current system can be worked around, and will
be improved in each release, as they have been to date. Each release is
generally leaps ahead of previous releases...even the minor releases
contain changes that improve things...

Quite frankly, I think the fact that Jochen is still around *even though*
he has problems says alot about the quality of both the software and the
development processes that we've developed over the past year, and also
gives a good indication of where we are going...

If you are still hestitant, write your application in such a way that if
things get to the point that you just can't stay with PostgreSQL, you can
switch. Use perl/dbi, so that you can switch with a simple chagne to the
connect string, its what I do...except, in my case, its to make sure that
I can do all my development work in PostgreSQL, while keepign in mind that
the end user might not feel comfortable with that, and/or to keep options
open for them in the future...so far, I've been lucky, and all my clients
have been quite happy with PostgreSQL as well...

On Mon, 22 Nov 1999, Stephen Birch wrote:

I have been surprised by the response to this question. I was hoping that the
responses would be more consistent, after all when software is unreliable it
is generally known by all users.

Although one would expect a subjective bias to the opinions, the answers
provided in the thread are highly polarized. Jochen Topf gave a frightening
description of an unreliable database which gave unpredictable results. For
example:

The most frustrating thing is that most bugs are not repeatable or at least
not repeatable in a small test script that I could send in with a bug report.
Looking at the bug reports that come through the mailing list, there are a
lots of the type: X works here but not in this similar situation. This is
IMHO a symptom of a bad design. A recent upgrade (I think it was from 6.5
to 6.5.1 or something like that) helped a little bit but on the other hand
some query optimizations that worked before didn't work anymore.

This is pretty scary.

However, I then read another reply only to find that Brett McCoy is converting
"hundreds of thousands of documents" with no PostgresSQL problems at all.
Brett indicates that:

So I think PostgreSQL is quite solid and reliable. The only thing I think
that is sorely needed in PostgreSQL is referential integrity constraints
like foreign keys (although this can be emulated with triggers).

In fact, the lack of referential integrity constraints happens to be my
biggest concern - assuming the database is reliable, something that is proving
hard to determine.

Reading on, I see that "The Hermit Hacker" (love the name) also finds the
database to be reliable:

Odd, I've been using PostgreSQL since v1.x for exactly this same reason,
and we haven't had any problems with the database crashing since v6.x was
released. Then again, the radius server opens/closes its connections as
required, instead of relynig on one persistent connection, so maybe that
helps, but that's just "application programming" vs backend...

There is a subtle implication that perhaps Jochen's problems are self
inflicted. In a later email, Jochen responds and asks if he is the only one
using "advanced features" and suggests that they may be the cause of his
problems. However, his list of "advanced features" is a little scary since
that are the very features that makes PostgreSQL so attractive in the first
place - and I fully intend to use them!

So which is is guys, is this database dependable for commercial use - or is an
academic oddity, worth watching but not using?

Any other success or failure stories would be really helpful....

Is PostgresSQL ready for prime time, or is it limpware?

Steve

-------------------------------------------------

PS This thread was started in pgsql-general, I cross posted to pgsql-novice as
I am sure that some readers of that group would be interested in this topic.
If you want to comment, please reply to pgsql-general@postgreSQL.org, I don't
want to fork the thread!

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Nov 22 21:40:59 1999
Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA13826
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 21:40:49 -0500 (EST)
(envelope-from davidb@vectormath.com)
From: davidb@vectormath.com
Received: from bullwinkle (adsl-204-1-67-149.indi.se.verio.net [204.1.67.149])
by sakaki.communique.net (8.8.8/8.8.8) with SMTP id UAA22271
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 20:39:04 -0600 (CST)
Message-ID: <001301bf355b$ee87b370$0402010a@bullwinkle.Radix>
To: <pgsql-general@postgreSQL.org>
Subject: Re: Is PostgreSQL ready for ...
Date: Mon, 22 Nov 1999 20:38:57 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4

I think the problem is that nobody wants to say "Oh yeah, solid as a rock!"
and then have someone die as a result of a database error. However, I have
personally witnessed unrepeatable database errors in both MSSQL and Oracle.
Those databases both have marketing departments widely touting them as
"mission critical" databases. I've had MSSQL databases fill the log tables
with crap to the point where the whole database crashes because Microsoft
decided it was time for a dll change -- and they didn't tell anyone "Hey, be
sure to un-check the 'Let Microsoft ruin your life' checkbox". (that was an
emergency personnel tracking database on an offshore oil rig). I've managed
the development of an entire application based on Y2K compliant Oracle only
to find out that it's only Y2K compliant if you enclose EVERY SINGLE READ
AND WRITE in a goofy-ass "FORMAT" statement. Although, if you don't use the
FORMAT statement, it will still accept four digit year entries without
barking, and it will also display four digit years based on the two digit
year it actually stores (so I guess if you never know the difference, what
does it matter, right?). By the way, even if you use the Format statement,
Oracle still craps out after 2035 (it was a rather carefully worded Y2K
compliance statement that accompanied that application). (that application
was a safety statistics tracking database). Soooo, for my part, I now put
my faith in a database whose proponents do not face financial ruin if they
tell you the truth. I much prefer a "Not yet implemented" message from the
database, or a "this is still a little wonky" message from the developer, I
much prefer that rather than the confident assurances you receive from
Microsoft and Oracle. Especially when you pass on those confident
assurances to your client and wind up looking like an ass.

Sorry to explode. I feel better...

David Boerwinkle

From bouncefilter Mon Nov 22 21:53:59 1999
Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA15495
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 21:53:29 -0500 (EST)
(envelope-from davidb@vectormath.com)
From: davidb@vectormath.com
Received: from bullwinkle (adsl-204-1-67-149.indi.se.verio.net [204.1.67.149])
by sakaki.communique.net (8.8.8/8.8.8) with SMTP id UAA26644
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 20:51:45 -0600 (CST)
Message-ID: <003701bf355d$b3d4ed90$0402010a@bullwinkle.Radix>
To: <pgsql-general@postgreSQL.org>
Subject: Re: Is PostgreSQL ready for ...
Date: Mon, 22 Nov 1999 20:51:48 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4

I think the problem is that nobody wants to say "Oh yeah, solid as a rock!"
and then have someone die as a result of a database error. However, I have
personally witnessed unrepeatable database errors in both MSSQL and Oracle.
Those databases both have marketing departments widely touting them as
"mission critical" databases. I've had MSSQL databases fill the log tables
with crap to the point where the whole database crashes because Microsoft
decided it was time for a dll change -- and they didn't tell anyone "Hey, be
sure to un-check the 'Let Microsoft ruin your life' checkbox". (that was an
emergency personnel tracking database on an offshore oil rig). I've managed
the development of an entire application based on Y2K compliant Oracle only
to find out that it's only Y2K compliant if you enclose EVERY SINGLE F***ING
READ
AND WRITE in a goofy-ass "FORMAT" statement. Although, if you don't use the
FORMAT statement, it will still accept four digit year entries without
barking, and it will also display four digit years based on the two digit
year it actually stores (so I guess if you never know the difference, what
does it matter, right?). By the way, even if you use the Format statement,
Oracle still craps out after 2035. (that application was a safety
statistics
tracking database). Soooo, for my part, I now put my faith in a database
whose proponents do not face financial ruin if they tell you the truth. I
much
prefer a "Not yet implemented" message from the database, or a "this is
still a little wonky" message from the developer, I much prefer that rather
than the confident assurances you receive from Microsoft and Oracle.
Especially when you pass on those confident assurances to your client and
wind up looking like an ass.

Sorry to explode. I feel better...

David Boerwinkle

From bouncefilter Mon Nov 22 22:29:00 1999
Received: from solaris1.mysolution.com (adachi.mysolution.com [216.37.18.104])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA20905
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 22:28:14 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id WAA24179;
Mon, 22 Nov 1999 22:18:21 -0500 (EST)
Message-ID: <000901bf3563$79b80240$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: "The Hermit Hacker" <scrappy@hub.org>,
"Stephen Birch" <sbirch@ironmountainsystems.com>
Cc: <pgsql-general@postgreSQL.org>
References: <Pine.BSF.4.10.9911222148291.14653-100000@thelab.hub.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
Date: Mon, 22 Nov 1999 22:32:43 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

The reason why opinions are so varied has alot to do with the expertise of
each person in relation to PostgreSQL and Linux. Often problems that are
considered simple to resolve by some are very difficult for others. And
sometimes problems are caused by actions that are done out of inexperince
with the system like cancelling certain operations in progress etc...
You probably would not be able to determine reliability from opinions. The
thing is PostgreSQL is extremely reliable if u know what you are doing and
know how to handle/get around any bugs.

Lookig at some of the other posts about reliability...the number of records
in a database will mainly determine the ability of a database to maintain
performance at larger file/index sizes. It does not really impact
stability. Stability is mainly affected by the number of
reads/updates/inserts that are performed. Usually u want to look at large
user loads, large transaction loads and large number of
updates/inserts/deletes to gauge reliability. I havent seen anyone post
saying that they are running a system that does this...perhaps I just missed
the post.

can I ask what type of application u aer going to use PostgreSQL for?

----- Original Message -----
From: The Hermit Hacker <scrappy@hub.org>
To: Stephen Birch <sbirch@ironmountainsystems.com>
Cc: <pgsql-general@postgresql.org>; <pgsql-novice@postgresql.org>
Sent: Monday, November 22, 1999 9:32 PM
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?

Everyone has their own experiences, and difficulties...there are X
platforms out there that PostgreSQL supports, multiply that by however
many different hardware pieces that be thrown the standard box, and you'll
get that many different experiences...would i use it in a mission critical
box? yes, I do on several. have I ever had problems...to be honest,
yes...most of them at the application level.

On Mon, 22 Nov 1999, Stephen Birch wrote:

I have been surprised by the response to this question. I was hoping

that the

responses would be more consistent, after all when software is

unreliable it

is generally known by all users.

Although one would expect a subjective bias to the opinions, the answers
provided in the thread are highly polarized. Jochen Topf gave a

frightening

description of an unreliable database which gave unpredictable results.

For

example:

The most frustrating thing is that most bugs are not repeatable or at

least

not repeatable in a small test script that I could send in with a bug

report.

Looking at the bug reports that come through the mailing list, there

are a

lots of the type: X works here but not in this similar situation. This

IMHO a symptom of a bad design. A recent upgrade (I think it was from

6.5

to 6.5.1 or something like that) helped a little bit but on the other

hand

some query optimizations that worked before didn't work anymore.

This is pretty scary.

However, I then read another reply only to find that Brett McCoy is

converting

"hundreds of thousands of documents" with no PostgresSQL problems at

all.

Brett indicates that:

So I think PostgreSQL is quite solid and reliable. The only thing I

think

that is sorely needed in PostgreSQL is referential integrity

constraints

like foreign keys (although this can be emulated with triggers).

In fact, the lack of referential integrity constraints happens to be my
biggest concern - assuming the database is reliable, something that is

proving

hard to determine.

Reading on, I see that "The Hermit Hacker" (love the name) also finds

the

database to be reliable:

Odd, I've been using PostgreSQL since v1.x for exactly this same

reason,

and we haven't had any problems with the database crashing since v6.x

was

released. Then again, the radius server opens/closes its connections

required, instead of relynig on one persistent connection, so maybe

that

helps, but that's just "application programming" vs backend...

There is a subtle implication that perhaps Jochen's problems are self
inflicted. In a later email, Jochen responds and asks if he is the only

one

using "advanced features" and suggests that they may be the cause of his
problems. However, his list of "advanced features" is a little scary

since

that are the very features that makes PostgreSQL so attractive in the

first

place - and I fully intend to use them!

So which is is guys, is this database dependable for commercial use - or

is an

academic oddity, worth watching but not using?

Any other success or failure stories would be really helpful....

Is PostgresSQL ready for prime time, or is it limpware?

Steve

From bouncefilter Mon Nov 22 22:44:00 1999
Received: from solaris1.mysolution.com ([216.37.18.102])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA23112
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 22:43:23 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id WAA24552
for <pgsql-general@postgreSQL.org>;
Mon, 22 Nov 1999 22:33:36 -0500 (EST)
Message-ID: <001101bf3565$9a8c05a0$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: <pgsql-general@postgreSQL.org>
References: <003701bf355d$b3d4ed90$0402010a@bullwinkle.Radix>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for ...
Date: Mon, 22 Nov 1999 22:47:58 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Bah, no comment on Microsofts reliability :)
But Oracle I have used extensively 7.x versions. I implicitly trust its
reliability...except I heard of some probs with version 8 when it came out
:) Cant imagine someone using the same version of the database for 35 years
tho. By that time you would have upgraded I would imagine. And Oracle
upgrades its data types with no probs...

----- Original Message -----
From: <davidb@vectormath.com>
To: <pgsql-general@postgreSQL.org>
Sent: Monday, November 22, 1999 9:51 PM
Subject: [GENERAL] Re: Is PostgreSQL ready for ...

emergency personnel tracking database on an offshore oil rig). I've

managed

the development of an entire application based on Y2K compliant Oracle

only

to find out that it's only Y2K compliant if you enclose EVERY SINGLE

F***ING

READ
AND WRITE in a goofy-ass "FORMAT" statement. Although, if you don't use

the

FORMAT statement, it will still accept four digit year entries without
barking, and it will also display four digit years based on the two digit
year it actually stores (so I guess if you never know the difference, what
does it matter, right?). By the way, even if you use the Format

statement,

Oracle still craps out after 2035. (that application was a safety

From bouncefilter Mon Nov 22 22:53:00 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA24318
for <pgsql-general@postgresql.org>;
Mon, 22 Nov 1999 22:52:26 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA59191;
Mon, 22 Nov 1999 23:52:19 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 22 Nov 1999 23:52:13 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Kane Tao <khtao@yahoo.com>
cc: Stephen Birch <sbirch@ironmountainsystems.com>,
pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <000901bf3563$79b80240$040101c0@p2400arcane>
Message-ID: <Pine.BSF.4.10.9911222351040.14653-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 22 Nov 1999, Kane Tao wrote:

The reason why opinions are so varied has alot to do with the expertise of
each person in relation to PostgreSQL and Linux. Often problems that are

Ack, you know the discussion is going downhill when someone mentioned
Linux *sigh* *big, friendly, Daemon grin*

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Tue Nov 23 01:02:02 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA46010
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 01:01:40 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id OAA25086;
Tue, 23 Nov 1999 14:01:39 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma025082; Tue, 23 Nov 99 14:01:15 +0800
Message-Id: <3.0.5.32.19991123140154.0088fa10@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 23 Nov 1999 14:01:54 +0800
To: davidb@vectormath.com, <pgsql-general@postgreSQL.org>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for ...
In-Reply-To: <003701bf355d$b3d4ed90$0402010a@bullwinkle.Radix>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:51 PM 22-11-1999 -0600, davidb@vectormath.com wrote:

tracking database). Soooo, for my part, I now put my faith in a database
whose proponents do not face financial ruin if they tell you the truth. I
much
prefer a "Not yet implemented" message from the database, or a "this is
still a little wonky" message from the developer, I much prefer that rather
than the confident assurances you receive from Microsoft and Oracle.
Especially when you pass on those confident assurances to your client and
wind up looking like an ass.

Yeah!

I want truths. I'm a technical guy, I didn't get good technical knowledge
by believing lies and fuzzy stuff.

Thing is, Postgres could go various ways depending on the goals.

If the priorities include stability and reliability, that's what you get.
If the priorities are features at any cost, you get junk.

Though Open Source projects are less susceptible to featuritis, they're far
from immune. Trouble is many PHBs only compare stuff feature by brochure
feature.

Hmm, I must remember to put in "Maximum of one restart/reboot per year
subject to clause X" in tender specs.

Cheerio,

Link.

From bouncefilter Tue Nov 23 01:21:02 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA48279
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 01:20:25 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
BAA18462;
Tue, 23 Nov 1999 01:18:59 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911230618.BAA18462@candle.pha.pa.us>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for ...
In-Reply-To: <3.0.5.32.19991123140154.0088fa10@pop.mecomb.po.my> from Lincoln
Yeoh at "Nov 23, 1999 02:01:54 pm"
To: Lincoln Yeoh <lylyeoh@mecomb.com>
Date: Tue, 23 Nov 1999 01:18:59 -0500 (EST)
CC: davidb@vectormath.com, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

If the priorities include stability and reliability, that's what you get.
If the priorities are features at any cost, you get junk.

Though Open Source projects are less susceptible to featuritis, they're far
from immune. Trouble is many PHBs only compare stuff feature by brochure
feature.

We only do 2-3 major releases a year for a reason. If it is not
reliable, it is useless. This is not a computer game.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 23 01:45:02 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA50776
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 01:44:54 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id OAA25505;
Tue, 23 Nov 1999 14:44:54 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma025503; Tue, 23 Nov 99 14:44:38 +0800
Message-Id: <3.0.5.32.19991123144516.008ba100@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 23 Nov 1999 14:45:16 +0800
To: Bruce Momjian <pgman@candle.pha.pa.us>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for ...
Cc: davidb@vectormath.com, pgsql-general@postgreSQL.org
In-Reply-To: <199911230618.BAA18462@candle.pha.pa.us>
References: <3.0.5.32.19991123140154.0088fa10@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:18 AM 23-11-1999 -0500, Bruce Momjian wrote:

If the priorities include stability and reliability, that's what you get.
If the priorities are features at any cost, you get junk.

Though Open Source projects are less susceptible to featuritis, they're far
from immune. Trouble is many PHBs only compare stuff feature by brochure
feature.

We only do 2-3 major releases a year for a reason. If it is not
reliable, it is useless. This is not a computer game.

Yep. Glad to hear that.

My boss asked "MSSQL or Postgres" and a colleague and I said "Postgres". I
figured we'd have fewer problems with Postgres, so what if we couldn't
point fingers at someone else, better to get things done/fixed. Still good
to hear that reliability is high on your list.

Another colleague, was an Oracle guy and was nervous about Postgres - coz
if anything goes wrong he may have to help :). But Oracle was way too
pricey- we could have bought a house at the price they gave us...

In contrast: Netscape proudly proclaimed that when it was a choice between
features and stability, features always won. Explains a lot.

Cheerio,

Link.

From bouncefilter Tue Nov 23 03:10:05 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA63838
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 03:09:51 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11qB1K-0004B7-00; Tue, 23 Nov 1999 09:09:50 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11qArL-0000eg-00
for pgsql-general@postgresql.org; Tue, 23 Nov 1999 08:59:31 +0100
Date: Tue, 23 Nov 1999 08:59:30 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission criticalapplications?
Message-ID: <19991123085929.A2440@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

Kane Tao <death@solaris1.mysolution.com> wrote:
: The reason why opinions are so varied has alot to do with the expertise of
: each person in relation to PostgreSQL and Linux. Often problems that are
: considered simple to resolve by some are very difficult for others. And
: sometimes problems are caused by actions that are done out of inexperince
: with the system like cancelling certain operations in progress etc...
: You probably would not be able to determine reliability from opinions. The
: thing is PostgreSQL is extremely reliable if u know what you are doing and
: know how to handle/get around any bugs.

Sorry, this is simply not true. We are talking about reliability here and
not about some features that might be difficult to find for the inexperienced
user or something like that. For instance, I had to fight with PostgreSQL and
Perl to get Notify to work. It might be difficult to get this to work, because
the lack of documentation or bugs in the way it is implemented, but I got
it to work. This is the thing a beginner stumbles over, and if not persistent
enough will label as a bug, although it might be only the documentation that
is buggy, or his level of understanding of the workings of the database is
just not good enough.

But I am not imagining the random "I have rolled back the current transaction
and am going to terminate your database system connection and exit." messages.
If there is a way to kill a database as a normal user, it is not reliable.
Maybe, if I knew more about PostgreSQL, I would be able to not trigger the
bugs, but that is not the point. The bugs should not be there or there
should be at least a meaningful error message saying: "I am sorry Dave, I can't
let you do this, because it would trigger a bug." I have seen random chrashes
without any indication to the problem and I have seen strange messages
hinting at a problem deep down in a btree implementation or something like
that. And the worst thing is, that these bugs are not repeatable in a way
that someone could start debugging them or at least work around them.

To be fair, I have never lost any data (or had it corrupted) that was
already *in* the database, although there is one unresolved case, which might
have been a database corruption but was probabely an application error. But
I have lost data, because the application wasn't able to put it in the
database in the first place and the database was not accessible. But that is
probabely an application error too, because it only buffered data in memory
and not on disk, in case of a database failure. I thought that this is enough,
because databases are supposed to be more reliable then simple filesystems...

: Lookig at some of the other posts about reliability...the number of records
: in a database will mainly determine the ability of a database to maintain
: performance at larger file/index sizes. It does not really impact
: stability. Stability is mainly affected by the number of
: reads/updates/inserts that are performed. Usually u want to look at large
: user loads, large transaction loads and large number of
: updates/inserts/deletes to gauge reliability. I havent seen anyone post
: saying that they are running a system that does this...perhaps I just missed
: the post.

While this is generally true, a huge database can have an impact on
stability. For instance, if you have a very small memory leak, it will not
show in small databases but might show in big ones, triggering a bug. Or
an index grows over some bound and a hash file has to be increased or whatever.
And there are some problems of this kind in PostgreSQL. I am logging all
logins and logouts from a radius server into PostgreSQL and after it ran
well for several months, it slowed to a crawl and vacuum wouldn't work
anymore. So, yes, I do have a lot of inserts, although about 6000 inserts a
day and a total of a few hundert thausend records is not really much.

My question of an earlier posting is still not answered. Does anybody here,
who reported PostgreSQL to be very stable, use advanced features like pl/pgsql
procedures, triggers, rules and notifies? Lets have a show of hands. I would
really like to know, why I am the only one having problems. :-) Although
it might be, because, as this is a PostgreSQL mailing list, most of the
readers are people who are happy with PostgreSQL, because all the others
have left and are on an Oracle list now. :-)

I would really, really like PostgreSQL to be stable and useful for mission
critical things, because it has some very nice features, is easy to setup,
and easy to maintain and generally a lot better then all the other databases
I know, weren't it for the problems described above. I hope that my criticism
here is not perceived as PostgreSQL bashing but as an attempt to understand
why so many people are happy with PostgreSQL and I am not.

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Tue Nov 23 03:20:03 1999
Received: from volcano.DEFUDATA.DK ([195.97.164.2])
by hub.org (8.9.3/8.9.3) with SMTP id DAA65230
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 03:19:52 -0500 (EST) (envelope-from kar@webline.dk)
Received: from VOLCANO [195.97.164.2] (HELO localhost)
by volcano.DEFUDATA.DK (AltaVista Mail V2.0J/2.0J BL25J listener)
id 0000_004c_383a_4db8_e5b8; Tue, 23 Nov 1999 09:18:00 +0100
Message-ID: <383A4E20.5E6ADF4E@webline.dk>
Date: Tue, 23 Nov 1999 09:19:44 +0100
From: Kaare Rasmussen <kar@webline.dk>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: [GENERAL] Re: Is PostgreSQL ready for mission criticalapplications?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

But I am not imagining the random "I have rolled back the current

transaction

and am going to terminate your database system connection and exit."

messages.

I'm wondering if you ever reported these problems to this list or the
the hackers list? I've been reading both regularily and don't recall
seeing this descussed before, but maybe I'm wrong.

Generally I find the responsiveness from the development team way better
than any commercial products. _All_ problem reports are treated with
concern. So if you didn't report them before, please take the time to
document your experience and send the problem report to the correct
place.

From bouncefilter Tue Nov 23 03:44:04 1999
Received: from morahalom.hu (IDENT:qmailr@linux.morahalom.hu [194.9.65.29])
by hub.org (8.9.3/8.9.3) with SMTP id DAA68295
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 03:43:12 -0500 (EST)
(envelope-from roodie@morahalom.hu)
Received: (qmail 6864 invoked from network); 23 Nov 1999 08:44:48 -0000
Received: from unknown (HELO morahalom.hu) (10.0.0.1)
by linux.morahalom.hu with SMTP; 23 Nov 1999 08:44:48 -0000
Message-ID: <383A5386.D451539D@morahalom.hu>
Date: Tue, 23 Nov 1999 09:42:46 +0100
From: Roodie <roodie@morahalom.hu>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

subscribe
end

From bouncefilter Tue Nov 23 03:52:04 1999
Received: from morahalom.hu (IDENT:qmailr@linux.morahalom.hu [194.9.65.29])
by hub.org (8.9.3/8.9.3) with SMTP id DAA69232
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 03:51:26 -0500 (EST)
(envelope-from roodie@morahalom.hu)
Received: (qmail 6987 invoked from network); 23 Nov 1999 08:53:03 -0000
Received: from unknown (HELO morahalom.hu) (10.0.0.1)
by linux.morahalom.hu with SMTP; 23 Nov 1999 08:53:03 -0000
Message-ID: <383A5574.F0A1CC30@morahalom.hu>
Date: Tue, 23 Nov 1999 09:51:01 +0100
From: Roodie <roodie@morahalom.hu>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: PL
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi!
Just a quick question: is there a PL/pgSQL in the 6.5.1 version?
I cannot find it, but I need some functionality it offers.
Any help?

--
----------------------------------------------------------------------
Roodie aka Steve aka Farkas Istv�n ICQ: 53623985 ; Linux, C++
VisualBasic, Quake, Ars Magica, AD&D, Lightwave 3D, Mutant Chronicles

From bouncefilter Tue Nov 23 03:53:04 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA69308
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 03:52:34 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id QAA27042
for <pgsql-general@postgreSQL.org>; Tue, 23 Nov 1999 16:52:31 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma027029; Tue, 23 Nov 99 16:51:50 +0800
Message-Id: <3.0.5.32.19991123165228.008c6820@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 23 Nov 1999 16:52:28 +0800
To: PostreSQL <pgsql-general@postgreSQL.org>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] logging stuff in the right sequence.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

I'm trying to set up logging tables and need a bit of help.

I would like to ensure that things are stored so that they can be retrieved
in the correct sequence.

CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
WHERE NEW.sl_avail != OLD.sl_avail
DO INSERT INTO shoelace_log VALUES (
NEW.sl_name,
NEW.sl_avail,
getpgusername(),
'now'::text
);

However is there a guarantee that datetime is sufficient for correct order
if an item is updated by different people one after the other at almost the
same time?

I would prefer something like

CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
WHERE NEW.sl_avail != OLD.sl_avail
DO INSERT INTO shoelace_log VALUES (
NEW.sl_name,
NEW.sl_avail,
getpgusername(),
'now'::text
);

Can/should I use now() instead of 'now'::text?

The serial type is an int4. Hmm, there actually may be more than 2 billion
updates to keep track off :). But I suppose we could cycle the logs and
resequence.

Cheerio,

Link.

From bouncefilter Tue Nov 23 04:36:04 1999
Received: from ns.prov-liege.be (ns.prov-liege.be [193.190.122.12])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA75421
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 04:35:38 -0500 (EST)
(envelope-from Fabian.Frederick@prov-liege.be)
From: Fabian.Frederick@prov-liege.be
Received: by ns.prov-liege.be; (8.8.8/1.3/10May95) id KAA12369;
Tue, 23 Nov 1999 10:29:59 +0100 (GMT+0100)
Received: by mesepl.epl.prov-liege.be with Internet Mail Service (5.5.1960.3)
id <WP9VR5J1>; Tue, 23 Nov 1999 10:33:32 +0100
Message-ID: <17AB709C82E5D111ACF20000F805F4532B402C@mesadm.epl.prov-liege.be>
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] Socket file lock
Date: Tue, 23 Nov 1999 10:33:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

Hi,

Sometimes I've got some core socket file in /tmp.However Postgres leaved
correctly in previous shutdown : /

What would be the best way to avoid this. (The big big problem is that
postmaster can't be launched due to that core).

Regards, Fabian

From bouncefilter Tue Nov 23 21:33:16 1999
Received: from mail.toppoint.de (LaForge.toppoint.de [195.244.243.6])
by hub.org (8.9.3/8.9.3) with SMTP id VAA17693;
Tue, 23 Nov 1999 21:33:15 -0500 (EST)
(envelope-from feki.toppoint.de!marten@toppoint.de)
Received: by mail.toppoint.de (Smail3.1.29.1)
id <m11qSEx-0002JxC>; Wed, 24 Nov 99 03:33 MET
Received: (from marten@localhost)
by feki.toppoint.de (8.9.3/8.9.3) id KAA18422;
Tue, 23 Nov 1999 10:42:23 +0100
From: marten@feki.toppoint.de
Message-Id: <199911230942.KAA18422@feki.toppoint.de>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <38399881.513D4947@ironmountainsystems.com> from Stephen Birch at
"Nov 22, 1999 11:24:49 am"
To: sbirch@ironmountainsystems.com (Stephen Birch)
Date: Tue, 23 Nov 1999 10:42:23 +0100 (CET)
Cc: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL47 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

So which is is guys, is this database dependable for commercial use - or is an
academic oddity, worth watching but not using?

For me it depends on what you use in PostreSQL. Some basic stuff is working
really well in PostgreSQL - other parts have problems.

As I've written earlies in some postings. Our company is evaluating
PostgreSQL to get a solid database for a research project and perhaps
later for a product. We've used Adabas-D in our previous products.

We've written a PostgreSQL->Smalltalk/X wrapper, now we are developing
a oo->rdmbs framework on top of it and we've noticed the following
problems with PostgreSQL 6.5.1:

a) Due to the database layouts we are in need of doing all these nice
sql-statements like "group by" and "having" ... and as posted earlier
in this group: they're limited in PostgreSQL.

Now if you need these aggregations urgently you get many, many
problems and you have to produce work-arounds ...

And this is one reason for all problems running around: as with
all programming languages all these guys come with special SQL
knowledge (e.g. I use these statements very much ...) and now
you come to POstgreSQL and find out, that these statements are
special.

Our application relies on "groub by" and "having" due to the fact,
that we store our attributes for objects not column-wide but
row-wide. Therefore you've the need for much more complicated
SQL commands to retrieve the attribute values for one object - if
they do not work - you have really problems.

Now working two months with PostgreSQL I've to admit, that the
database works, but due to the sql limitations we consider to
drop it.

b) We had problems with vacuumdb here and there. Some times it cored.
We've deleted a 300 MB database under psql and the backend cored ...

In general it is no wonder, that some persons tell us: "we use it
with success in our multi-gigabyte database" and others have a totally
different opinion.

When considering the fact, that PostgreSQl is a free database it is
worty. Some persons are developing the database and if I
could have a wish: please, please fix all these limitations of
"groub by" and "having" statements and get closer to the sql standard.

And to mention, how different the expectations are: some persons out
there mentioned, that referential integrity would be a very urgent need
for them - I've the totally different opinion about this:

When doing procedural queries to the database, this need is ok. If you
put a full oo->rdbms wrapper on top of this database and do your
programming in some oo-languages this need vanishes - because referential
integrity does so much in the background, that your object-model in
your application simply becomes wrong - therefore I throw away
referential integrity. It makes the administration for the databases
also much more simplier.

Just my opinion .. not to be misinterpreted. I encourage every work
the people push into PostgreSQL because I want to have a free
database.

Marten

From bouncefilter Tue Nov 23 05:12:05 1999
Received: from bbaer.muenster.de (root@bbaer.muenster.de [195.202.32.20])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA81178
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 05:11:33 -0500 (EST)
(envelope-from holger@klawitter.de)
Received: from klawitter.de (holger@mueasa-wan137.citykom.de [195.202.33.137])
by bbaer.muenster.de (8.8.8/8.8.8) with ESMTP id LAA26136
for <pgsql-general@postgreSQL.org>; Tue, 23 Nov 1999 11:11:29 +0100
Sender: holger@muenster.de
Message-ID: <383A682B.70CF63ED@klawitter.de>
Date: Tue, 23 Nov 1999 11:10:51 +0100
From: Holger Klawitter <holger@klawitter.de>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.2.11 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: PostgreSQL-general <pgsql-general@postgreSQL.org>
Subject: How to do this in Postgres
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi there,

I tried all I could think of with the following problem, perhaps
someone has another idea.

I have a table where for each id there may (and often are) multiple
rows with some kind of priority.
create table data ( id1 int4, id2 int4, <<lots of data>>, prio int4 );
The minimal priority is not guaranteed to be 1. There are 200k
different ids with up to 10 entries, summing up to 400k rows.

Not I want to do something like this:

select * from data where <<prio is minimal per id pair>>.

First attempt (deleting non minimal)
------------------------------------

select a.id1, a.id2, a.prio
into bugos
from a data, b data
where a.prio > b.prio and a.id1 = b.id1 and a.id2 = b.id2;

delete from data
where id1 = bogus.id1 and id2 = bogus.id2 and prio = bogus.prio;

The join does not seem to complete. I am not sure whether I should
have waited longer, but after 4h without significant disk access I
do not think that this thing will ever return. Indexing didn't help.

Second attempt (stored procedures)
----------------------------------

create function GetData( int4, int4 )
returns data
as 'select *
from data
where id1 = $1 and id2 = $2
order by prio
limit 1'
language 'sql';

select GetData(id1,id2) from <<table with unique ids>>;

limit in functions is not yet implemented in postgres (6.5.2)

Third attempt (use perl on dumped table)
----------------------------------------

I don't want to :-)

Regards,
Holger Klawitter
--
Holger Klawitter +49 (0)251 484 0637
holger@klawitter.de http://www.klawitter.de/

From bouncefilter Tue Nov 23 05:44:06 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA85480
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 05:43:43 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11qDQE-0004Ss-00; Tue, 23 Nov 1999 11:43:42 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11qDPn-0000lK-00
for pgsql-general@postgresql.org; Tue, 23 Nov 1999 11:43:15 +0100
Date: Tue, 23 Nov 1999 11:43:14 +0100
From: Jochen Topf <jochen@remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission criticalapplications?
Message-ID: <19991123114313.A2891@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i

Kaare Rasmussen <kar@webline.dk> wrote:
:> But I am not imagining the random "I have rolled back the current
: transaction
:> and am going to terminate your database system connection and exit."
: messages.

: I'm wondering if you ever reported these problems to this list or the
: the hackers list? I've been reading both regularily and don't recall
: seeing this descussed before, but maybe I'm wrong.

: Generally I find the responsiveness from the development team way better
: than any commercial products. _All_ problem reports are treated with
: concern. So if you didn't report them before, please take the time to
: document your experience and send the problem report to the correct
: place.

No I haven't reported them. I have reported a minor bug that I could reproduce
to the bug tracking system. But all the other problems I had, were, as I said,
not reproducable. I tried to come up with a small test case for some of the
bugs and failed. Sure I can report them all, but the developers will tell me,
and rightly so, that they can't do anything with it, because they can't
reproduce it. I know that this is not very helpful, but I know no easy way out
here.

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Tue Nov 23 05:50:05 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA86373
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 05:49:12 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11qDVX-0004TE-00; Tue, 23 Nov 1999 11:49:11 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11qDVK-0000nA-00
for pgsql-general@postgreSQL.org; Tue, 23 Nov 1999 11:48:58 +0100
Date: Tue, 23 Nov 1999 11:48:58 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission criticalapplications?
Message-ID: <19991123114857.A3043@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

: I'm wondering if you ever reported these problems to this list or the
: the hackers list? I've been reading both regularily and don't recall
: seeing this descussed before, but maybe I'm wrong.

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Tue Nov 23 07:12:06 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA96313
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 07:11:09 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11qEmq-0004cJ-00; Tue, 23 Nov 1999 13:11:08 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11qEm9-0000qc-00
for pgsql-general@postgresql.org; Tue, 23 Nov 1999 13:10:25 +0100
Date: Tue, 23 Nov 1999 13:10:25 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
Message-ID: <19991123131024.A3253@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

The Hermit Hacker <scrappy@hub.org> wrote:
: [...]
: take a look at:
: [list deleted]
: Each one of those is mission critical to the person using it, and, in some
: cases, I'd say to the ppl that they affect (Utility Billing and POS System
: are the two that come to mind there)...
: [...]

Well, there are millions of people using Microsoft products for mission
critical applications. I would never do that. :-) Maybe my standards are higher
or my applications different. So this list really doesn't say much. The
problem with databases in general is, that my standards for them are way
higher then for most other pieces of software. If my web server failes, I
restart it. If a mail server fails, I restart it, if syslog failes, I don't
have a log file. But if a database failes, it is generally a lot more trouble.
On the other hand a database is generally, apart from the kernel, the most
complex thing running on your servers...

: Quite frankly, I think the fact that Jochen is still around *even though*
: he has problems says alot about the quality of both the software and the
: development processes that we've developed over the past year, and also
: gives a good indication of where we are going...

This is true. Despite of the problems I had with PostgreSQL, the system
I am using it for still runs PostgreSQL and it sort of works. We have to
reload the database every once in a while, and some of the triggers, I would
like to have, don't work. But basically it works. If you don't have the
money to go for a commercial database, PostgreSQL is not a bad option. But
don't think that everything with PostgreSQL is as bright, like some of the
postings make you believe. Watch your database for performance and other
problems, don't forget the backups and think about how to build your
application that it failes gracefully if the database screws up.

If you have an Oracle database you don't do that, you hire a DBA for it.
There is no way you can do it yourself. :-)

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Tue Nov 23 07:31:09 1999
Received: from relay-smtp2.sip.fr (mailhost.sip.fr [194.2.210.177])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA99139
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 07:30:14 -0500 (EST)
(envelope-from Alain.Tesio@sip.fr)
From: Alain.Tesio@sip.fr
Received: from applications.sip.fr (applications.sip.fr [1.1.1.50])
by relay-smtp2.sip.fr (8.9.1a/jtpda-5.3.1) with SMTP id OAA14255
; Fri, 1 Feb 1980 14:34:47 GMT
Received: by applications.sip.fr(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999)) id
C1256832.00449DCB ; Tue, 23 Nov 1999 13:29:28 +0100
X-Lotus-FromDomain: D_NOTES
To: Holger Klawitter <holger@klawitter.de>,
PostgreSQL-general <pgsql-general@postgreSQL.org>
Message-ID: <C1256832.00449D7E.00@applications.sip.fr>
Date: Tue, 23 Nov 1999 13:34:39 +0100
Subject: Re: [GENERAL] How to do this in Postgres
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

Try this :

select *
from data
group by id1,id2
having prio=min(prio)

I'm not sure it works with Postgres, using Sybase this would
returns a lot of duplicates since the group by mechanism is
a bit strange.

If it does't, this should work :

select id1,id2
into bogus
from data
group by id1,id2
having prio=min(prio)

select data.id1,data.id2,<<lots of data>>
from data,bogus
where data.id1=bogus.id1 and data.id2=bogus.id2

drop table bogus

Alain

--- Holger Klawitter <holger@klawitter.de> wrote:

Hi there,

I tried all I could think of with the following problem, perhaps
someone has another idea.

I have a table where for each id there may (and often are) multiple
rows with some kind of priority.
create table data ( id1 int4, id2 int4, <<lots of data>>, prio
int4 );
The minimal priority is not guaranteed to be 1. There are 200k
different ids with up to 10 entries, summing up to 400k rows.

Not I want to do something like this:

select * from data where <<prio is minimal per id pair>>.

From bouncefilter Tue Nov 23 09:15:07 1999
Received: from ns.prov-liege.be (ns.prov-liege.be [193.190.122.12])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA10828
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 09:14:32 -0500 (EST)
(envelope-from Fabian.Frederick@prov-liege.be)
From: Fabian.Frederick@prov-liege.be
Received: by ns.prov-liege.be; (8.8.8/1.3/10May95) id PAA22782;
Tue, 23 Nov 1999 15:08:42 +0100 (GMT+0100)
Received: by mesepl.epl.prov-liege.be with Internet Mail Service (5.5.1960.3)
id <WP9VR5X1>; Tue, 23 Nov 1999 15:12:15 +0100
Message-ID: <17AB709C82E5D111ACF20000F805F4532B4040@mesadm.epl.prov-liege.be>
To: holger@klawitter.de, pgsql-general@postgreSQL.org
Cc: didier@sonycom.com, christophe.gavage@nrb.be, philippe.frederick@Beldi.be,
dutshs@yahoo.com, franckenj@hotmail.com, frederic.langer@groupes.be,
jean.francois.lefebvre@comexis.com, Freddy.Frederick@readymix.be,
REMACLT1@midas-kapiti.com
Subject: RE: [GENERAL] How to do this in Postgres
Date: Tue, 23 Nov 1999 15:12:10 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

Hi there,

I tried all I could think of with the following problem, perhaps
someone has another idea.

I have a table where for each id there may (and often are) multiple
rows with some kind of priority.
create table data ( id1 int4, id2 int4, <<lots of data>>,
prio int4 );
The minimal priority is not guaranteed to be 1. There are 200k
different ids with up to 10 entries, summing up to 400k rows.

Not I want to do something like this:

select * from data where <<prio is minimal per id pair>>.

First attempt (deleting non minimal)
------------------------------------

select a.id1, a.id2, a.prio
into bugos
from a data, b data
where a.prio > b.prio and a.id1 = b.id1 and a.id2 = b.id2;

delete from data
where id1 = bogus.id1 and id2 = bogus.id2 and prio = bogus.prio;

The join does not seem to complete. I am not sure whether I should
have waited longer, but after 4h without significant disk access I
do not think that this thing will ever return. Indexing didn't help.

Second attempt (stored procedures)
----------------------------------

create function GetData( int4, int4 )
returns data
as 'select *
from data
where id1 = $1 and id2 = $2
order by prio
limit 1'
language 'sql';

select GetData(id1,id2) from <<table with unique ids>>;

limit in functions is not yet implemented in postgres (6.5.2)

Third attempt (use perl on dumped table)
----------------------------------------

I don't want to :-)

IMHO, Perl is the solution,
some foreach architecture on @table should work...
Of course it could be ordinal (usable on fixed row system).
The best would be to recover row name as well(if someone has an
idea to do this ???):

foreach $item in fetched_row{
#Recover row name (Process runned once (rec#1)
???
#Recover row content
}

Regards, Fabian

From bouncefilter Tue Nov 23 10:00:08 1999
Received: from mail.net.uni-c.dk (mail.net.uni-c.dk [130.226.1.3])
by hub.org (8.9.3/8.9.3) with SMTP id JAA17489
for <pgsql-general@hub.org>; Tue, 23 Nov 1999 09:59:52 -0500 (EST)
(envelope-from fk@akf.dk)
From: fk@akf.dk
Message-Id: <199911231459.JAA17489@hub.org>
Received: (qmail 29474 invoked from network); 23 Nov 1999 14:59:47 -0000
Received: from mail.akf.dk (HELO AKF.DK) (130.226.251.9)
by mail.net.uni-c.dk with SMTP; 23 Nov 1999 14:59:47 -0000
Received: from POST/SpoolDir by AKF.DK (Mercury 1.40);
23 Nov 99 15:55:23
Received: from SpoolDir by POST (Mercury 1.40); 23 Nov 99 15:55:11
Organization: AKF
To: pgsql-general@hub.org
Date: Tue, 23 Nov 1999 15:55:05 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Tcl from a Web-browser
X-Confirm-Reading-To: <fk@akf.dk>
X-pmrqc: 1
Priority: normal

Hello out there.

Does anyone know if it's possible to connect to PostGres from a tcl
script running in the plugin of a Web-browser such as Netscape. If it
is, then how does one do it???

Yours faithfully.
Finn Kettner.

From bouncefilter Tue Nov 23 10:54:08 1999
Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA27477
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 10:53:20 -0500 (EST)
(envelope-from rison@biochemistry.ucl.ac.uk)
Received: from biochem.ucl.ac.uk (actually host bsmori1.biochem.ucl.ac.uk)
by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP;
Tue, 23 Nov 1999 15:52:42 +0000
Received: from bsmlx17.biochem.ucl.ac.uk (bsmlx17 [128.40.46.142]) by
biochem.ucl.ac.uk (8.9.2/8.9.1)
with ESMTP id PAA14446; Tue, 23 Nov 1999 15:52:53 GMT
Received: from localhost (rison@localhost)
by bsmlx17.biochem.ucl.ac.uk (8.9.3/8.6.6) with ESMTP id PAA16217;
Tue, 23 Nov 1999 15:58:56 GMT
X-Authentication-Warning: bsmlx17.biochem.ucl.ac.uk: rison owned process doing
-bs
Date: Tue, 23 Nov 1999 15:58:56 +0000 (GMT)
From: Stuart Rison <rison@biochemistry.ucl.ac.uk>
X-Sender: rison@bsmlx17
To: Fabian.Frederick@prov-liege.be
cc: holger@klawitter.de, pgsql-general@postgreSQL.org, didier@sonycom.com,
christophe.gavage@nrb.be, philippe.frederick@Beldi.be,
dutshs@yahoo.com, franckenj@hotmail.com, frederic.langer@groupes.be,
jean.francois.lefebvre@comexis.com, Freddy.Frederick@readymix.be,
REMACLT1@midas-kapiti.com
Subject: RE: [GENERAL] How to do this in Postgres
In-Reply-To: <17AB709C82E5D111ACF20000F805F4532B4040@mesadm.epl.prov-liege.be>
Message-ID: <Pine.LNX.4.10.9911231550410.15806-100000@bsmlx17>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hello,

On Tue, 23 Nov 1999 Fabian.Frederick@prov-liege.be wrote:

Hi there,

I tried all I could think of with the following problem, perhaps
someone has another idea.

I have a table where for each id there may (and often are) multiple
rows with some kind of priority.
create table data ( id1 int4, id2 int4, <<lots of data>>,
prio int4 );
The minimal priority is not guaranteed to be 1. There are 200k
different ids with up to 10 entries, summing up to 400k rows.

Not I want to do something like this:

select * from data where <<prio is minimal per id pair>>.

I'm going to stop here and try and give you a query that does exactly
that (I think).

How about:

select * from data
where (prio,id1,id2) = (
SELECT min(prio) from data d2 where d2.id1=1 and d2.id2=2 group by
d2.id1,d2.id2
);

Seems to work on my -very limited- test table. Trickiest bit was to avoid
the "ERROR: parser: Subselect has too many or too few fields." message
you get if you specify 'where id1=1 and id2=2' in the main SELECT and just
and 'AND prio=(SELECT min(prio)...' [do ignore this if it makes no
sense!].

Should be easy to turn that into a SELECT GetData( int4, int4 ) like
function if you want.

HTH,

Stuart.

Stuart C. G. Rison
Department of Biochemistry and Molecular Biology
6th floor, Darwin Building, University College London (UCL)
Gower Street, London, WC1E 6BT, United Kingdom
Tel. 0207 504 2303, Fax. 0207 380 7193
e-mail: rison@biochem.ucl.ac.uk

From bouncefilter Tue Nov 23 11:06:09 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA29998
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 11:05:17 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 3.3) with ESMTP id RAA01989;
Tue, 23 Nov 1999 17:03:07 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11qK85-0000pb-00; Tue, 23 Nov 1999 17:53:25 +0000
Message-ID: <383ABB59.2191F068@sferacarta.com>
Date: Tue, 23 Nov 1999 17:05:45 +0100
From: jose soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: Roodie <roodie@morahalom.hu>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] PL
References: <383A5574.F0A1CC30@morahalom.hu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

You have to install it
take a look at...
.../src/pl/plpgsql\ directory

Jos�

Roodie ha scritto:

Hi!
Just a quick question: is there a PL/pgSQL in the 6.5.1 version?
I cannot find it, but I need some functionality it offers.
Any help?

--
----------------------------------------------------------------------
Roodie aka Steve aka Farkas Istv�n ICQ: 53623985 ; Linux, C++
VisualBasic, Quake, Ars Magica, AD&D, Lightwave 3D, Mutant Chronicles

************

From bouncefilter Tue Nov 23 11:32:10 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA34352
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 11:31:30 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.9]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 23 Nov 1999 10:23:27 -0600
Sender: ed
Message-ID: <383AC1C1.4574D9DC@austin.rr.com>
Date: Tue, 23 Nov 1999 10:33:05 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Lincoln Yeoh <lylyeoh@mecomb.com>
CC: PostreSQL <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] logging stuff in the right sequence.
References: <3.0.5.32.19991123165228.008c6820@pop.mecomb.po.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lincoln Yeoh wrote:

Hi,

I'm trying to set up logging tables and need a bit of help.

I would like to ensure that things are stored so that they can be retrieved
in the correct sequence.

...

However is there a guarantee that datetime is sufficient for correct order
if an item is updated by different people one after the other at almost the
same time?

I would prefer something like

CREATE TABLE shoelace_log (
log_sequence serial -- sequence of events
sl_name char(10), -- shoelace changed
sl_avail integer, -- new available value
log_who name, -- who did it
log_when datetime, -- when
);

CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
WHERE NEW.sl_avail != OLD.sl_avail
DO INSERT INTO shoelace_log VALUES (
NEW.sl_name,
NEW.sl_avail,
getpgusername(),
'now'::text
);

However I notice there isn't a column name specification in the DO INSERT
INTO, how would I format the INSERT INTO statement so that log_sequence is
not clobbered? Can I use the normal INSERT into format and specify the
columns? I haven't managed to get it to work that way. Would defining the
sequence at the end of the table help? That would be untidy tho ;).

I haven't used rules yet, but in reviewing the 'CREATE RULE' documentation at

http://www.postgresql.org/docs/postgres/sql-createrule.htm

I believe the 'action' after the 'DO' can be any SQL statement, so you should
be able to name the columns. Am I missing something?

And if the 'serial' type doesn't mainatain a serial order across multiple
clients/users, I'm in deep trouble. :)

Can/should I use now() instead of 'now'::text?

I've been using a default datetime column definition of

log_when datetime default CURRENT_TIMESTAMP

in other similar situations, and that seems to work as you wish (you can then
leave it out of the INSERT statement).

Cheers.
Ed

From bouncefilter Tue Nov 23 11:42:10 1999
Received: from solaris1.mysolution.com (adachi.mysolution.com [216.37.18.104])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA35975
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 11:41:36 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id LAA09213;
Tue, 23 Nov 1999 11:31:47 -0500 (EST)
Message-ID: <003701bf35d2$5074cf20$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: "Jochen Topf" <pgsql-general@mail.remote.org>,
<pgsql-general@postgresql.org>
References: <19991123085929.A2440@eldorado.remote.org>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
Date: Tue, 23 Nov 1999 11:46:09 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

The
: thing is PostgreSQL is extremely reliable if u know what you are doing

and

: know how to handle/get around any bugs.

Sorry, this is simply not true. We are talking about reliability here and
not about some features that might be difficult to find for the

inexperienced

user or something like that. For instance, I had to fight with PostgreSQL

and

Perl to get Notify to work. It might be difficult to get this to work,

because

the lack of documentation or bugs in the way it is implemented, but I got
it to work. This is the thing a beginner stumbles over, and if not

persistent

enough will label as a bug, although it might be only the documentation

that

is buggy, or his level of understanding of the workings of the database is
just not good enough.

But I am not imagining the random "I have rolled back the current

transaction

and am going to terminate your database system connection and exit."

messages.

If there is a way to kill a database as a normal user, it is not reliable.
Maybe, if I knew more about PostgreSQL, I would be able to not trigger the
bugs, but that is not the point. The bugs should not be there or there
should be at least a meaningful error message saying: "I am sorry Dave, I

can't

let you do this, because it would trigger a bug." I have seen random

chrashes

without any indication to the problem and I have seen strange messages
hinting at a problem deep down in a btree implementation or something like
that. And the worst thing is, that these bugs are not repeatable in a way
that someone could start debugging them or at least work around them.

I guess I can see that point :) The ability for a less experienced user or
admin to reasonably do a task in a short amount of time without srewing
things up is more a factor of ease of use than reliability...The ease of
accidentally causing serious harm to the integrity of a database that
requires major repair (foolproofing) is a factor of reliability ;)

and not on disk, in case of a database failure. I thought that this is

enough,

because databases are supposed to be more reliable then simple

filesystems...

No only more flexible ;) Not much is more reliable than a flat file...just
you have to write all the routines to handle multiple users accessing the
file and routines to indeex and find what you are looking for :)

While this is generally true, a huge database can have an impact on
stability. For instance, if you have a very small memory leak, it will not
show in small databases but might show in big ones, triggering a bug. Or
an index grows over some bound and a hash file has to be increased or

whatever.

And there are some problems of this kind in PostgreSQL. I am logging all
logins and logouts from a radius server into PostgreSQL and after it ran
well for several months, it slowed to a crawl and vacuum wouldn't work
anymore. So, yes, I do have a lot of inserts, although about 6000 inserts

day and a total of a few hundert thausend records is not really much.

What version of PostgreSQL did this occur on? And how often were you
running vacuums?

My question of an earlier posting is still not answered. Does anybody

here,

who reported PostgreSQL to be very stable, use advanced features like

pl/pgsql

procedures, triggers, rules and notifies? Lets have a show of hands. I

would

really like to know, why I am the only one having problems. :-) Although
it might be, because, as this is a PostgreSQL mailing list, most of the
readers are people who are happy with PostgreSQL, because all the others
have left and are on an Oracle list now. :-)

:)
In reference to your other posting...if you are experienced enough to
understand the inner workings of PostgreSQL. You are experienced enough to
DBA Oracle yourself ;) Dont waste your money hiring a $100,000 certified
DBA (unless u need the extra help) ;)

From bouncefilter Tue Nov 23 12:27:10 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA42783
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 12:26:27 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11qJhp-000LEEC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Tue, 23 Nov 1999 11:26:17 -0600 (CST)
Date: Tue, 23 Nov 1999 11:26:17 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: Jochen Topf <pgsql-general@mail.remote.org>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
Message-ID: <19991123112617.B18256@wallace.ece.rice.edu>
References: <19991123114857.A3043@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <19991123114857.A3043@eldorado.remote.org>;
from Jochen Topf on Tue, Nov 23, 1999 at 11:48:58AM +0100

On Tue, Nov 23, 1999 at 11:48:58AM +0100, Jochen Topf wrote:

Kaare Rasmussen <kar@webline.dk> wrote:

No I haven't reported them. I have reported a minor bug that I could reproduce
to the bug tracking system. But all the other problems I had, were, as I said,
not reproducable. I tried to come up with a small test case for some of the
bugs and failed. Sure I can report them all, but the developers will tell me,
and rightly so, that they can't do anything with it, because they can't
reproduce it. I know that this is not very helpful, but I know no easy way out
here.

Jochen -
One thing I've noticed following the HACKERS list for a while, is that
the developers are very good at helping turn not-reproducible bugs into
reproducible ones, as well. By that I mean, they can often help narrow
the scope of variables to consider significant, based on the exact error
message, even if it's a rare bug. Sometimes, just knowing a particular
error can be triggered on anyone's system can lead a developer in the
right direction when back-tracing possible execution paths, and often
suggest some simple tests. As I said, I've seen it happen more than
once in the last year. I understand your reticence in reporting bugs
without a simple reproducible test case: it's worthless when contacting
your typical commercial vendor, where your talking to some code tester,
who probably isn't a developer.

Heck, I recently had a case where I submitted a bug, with simple
reproducible case to a commercial vendor. I even diagnosed exactly what
the cause was. When that company got ready to release a new point release,
I was contacted by their QA department, because they couldn't reproduce
the bug, and wanted me to pull their beta, upgrade my working mission
critical system, and see if the bug was still there! Apparently, they
couldn't be bothered to keep an installation of their currently released
product around to test on, but I could be bothered to potentially break
my system for them. Sheesh!

So, in short, report those bugs, even if elusive. At best, the bugs
will get stamped out faster, at worst, you'll point out pontentially
suspicious sections of code to the developers.

Ross

P.S. I noticed you mentioned the 'bug tracking system'. I know that a
web based bug tracker was tried out earlier this year, but was abandoned
in favor of the mailing lists.
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

From bouncefilter Tue Nov 23 12:54:11 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA46106
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 12:53:11 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA05444;
Tue, 23 Nov 1999 12:40:35 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911231740.MAA05444@candle.pha.pa.us>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for ...
In-Reply-To: <3.0.5.32.19991123144516.008ba100@pop.mecomb.po.my> from Lincoln
Yeoh at "Nov 23, 1999 02:45:16 pm"
To: Lincoln Yeoh <lylyeoh@mecomb.com>
Date: Tue, 23 Nov 1999 12:40:35 -0500 (EST)
CC: davidb@vectormath.com, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

At 01:18 AM 23-11-1999 -0500, Bruce Momjian wrote:

If the priorities include stability and reliability, that's what you get.
If the priorities are features at any cost, you get junk.

Though Open Source projects are less susceptible to featuritis, they're far
from immune. Trouble is many PHBs only compare stuff feature by brochure
feature.

We only do 2-3 major releases a year for a reason. If it is not
reliable, it is useless. This is not a computer game.

Yep. Glad to hear that.

Read our development history on our web site. It discusses this.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 23 13:02:10 1999
Received: from guinness.urw.org (root@guinness.urw.org [209.32.194.52])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA47355
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 13:01:57 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from wookimus.net (chewie@wookimus.net [209.32.194.62])
by guinness.urw.org (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id MAA06073;
Tue, 23 Nov 1999 12:01:32 -0600
Date: Tue, 23 Nov 1999 12:01:32 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@guinness.urw.org
To: Fabian.Frederick@prov-liege.be
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Socket file lock
In-Reply-To: <17AB709C82E5D111ACF20000F805F4532B402C@mesadm.epl.prov-liege.be>
Message-ID: <Pine.LNX.4.10.9911231154180.6016-100000@guinness.urw.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 23 Nov 1999 Fabian.Frederick@prov-liege.be wrote:

Sometimes I've got some core socket file in /tmp.However Postgres
leaved correctly in previous shutdown : / What would be the best way
to avoid this. (The big big problem is that postmaster can't be
launched due to that core).

I am not versed in the mannerisms or options of Postgresql quite yet, so
bear with me if there is another more suited approach to this problem.
If you're talking about a /tmp file, you are obviously running this on a
*NIX based system. I use Debian Linux, so my background with the
scripts to launch Postgresql stem from my familiarity with this
distribution, and subsequently the SysV standard for init.d scripts.

To launch Postgresql, I use the script found in /etc/init.d. I have
found it a fairly nominal task to include a 'cleanup()' function in the
init.d script. Something to the effect of:

#!/bin/sh

cleanup() {
for i in /tmp/<insert string match for socket file> ; do
rm -rf ${i}
done
}

This you can include as the first line under each of the case statements
of start, stop, restart, reload, etc...

^chewie

From bouncefilter Tue Nov 23 13:26:11 1999
Received: from mail.remote.org (mail@visby.remote.org [212.227.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA51992
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:25:44 -0500 (EST)
(envelope-from jochen@remote.org)
Received: from localhost by mail.remote.org with local-rmail
id 11qKdK-0005Zo-00; Tue, 23 Nov 1999 19:25:42 +0100
Received: from sqrt by eldorado.remote.org with local (Exim 2.02 #1)
id 11qKWc-0000xA-00
for pgsql-general@postgresql.org; Tue, 23 Nov 1999 19:18:46 +0100
Date: Tue, 23 Nov 1999 19:18:46 +0100
From: Jochen Topf <pgsql-general@mail.remote.org>
To: pgsql-general@postgresql.org
Subject: Re: Is PostgreSQL ready for mission critical applications?
Message-ID: <19991123191845.B3651@eldorado.remote.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: Jochen Topf <jochen@remote.org>

Kane Tao <death@solaris1.mysolution.com> wrote:
:> And there are some problems of this kind in PostgreSQL. I am logging all
:> logins and logouts from a radius server into PostgreSQL and after it ran
:> well for several months, it slowed to a crawl and vacuum wouldn't work
:> anymore. So, yes, I do have a lot of inserts, although about 6000 inserts
:> a day and a total of a few hundert thausend records is not really much.

: What version of PostgreSQL did this occur on? And how often were you
: running vacuums?

6.4.something and 6.5.1. Vacuum runs nightly.

Ross J. Reedstrom <reedstrm@wallace.ece.rice.edu> wrote:
: P.S. I noticed you mentioned the 'bug tracking system'. I know that a
: web based bug tracker was tried out earlier this year, but was abandoned
: in favor of the mailing lists.

I tried reporting it to the mailing list which I found in the documentation
or on the web page somewhere, but it didn't accept my message because I was
not subscribed. I figured that maybe the list was only for internal use
of the developers and the web bug tracking system, so I put it into the
web based system. That was a few month ago. I have no idea whether that was
the right thing to do and what happend to that bug report. It is not easy
to find information about that on the web pages or in the documentation.

Jochen
--
Jochen Topf - jochen@remote.org - http://www.remote.org/jochen/

From bouncefilter Tue Nov 23 13:20:10 1999
Received: from guinness.urw.org (root@guinness.urw.org [209.32.194.52])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA50783
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 13:19:56 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from wookimus.net (chewie@wookimus.net [209.32.194.62])
by guinness.urw.org (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id MAA06117
for <pgsql-general@postgreSQL.org>; Tue, 23 Nov 1999 12:19:53 -0600
Date: Tue, 23 Nov 1999 12:19:53 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@guinness.urw.org
To: pgsql-general@postgreSQL.org
Subject: PL/pgsql or C/C++
Message-ID: <Pine.LNX.4.10.9911231214181.6016-100000@guinness.urw.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

This is a general question expecting general answers. I've read the
documentation concerning triggers and functions, as well as the
documentation on the different languages you can use for driving these
triggers and functions. Aside from portability and the lack of having
to explicitly compiling a C/C++ library, what advantages does PL/pgsql
have over C/C++ or even PL/tcl?

^chewie

From bouncefilter Tue Nov 23 13:30:10 1999
Received: from castle-smtp (firewall-user@ns2.amgen.com [138.133.17.7])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA52605
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:29:41 -0500 (EST) (envelope-from tmark@amgen.com)
Received: by castle-smtp; id KAA19085; Tue, 23 Nov 1999 10:30:09 -0800 (PST)
Received: from imc-exch.amgen.com(138.133.10.75) by castle-smtp.amgen.com via
smap (V4.2) id xma018952; Tue, 23 Nov 99 10:29:44 -0800
Received: by imc-exch.amgen.com with Internet Mail Service (5.5.2650.21)
id <X363DS5L>; Tue, 23 Nov 1999 10:29:02 -0800
Message-ID: <548152BB0AD9D2119C400008C7CFE8C801F12FBB@gold-exch.amgen.com>
From: "Mark, Terry" <tmark@amgen.com>
To: pgsql-general@postgresql.org
Subject: large inserts
Date: Tue, 23 Nov 1999 10:28:50 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

Hi all,
I am trying to do inserts which might get somewhat large. Using Perl and
DBI, I get an error from PGQuery () saying that the query was too large. (I
am presuming this is Postgres' message).

Is it possible to do a large insert *without* using the COPY command ? (I am
having trouble seeing how the pipes would look from within my script and
would prefer not to have to grant super-user status).

thank you for any help,
terry

From bouncefilter Tue Nov 23 13:40:11 1999
Received: from plg2.math.uwaterloo.ca (root@plg2.math.uwaterloo.ca
[129.97.140.200]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA54570
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:39:41 -0500 (EST)
(envelope-from qtu@plg2.math.uwaterloo.ca)
Received: from swag03 (swag03.uwaterloo.ca [129.97.78.8])
by plg2.math.uwaterloo.ca (8.8.8/8.8.8) with SMTP id NAA29386
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:39:37 -0500 (EST)
Message-ID: <000e01bf35e2$5e5d3130$084e6181@uwaterloo.ca>
From: "Qiang (John) Tu" <qtu@plg2.math.uwaterloo.ca>
To: <pgsql-general@postgreSQL.org>
Subject: old releases of PostgreSQL ?
Date: Tue, 23 Nov 1999 13:41:34 -0500
Organization: Department of Computer Science, University of Waterloo
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_000B_01BF35B8.753DC420"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01BF35B8.753DC420
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am a graduate student studying at University of Waterloo. Now I am =
researching on the topic of Software Evolution. PostgreSQL is one of the =
"open source" example I am trying to investigate. My method is to use =
software reverse-engineering and visualization tool to analysis the =
evolution pattern of "open source" project.

I downloaded all the old distributions of postgreSQL source code, but =
failed to find out the following versions:

Release 6.4.1
Release 6.4
Release 6.3.2
Release 6.3.1
Release 6.3
Release v6.0
Release v1.09
=20
I understand Ingres of the grandfather of all IngresII, postgres95 and =
postgreSQL. However, only the last version 8.9 can be founded on the ftp =
sites. I though it could be interesting to include Ingres evolution =
history into my research, in order to investigate the impact of Internet =
collaborate on traditional "open source" project evolution. It will be =
very helpful if you can show me where can I find out all the past =
releases of Ingress prior to version 8.9

------=_NextPart_000_000B_01BF35B8.753DC420
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

evolution pattern of "open source" project.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial>I downloaded all the old distributions of =
postgreSQL=20
source code, but failed to find out the following versions:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial><SPAN style=3D"FONT-FAMILY: 'Courier =
New'">Release=20
6.4.1</SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN style=3D"FONT-FAMILY: 'Courier =
New'"></SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">Release 6.4</SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN style=3D"FONT-FAMILY: 'Courier =
New'"></SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">Release 6.3.2</SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'"></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN style=3D"FONT-FAMILY: 'Courier =
New'">Release=20
6.3.1<?xml:namespace prefix =3D o ns =3D =
"urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Release=20
6.3</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'">Release =
v6.0<o:p></o:p></SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Release=20
v1.09</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN> </DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">I=20
understand Ingres of the grandfather of all IngresII, postgres95 and =
postgreSQL.=20
However, only the last version 8.9 can be founded on the ftp sites. I =
though it=20
could be interesting to include Ingres evolution history into =
my research,=20
in order to investigate the impact of Internet collaborate on =
traditional "open=20
source" project evolution. It will be very helpful if you can show me =
where can=20
I find out all the past releases of Ingress prior to version=20
8.9</SPAN></SPAN></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_000B_01BF35B8.753DC420--

From bouncefilter Tue Nov 23 13:44:11 1999
Received: from plg2.math.uwaterloo.ca (root@plg2.math.uwaterloo.ca
[129.97.140.200]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA55569
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:44:05 -0500 (EST)
(envelope-from qtu@plg2.math.uwaterloo.ca)
Received: from swag03 (swag03.uwaterloo.ca [129.97.78.8])
by plg2.math.uwaterloo.ca (8.8.8/8.8.8) with SMTP id NAA29514
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 13:44:02 -0500 (EST)
Message-ID: <003e01bf35e2$fc5122c0$084e6181@uwaterloo.ca>
From: "Qiang (John) Tu" <qtu@plg2.math.uwaterloo.ca>
To: <pgsql-general@postgresql.org>
Subject: old releases of PostgreSQL ?
Date: Tue, 23 Nov 1999 13:46:00 -0500
Organization: Department of Computer Science, University of Waterloo
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_003B_01BF35B9.136744A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_003B_01BF35B9.136744A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I downloaded all the old distributions of postgreSQL source code, but =
failed to find out the following versions:

------=_NextPart_000_003B_01BF35B9.136744A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_003B_01BF35B9.136744A0--

From bouncefilter Tue Nov 23 22:29:16 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA26999
for <pgsql-general@hub.org>; Tue, 23 Nov 1999 22:28:19 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-110.ocis.net [209.52.175.82])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id TAA25573
for <pgsql-general@hub.org>; Tue, 23 Nov 1999 19:28:17 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <383AE385.D110B8BC@mail.ocis.net>
Date: Tue, 23 Nov 1999 10:57:09 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: GGENERATOR
References: <199911230942.KAA18422@feki.toppoint.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I'm wondering if Pg has anything like an interbase generator? What I'd like to do
is create a trigger that auto numbers a column.

Thanks,
Jason.

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

LINUX!

From bouncefilter Tue Nov 23 14:49:11 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA65470
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 14:48:40 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA10900;
Tue, 23 Nov 1999 14:47:28 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911231947.OAA10900@candle.pha.pa.us>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <19991123112617.B18256@wallace.ece.rice.edu> from "Ross J.
Reedstrom" at "Nov 23, 1999 11:26:17 am"
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
Date: Tue, 23 Nov 1999 14:47:28 -0500 (EST)
CC: Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Jochen -
One thing I've noticed following the HACKERS list for a while, is that
the developers are very good at helping turn not-reproducible bugs into
reproducible ones, as well. By that I mean, they can often help narrow
the scope of variables to consider significant, based on the exact error
message, even if it's a rare bug. Sometimes, just knowing a particular
error can be triggered on anyone's system can lead a developer in the
right direction when back-tracing possible execution paths, and often
suggest some simple tests. As I said, I've seen it happen more than
once in the last year. I understand your reticence in reporting bugs
without a simple reproducible test case: it's worthless when contacting
your typical commercial vendor, where your talking to some code tester,
who probably isn't a developer.

Another thing is that when we hear a few unrepeatable bug reports, we
usually get cracking at finding the cause. Also, sometimes some one
will come along with a reproducable case, and we jump on that case very
quickly because we know others are seeing the problem too.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 23 14:53:11 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA66119
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 14:52:16 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA11032;
Tue, 23 Nov 1999 14:51:26 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911231951.OAA11032@candle.pha.pa.us>
Subject: Re: [GENERAL] old releases of PostgreSQL ?
In-Reply-To: <003e01bf35e2$fc5122c0$084e6181@uwaterloo.ca> from "Qiang (John)
Tu" at "Nov 23, 1999 01:46:00 pm"
To: "Qiang (John) Tu" <qtu@plg2.math.uwaterloo.ca>
Date: Tue, 23 Nov 1999 14:51:26 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

[Charset iso-8859-1 unsupported, filtering to ASCII...]

I am a graduate student studying at University of Waterloo. Now
I am researching on the topic of Software Evolution. PostgreSQL
is one of the "open source" example I am trying to investigate.
My method is to use software reverse-engineering and visualization
tool to analysis the evolution pattern of "open source" project.

I downloaded all the old distributions of postgreSQL source
code, but failed to find out the following versions:

Release 6.4.1 Release 6.4 Release 6.3.2 Release 6.3.1 Release
6.3 Release v6.0 Release v1.09

I understand Ingres of the grandfather of all IngresII, postgres95
and postgreSQL. However, only the last version 8.9 can be founded
on the ftp sites. I though it could be interesting to include
Ingres evolution history into my research, in order to investigate
the impact of Internet collaborate on traditional "open source"
project evolution. It will be very helpful if you can show me
where can I find out all the past releases of Ingress prior to
version 8.9

First, read my development history on the web site and chapter 1
of my book which is also on the documentation page and is very
similar to the developemnt history article.

As far as Ingres history , I couldn't find any real hard information
either except the dates I mention in the article. I do have ingres89
source here as well.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 23 19:55:15 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA03884
for <pgsql-general@postgresql.org>;
Tue, 23 Nov 1999 19:54:57 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:62903 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sCnQo217508>; Wed, 24 Nov 1999 01:54:12 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11qQkh-0000Cb-00; Wed, 24 Nov 1999 01:57:43 +0100
Date: Wed, 24 Nov 1999 01:57:43 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Kane Tao <khtao@yahoo.com>
cc: Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <002d01bf348d$5bbfe900$040101c0@p2400arcane>
Message-ID: <Pine.LNX.4.20.9911231548370.352-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

How about isolating some of these problems and solving them? Or if you
don't have the time/skills to do that, at least develop a detailed plan
how it should work. I am not trying to be arrogant here, but this project
depends on people finding things that annoy them and then fix them. That's
how I ended up here.

In particular documentation issues are more prone to be neglected because
the core developers are of course extremely familiar with everything and
also mostly have other things to do. (No offense to Thomas -- great work.)
It takes no programming skills to update the documenation, and if you
don't know SGML/DocBook, we're here to help.

On 1999-11-21, Kane Tao mentioned:

1) It requires a VERY skilled DBA in both Unix and PostgreSQL

Granted, the installation process receives critique all the time. How
would you like it to work? What parts are too complicated? If they only
*appear* to be so, then this is a documentation deficiency, otherwise we'd
need to think about it.

2) There are few tools that make for ease of development and
administration.

Personally, I am under the impression that there is not a whole lot of
administering to do, which is Good. Regarding ease of development, the
interfaces we offer are IMHO just as good as other DBMS' offer, but we're
not in the business of providing toolkits such as Zope. If less third
parties choose to support us, that sucks, but it's not an argument against
PostgreSQL itself. (cf. "<some_free_os> is inferior because there are no
'productivity' apps available for it")

3) Documentation is no where near as detailed or all encompassing as a
database like Oracle.

Although I usually find what I need, see 2nd paragraph.

4) There are certain instances when the database requires a rebuild from
scratch or tape that are not related to hardware failure or disk corruption.

Huh?

.5) There are no transaction logs or redo logs that allow you to recover
the database to a point in time or handle hot online backups.

Point granted. But it's coming.

6) It does not scale up to multi processor/multi threading very well (As I
understand it).

I don't understand this area too well either, but is there *anything*
below $10000 that scales to multiprocessors well?

7) A vacuum has to be run often (at a regular interval) taking up valuable
system resources...locking tables and sometimes just failing utterly.

Not really. Sunday morning at 4 should suffice unless you run the hottest
thing on the Net.

-Peter

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Nov 23 22:45:16 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA48691
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 22:44:35 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id LAA01123;
Wed, 24 Nov 1999 11:44:33 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma001115; Wed, 24 Nov 99 11:43:57 +0800
Message-Id: <3.0.5.32.19991124114437.008eb660@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Wed, 24 Nov 1999 11:44:37 +0800
To: Ed Loehr <ELOEHR@austin.rr.com>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] logging stuff in the right sequence.
Cc: PostreSQL <pgsql-general@postgreSQL.org>
In-Reply-To: <383AC1C1.4574D9DC@austin.rr.com>
References: <3.0.5.32.19991123165228.008c6820@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:33 AM 23-11-1999 -0600, you wrote:

Lincoln Yeoh wrote:

Hi,

I'm trying to set up logging tables and need a bit of help.

I got it to work - I screwed up somewhere... ;).

And if the 'serial' type doesn't mainatain a serial order across multiple
clients/users, I'm in deep trouble. :)

Actually I meant "is datetime good enough?". It doesn't seem to be, that's
why I'm using a serial as well as datetime.

I tried doing
insert ...;
insert ....;
and when I do the order by datetime it can be the wrong order. Plus the
"order by" resolution only seems to be down to the second. The docs say
datetime resolution is a microsecond, but I haven't figured out how to
display stuff down to that.

When datetime matches the most recently updated record is displayed last.

So if you "order by datetime" it's fine. But if you "order by datetime
desc", you have probs.

If a record is updated it will move to the end.

I've been using a default datetime column definition of

log_when datetime default CURRENT_TIMESTAMP

in other similar situations, and that seems to work as you wish (you can then
leave it out of the INSERT statement).

Hmm what's the recommended way of doing it? Or there are and will always be
many ways of doing this (ala Perl).

I've seen 'now'::text in the FAQ

http://www.postgresql.org/docs/postgres/datatype1019.htm mentions something
like "current", but that doesn't work like 'now'::text works (or
CURRENT_TIMESTAMP).

There's one more thing I'd like in the documentation- for the data types
it'll be good to have the min/max values/sizes for all of them.

For example, it's not obvious what the maximum size a 'text' column can be.
In other places in the docs I read the max row size can be 8K (by default).
So can I assume that the max size for 'text' is limited by that?

Similar for sequence - the default max seq num is about 2^31. But no
mention of what the max "max seq num" can be. I could assume it's actually
an int4. But who knows maybe it's int8.

Cheerio,

Link

From bouncefilter Wed Nov 24 00:25:18 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA75697;
Wed, 24 Nov 1999 00:25:15 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA69309;
Wed, 24 Nov 1999 01:25:01 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 24 Nov 1999 01:25:00 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: marten@feki.toppoint.de
cc: Stephen Birch <sbirch@ironmountainsystems.com>,
pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <199911230942.KAA18422@feki.toppoint.de>
Message-ID: <Pine.BSF.4.10.9911240123270.63896-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 23 Nov 1999 marten@feki.toppoint.de wrote:

a) Due to the database layouts we are in need of doing all these nice
sql-statements like "group by" and "having" ... and as posted earlier
in this group: they're limited in PostgreSQL.

Since I use 'Group By' quite a bit...Having not so much...can you be more
specific on the problems?

b) We had problems with vacuumdb here and there. Some times it cored.
We've deleted a 300 MB database under psql and the backend cored ...

What version of PostgreSQL?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Nov 24 01:47:20 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA85109
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 01:47:09 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id IAA12608; Wed, 24 Nov 1999 08:51:01 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
IAA15166; Wed, 24 Nov 1999 08:47:06 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <383B89EA.564DF1EE@albourne.com>
Date: Wed, 24 Nov 1999 08:47:06 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Jaco de Groot <jaco@gospelsjop.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] drop/rename table and transactions
References: <383962C9.3D739AC9@gospelsjop.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jaco de Groot wrote:

Hi,

Every now and then I get the following error:

cannot write block 0 of tablename [username] blind

If this happens, all my database connections get this error when trying
to access the database and I need to restart postgresql. The problem
causing this error needs to be something like this:

create table table2 (col1 text);
insert into table2 (col1) values ('some data');
begin work;
drop table table1;
alter table table2 rename to table1;
commit;

I've seen the same problem. I found that if I always do a vacuum first,
it does not seem to happen. It is the 'alter table .. rename..' that
causes the problem for me.

BTW, are there any plans to implement the rest of the SQL '92 ALTER
TABLE stuff (deleting columns, changing constraints). I'm conjuring up
SQL to do this for my tables, but it is quite painful -- especially if
you have several indices and a SERIAL type in the table.

Adriaan

From bouncefilter Wed Nov 24 01:51:51 1999
Received: from solaris1.mysolution.com ([216.37.18.102])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA85600
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 01:51:08 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id BAA28285;
Wed, 24 Nov 1999 01:41:17 -0500 (EST)
Message-ID: <005d01bf3648$fd31ae60$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: "Peter Eisentraut" <peter_e@gmx.net>
Cc: "Jochen Topf" <pgsql-general@mail.remote.org>,
<pgsql-general@postgreSQL.org>
References: <Pine.LNX.4.20.9911231548370.352-100000@localhost.localdomain>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Date: Wed, 24 Nov 1999 01:55:39 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

How about isolating some of these problems and solving them? Or if you
don't have the time/skills to do that, at least develop a detailed plan
how it should work. I am not trying to be arrogant here, but this project
depends on people finding things that annoy them and then fix them. That's
how I ended up here.

I have solved all of the problems I have encountered through my light usage
of PostgreSQL. The problems I refer to are problems I read about in here
for example when users say they have corrupt indexes and the suggested
solution is to rebuild all the indexes (which is not easy to do i.e. one
click of the mouse, or a problem that should occur so often)

In particular documentation issues are more prone to be neglected because
the core developers are of course extremely familiar with everything and
also mostly have other things to do. (No offense to Thomas -- great work.)
It takes no programming skills to update the documenation, and if you
don't know SGML/DocBook, we're here to help.

Although I do see this happen all of the time...it still is a deficiency
that makes the database that much harder to learn and use...

1) It requires a VERY skilled DBA in both Unix and PostgreSQL

Granted, the installation process receives critique all the time. How
would you like it to work? What parts are too complicated? If they only
*appear* to be so, then this is a documentation deficiency, otherwise we'd
need to think about it.

I think the concept of user friendly design is universal. There should be
one button in the middle of the screen you push and everything is done for
you :) (refer to technical support if you need to know more :)

2) There are few tools that make for ease of development and
administration.

Personally, I am under the impression that there is not a whole lot of
administering to do, which is Good. Regarding ease of development, the
interfaces we offer are IMHO just as good as other DBMS' offer, but we're
not in the business of providing toolkits such as Zope. If less third
parties choose to support us, that sucks, but it's not an argument against
PostgreSQL itself. (cf. "<some_free_os> is inferior because there are no
'productivity' apps available for it")

Database administration is not just system maintenance. It is also
designing and maintaining tables, stored procedures, triggers etc ...

3) Documentation is no where near as detailed or all encompassing as a
database like Oracle.

Although I usually find what I need, see 2nd paragraph.

I havent been though the documentation in quite a while. But I remember
wanting to know allt he files that were installed for PostgreSQL and where
they were located as well as what each file is used for, how the system was
affected by abnormal shutdowns, a list of all the possible error msgs
generated and the steps to recover/correct the problems, file buffer
optimization, transaction buffer optimization, disk space usage for tables
and indexes and how to calculate them, system tables and what each field
meant and when they were updated, how to turn on system metrics for
transactions, what are the pros and cons of potential backup procedures;how
are they done... Those were just a few questions I had back when. Never
found the answers back then...

4) There are certain instances when the database requires a rebuild

from

scratch or tape that are not related to hardware failure or disk

corruption.

Huh?

Same as before...I have read numerous responses that state that the only way
to resolve a problem is to go to tape backups and restore....I personally
have never had to do it (Thank God)

6) It does not scale up to multi processor/multi threading very well

(As I

understand it).

I don't understand this area too well either, but is there *anything*
below $10000 that scales to multiprocessors well?

Oracle is under $10000 if u dont ask for the unlimited Internet users
version ;)

7) A vacuum has to be run often (at a regular interval) taking up

valuable

system resources...locking tables and sometimes just failing utterly.

Not really. Sunday morning at 4 should suffice unless you run the hottest
thing on the Net.

That brings up the differences in views on what is a mission critical
system. I see it as a 24x7 system that has thousands of transactions daily
in which the system cannot be down in case of emergency for more than 15
minutes and in case of scheduked down time less than 5 minutes if not at
all.

From bouncefilter Wed Nov 24 02:37:20 1999
Received: from rabies.toodarkpark.org (caffeine@rabies.toodarkpark.org
[207.176.94.148]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA91094
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 02:37:18 -0500 (EST)
(envelope-from caffeine@toodarkpark.org)
Received: from localhost (caffeine@localhost)
by rabies.toodarkpark.org (8.8.8/8.8.8/Debian/GNU) with SMTP id
CAA14835; Wed, 24 Nov 1999 02:39:56 -0500
Date: Wed, 24 Nov 1999 07:39:56 +0000 (GMT)
From: Howie <caffeine@toodarkpark.org>
To: marten@feki.toppoint.de
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <199911230942.KAA18422@feki.toppoint.de>
Message-ID: <Pine.LNX.3.96.991124064220.372X-100000@rabies.toodarkpark.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 23 Nov 1999 marten@feki.toppoint.de wrote:

[SNIP]
We've written a PostgreSQL->Smalltalk/X wrapper, now we are developing
a oo->rdmbs framework on top of it and we've noticed the following
problems with PostgreSQL 6.5.1:

wow, people still use Smalltalk ? i had figured that most moved to
Objective-C or Java.

a) Due to the database layouts we are in need of doing all these nice
sql-statements like "group by" and "having" ... and as posted earlier
in this group: they're limited in PostgreSQL.

Now if you need these aggregations urgently you get many, many
problems and you have to produce work-arounds ...

why wouldnt you have 'group by' functionality in the framework layer like
NeXT's Enterprise Objects Framework? isnt the whole point to eliminate (
or nearly eliminate ) the need to key in SQL ?

EOF gives you methods like -[NSArray computeAvgForKey:], -[NSArray
computeCountForKey:], -[NSArray computeMaxForKey:], -[NSArray
computeMinForKey:], and -[NSArray computeSumForKey:]. using, say, 2
methods, one can more than likely get the 'group by' functionality you're
talking about in an OO and RDBMS-independent way. for instance:

- (NSDecimalNumber *)amountBackOrdered
{
EOQualifier *backOrderedQualif =
[[EOKeyValueQualifier alloc] initWithKey:@"isBackOrdered"
operatorSelector:EOQualifierOperatorEqual
value:[NSNumber numberWithBool:YES]];
NSArray *backorders;

backorders =
[[self orders] filteredArrayUsingQualifier:backOrderedQualif];

return [backorders computeSumForKey:@"amount"];
}

( somewhat familiar syntax, eh ? :) )

lookie, no SQL! and, oh, btw, this works if your datastore is a flatfile,
postgresql, oracle, sybase, informix, or that gdbm-ish database.

And this is one reason for all problems running around: as with
all programming languages all these guys come with special SQL
knowledge (e.g. I use these statements very much ...) and now
you come to POstgreSQL and find out, that these statements are
special.

again, isnt the point of OO frameworks on top of non-OO RDBMSs to
eliminate the need to learn 20 vendors' implementations of SQL by
providing an OO 'alternative' ( for lack of a better word ) ?

[SNIP]
b) We had problems with vacuumdb here and there. Some times it cored.
We've deleted a 300 MB database under psql and the backend cored ...

the largest table i have is ~71m and growing somewhat quickly:
-rw------- 1 postgres postgres 71753728 Nov 24 02:06 logins
-rw------- 1 postgres postgres 71761920 Nov 24 02:10 logins

... and ive had absolutely no problems vacuuming it under 6.5.x.

[SNIP]
When considering the fact, that PostgreSQl is a free database it is
worty. Some persons are developing the database and if I
could have a wish: please, please fix all these limitations of
"groub by" and "having" statements and get closer to the sql standard.

www.pgsql.com, make a donation. :)

And to mention, how different the expectations are: some persons out
there mentioned, that referential integrity would be a very urgent need
for them - I've the totally different opinion about this:

When doing procedural queries to the database, this need is ok. If you
put a full oo->rdbms wrapper on top of this database and do your
programming in some oo-languages this need vanishes - because referential
integrity does so much in the background, that your object-model in
your application simply becomes wrong - therefore I throw away
referential integrity. It makes the administration for the databases
also much more simplier.

:) funny you should mention this -- there was a LOT of talk on the
webobjects mailing list about this recently. EOF uses two methods to add
objects to both sides of a relationship ( for back pointers ). these
methods end up calling two other methods in your custom classes. the
discussion was how to add two OTHER methods to front for
-addObject:toBothSidesOfRelationshipWithKey: so one wouldnt have to keep
typing that method ( and getting carpal tunnel syndrome in the process ).

but anyway... throwing RI away isnt all that wise, however. every db with
2+ tables would most likely benefit from keeping the two in sync, be it in
your object model or whatnot. of course, if your RI is in your object
model and object model ONLY, this would most likely present problems for
applications that dont use your framework; there's nothing preventing them
from mucking up your foreign keys. as long as you order your
inserts/deletes/updates properly, one can safely keep RI in the rdbms and
the object model... it get a little tricky when there's a table that
refers back to itself, though.

Just my opinion .. not to be misinterpreted. I encourage every work
the people push into PostgreSQL because I want to have a free
database.

you know, in all honesty, i could care less if the product was free. if
it works, and works well, then ill use it. so far, pgsql has worked
_VERY_ nicely -- so nicely, in fact, that i havent felt the need to move
off to Oracle for my internal dbs.

---
Howie <caffeine@toodarkpark.org> URL: http://www.toodarkpark.org
"Tell a man that there are 400 billion stars and he'll believe you.
Tell him a bench has wet paint and he has to touch it."

From bouncefilter Wed Nov 24 04:07:20 1999
Received: from nereus.informatik.uni-bonn.de (nereus.informatik.uni-bonn.de
[131.220.4.20]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA02749
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 04:06:53 -0500 (EST) (envelope-from elmar@haneke.de)
Received: from localhost (jod.informatik.uni-bonn.de [131.220.9.99])
by nereus.informatik.uni-bonn.de (8.8.8/8.8.8) with ESMTP id JAA17419
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 09:57:43 +0100 (MET)
Received: from Spooler by localhost (Mercury/32 v2.16);
24 Nov 99 10:06:19 +0100
Received: from spooler by haneke.de (Mercury/32 v2.16);
24 Nov 99 09:57:43 +0100
Received: from haneke.de (127.0.0.1) by Haneke Elektronik (Mercury/32 v2.16)
with ESMTP; 24 Nov 99 09:57:39 +0100
Message-ID: <383BA883.DA758425@haneke.de>
Date: Wed, 24 Nov 1999 09:57:39 +0100
From: Elmar Haneke <elmar@haneke.de>
Organization: Haneke
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
References: <Pine.LNX.4.20.9911231548370.352-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Eisentraut wrote:

6) It does not scale up to multi processor/multi threading very well (As I
understand it).

I don't understand this area too well either, but is there *anything*
below $10000 that scales to multiprocessors well?

The only real "deficit" of PostgreSQL in comparison to the "big
Servers" is, that it cannot utilize multiple CPU or disks to process
an single query faster. Servers as Informix or Oracle can split an
single SQL-statement to multiple Jobs done in parallel. PostgreSQL can
only process queries on different connections in parallel. I don't
know if there are any problems with SMP capability but I'm sure that
these should be solvable.

If someone really needs an DBMS capable of splitting single queries to
multiple CPU PostgreSQL is no choice - I don't think that this might
change in the future since there is not much need for such an
extension.

Elmar

From bouncefilter Wed Nov 24 04:47:22 1999
Received: from bbaer.muenster.de (root@bbaer.muenster.de [195.202.32.20])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA05938
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 04:46:29 -0500 (EST)
(envelope-from holger@klawitter.de)
Received: from klawitter.de (holger@mueamb-wan125.citykom.de [195.202.35.125])
by bbaer.muenster.de (8.8.8/8.8.8) with ESMTP id KAA13688
for <pgsql-general@postgreSQL.org>; Wed, 24 Nov 1999 10:46:27 +0100
Sender: holger@muenster.de
Message-ID: <383BAE18.B7F4D49C@klawitter.de>
Date: Wed, 24 Nov 1999 10:21:28 +0100
From: Holger Klawitter <holger@klawitter.de>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.2.11 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-general@postgreSQL.org" <pgsql-general@postgreSQL.org>
Subject: How to do this in Postgres
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks for all the hints I've got!

What I've learned from this question is, that not everything
which seems to be a database problem should be solved using
databases.

(select * from data where <<prio is minimal per id pair>>)

The problem wasn't that there is no statement to get this data,
the problem was the large number of rows. Everything involving
a join of data with itself took plainly too long. Nested
selects only seem to be a syntactical escape.

However, there is one solution (PostgreSQL specific) using the
feature SELECT DISTINCT ON extending the SQL standard. This
select retrieves only the first occurrence obeying the implied order.
However, one has to be distinct on one *single* column.
(Feature request: SELECT DISTINCT ON (id1,id2) ... ):

alter table data add column combined text;
update data set combined = ( id1 || '|' ) || id2;
select
distinct on combined
id1,id2,<<data>>
from data
order by prio

But, the update already takes more than 30 min.

The following perl script (paraphrased) solved the same
problem in 40 sec (not counting "copy into" which I had
to do anyhow):

while( <> ) {
my( $id1, $id2, $prio, $data ) = split( /\t/, $_ );
my( $key ) = "$id1\t$id2";
my( $entry ) = $table{$key};
if( $entry eq "" ) {
$table{$key} = "$prio\t$data";
} else {
my( $oldprio, $junk ) = split( /\t/, $entry );
if( $prio < $oldprio ) {
$table{$key} = "$prio\t$data";
}
}
}
foreach $key (keys %table) {
printf "%s\t%s", $key, $table{$key};
}

Regards,
Holger Klawitter
--
Holger Klawitter +49 (0)251 484 0637
holger@klawitter.de http://www.klawitter.de/

From bouncefilter Wed Nov 24 05:32:21 1999
Received: from nereus.informatik.uni-bonn.de (nereus.informatik.uni-bonn.de
[131.220.5.20]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA12205
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 05:31:38 -0500 (EST)
(envelope-from Elmar.Haneke@gmx.de)
From: Elmar.Haneke@gmx.de
Received: from localhost (jod.informatik.uni-bonn.de [131.220.9.99])
by nereus.informatik.uni-bonn.de (8.8.8/8.8.8) with ESMTP id LAA19870
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 11:22:26 +0100 (MET)
Received: from Spooler by localhost (Mercury/32 v2.16);
24 Nov 99 11:31:38 +0100
Received: from spooler by haneke.de (Mercury/32 v2.16);
24 Nov 99 10:47:49 +0100
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Date: Wed, 24 Nov 1999 10:47:40 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Mailer: Mercury/32 v2.16
Message-ID: <6A57D5543B@haneke.de>

Peter Eisentraut wrote:

6) It does not scale up to multi processor/multi threading very well (As I
understand it).

I don't understand this area too well either, but is there *anything*
below $10000 that scales to multiprocessors well?

Elmar

From bouncefilter Wed Nov 24 05:30:21 1999
Received: from imcwaw2.polkomtel.com.pl (imcwaw2.polkomtel.com.pl
[193.58.70.79]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA11897;
Wed, 24 Nov 1999 05:30:03 -0500 (EST)
(envelope-from andrzej.mazurkiewicz@polkomtel.com.pl)
Received: by imcwaw2.plusnet with Internet Mail Service (5.5.2448.0)
id <X1PPQ1KH>; Wed, 24 Nov 1999 11:29:11 +0100
Message-ID: <13288F4408ADD11186FF0060B06A43130164F9AF@MSGWAW1>
From: Andrzej Mazurkiewicz <andrzej.mazurkiewicz@polkomtel.com.pl>
To: "'marten@feki.toppoint.de'" <marten@feki.toppoint.de>,
sbirch@ironmountainsystems.com
Cc: pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: Referencial integrity - Re: Is PostgreSQL ready for mission criti
calapplications?
Date: Wed, 24 Nov 1999 11:29:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain

Not using reference integrity tools (triggers, constrains) is in log-term a
very dangerous practice.

- you cannot protect your data against by-passing your software simply with
psql;
- the more sophisticated scheme you use the more error prone it is; I am
very sceptical to solutions where somebody says my software is so excelent
that it does not need reference constrains on server basis and I had so many
problems with putting my software working with reference constrains that I
had to remove them. First question that I have is: does that guy really
understand referencial integrity introduced by his software.

Andrzej Mazurkiewicz

-----Original Message-----
From: marten@feki.toppoint.de [SMTP:marten@feki.toppoint.de]
Sent: 23 listopada 1999 10:42
To: sbirch@ironmountainsystems.com
Cc: pgsql-general@postgreSQL.org; pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?

And to mention, how different the expectations are: some persons out
there mentioned, that referential integrity would be a very urgent need
for them - I've the totally different opinion about this:

When doing procedural queries to the database, this need is ok. If you
put a full oo->rdbms wrapper on top of this database and do your
programming in some oo-languages this need vanishes - because referential
integrity does so much in the background, that your object-model in
your application simply becomes wrong - therefore I throw away
referential integrity. It makes the administration for the databases
also much more simplier.

Just my opinion .. not to be misinterpreted. I encourage every work
the people push into PostgreSQL because I want to have a free
database.

Marten

************

From bouncefilter Tue Nov 23 22:05:16 1999
Received: from hotmail.com (f13.law7.hotmail.com [216.33.237.13])
by hub.org (8.9.3/8.9.3) with SMTP id WAA21876
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 22:04:32 -0500 (EST)
(envelope-from workingcm@hotmail.com)
Received: (qmail 23985 invoked by uid 0); 24 Nov 1999 03:04:01 -0000
Message-ID: <19991124030401.23984.qmail@hotmail.com>
Received: from 202.135.119.100 by www.hotmail.com with HTTP;
Tue, 23 Nov 1999 19:04:01 PST
X-Originating-IP: [202.135.119.100]
From: "C.M. Woo." <workingcm@hotmail.com>
To: pgsql-general@postgreSQL.org
Subject:
Date: Wed, 24 Nov 1999 11:04:01 CST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

subscribe
end

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

From bouncefilter Tue Nov 23 22:32:16 1999
Received: from hotmail.com (f134.law7.hotmail.com [216.33.237.134])
by hub.org (8.9.3/8.9.3) with SMTP id WAA29073
for <pgsql-general@postgreSQL.org>;
Tue, 23 Nov 1999 22:31:34 -0500 (EST)
(envelope-from workingcm@hotmail.com)
Received: (qmail 4627 invoked by uid 0); 24 Nov 1999 03:30:59 -0000
Message-ID: <19991124033059.4626.qmail@hotmail.com>
Received: from 192.55.23.50 by www.hotmail.com with HTTP;
Tue, 23 Nov 1999 19:30:59 PST
X-Originating-IP: [192.55.23.50]
From: "C.M. Woo." <workingcm@hotmail.com>
To: pgsql-general@postgreSQL.org
Subject: Installation Problem on Solaris 2.5.1
Date: Wed, 24 Nov 1999 11:30:59 CST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Hi,

When I try to install postgresql 6.5.3 on Solaris 2.5.1, got
following error.

System configure
================
OS : Solaris 2.5.1 (with recommended patches)
flex : 2.5.4a
gcc : 2.95.1
gmake : 3.78.1

Installation Procedure
======================
1) cd postgresql-6.5.3/src
2) ./configure --prefix=/exports/www/postgresql/6.5.3
3) gmake <- have error

Any idea ...

Best regards,
C.M.

====================================================================
c++ -I../../backend -I../../include -I../../interfaces/libpq -I../../include
-I../../backend -Wall -Wmissing-prototypes -fPIC -c -o pglobject.o
pglobject.cc
ar crs libpq++.a pgconnection.o pgdatabase.o pgtransdb.o pgcursordb.o
pglobject.o ranlib libpq++.a ld -G -o libpq++.so.3.0 pgconnection.o
pgdatabase.o pgtransdb.o pgcursordb.o pglobject.o
-L../libpq -lpq -ldl -lsocket -lresolv -lnsl -lm -lc
pgconnection.o: could not read symbols: Bad value
gmake[2]http://www.postgresql.org/docs/programmer/xplang1771.htm: *** [libpq++.so.3.0] Error 1
gmake[2]http://www.postgresql.org/docs/programmer/xplang1771.htm: Leaving directory
`/exports/www/compile/postgresql-6.5.3/src/interfaces/libpq++'
gmake[1]http://www.postgresql.org/docs/programmer/xplang1501.htm: *** [all] Error 2
gmake[1]http://www.postgresql.org/docs/programmer/xplang1501.htm: Leaving directory
`/exports/www/compile/postgresql-6.5.3/src/interfaces'
gmake: *** [all] Error 2
767.0u 230.0s 18:33 89% 0+0k 0+0io 0pf+0w
======================================================================

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

From bouncefilter Wed Nov 24 07:17:22 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA22742
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 07:17:17 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11qbLp-0002DR-00
for pgsql-general@postgresql.org; Wed, 24 Nov 1999 12:16:45 +0000
Date: Wed, 24 Nov 1999 12:16:45 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: pgsql-general@postgresql.org
Subject: Errors compiling 6.5.3
Message-ID: <Pine.BSO.4.10.9911241213350.7921-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

An (admittedly quick) search through the list archives hasn't revealed
anything too similar to this problem, so hopefully someone here can
help....

Have downloaded and unpacked version 6.5.3 of Postgresql to see the
differences between it and my current version (6.5.0). Running the
configure script works fine, but I get the following error when I run
gmake:

storage/SUBSYS.o: Undefined symbol `_TAS' referenced from text segment

which appears in the middle of the following:

gmake[2]http://www.postgresql.org/docs/programmer/xplang1771.htm: Leaving directory
`/amd/service/raid0/home/mark/temp/pgsql/postgresql-6.5.3/src/backend/utils'
gcc -o postgres access/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o
commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o
main/SUBSYS.o parser/SUBSYS.o nodes/SUBSYS.o optimizer/SUBSYS.o
port/SUBSYS.o postmaster/SUBSYS.o regex/SUBSYS.o rewrite/SUBSYS.o
storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o ../utils/version.o -lcompat
-lm -lreadline -ltermcap -lcurses
storage/SUBSYS.o: Undefined symbol `_TAS' referenced from text segment
collect2: ld returned 1 exit status
gmake[1]http://www.postgresql.org/docs/programmer/xplang1501.htm: *** [postgres] Error 1
gmake[1]http://www.postgresql.org/docs/programmer/xplang1501.htm: Leaving directory
`/amd/service/raid0/home/mark/temp/pgsql/postgresql-6.5.3/src/backend'
gmake: *** [all] Error 2

Anyone have any ideas about this? I'm running OpenBSD 2.5.

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Wed Nov 24 08:14:23 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA27463;
Wed, 24 Nov 1999 08:13:29 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id JAA71843;
Wed, 24 Nov 1999 09:12:37 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 24 Nov 1999 09:12:37 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Andrzej Mazurkiewicz <andrzej.mazurkiewicz@polkomtel.com.pl>
cc: "'marten@feki.toppoint.de'" <marten@feki.toppoint.de>,
sbirch@ironmountainsystems.com, pgsql-general@postgreSQL.org,
pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Referencial integrity - Re: Is PostgreSQL ready for
mission criti calapplications?
In-Reply-To: <13288F4408ADD11186FF0060B06A43130164F9AF@MSGWAW1>
Message-ID: <Pine.BSF.4.10.9911240912120.63896-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 24 Nov 1999, Andrzej Mazurkiewicz wrote:

Not using reference integrity tools (triggers, constrains) is in log-term a
very dangerous practice.

Wait, we support both triggers and contraints though...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Nov 24 09:14:24 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA52928
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 09:13:58 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11qdAl-0003GQ-00
for pgsql-general@postgresql.org; Wed, 24 Nov 1999 14:13:27 +0000
Date: Wed, 24 Nov 1999 14:10:05 +0000 (GMT)
From: Mark Jewiss <mark@knowledge.com>
To: psql-general@postgresql.org
Subject: Tidying up vacuums
Message-ID: <Pine.BSO.4.10.9911241406520.7921-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
ReSent-Date: Wed, 24 Nov 1999 14:13:12 +0000 (GMT)
ReSent-From: Mark Jewiss <Mark.Jewiss@knowledge.com>
ReSent-To: pgsql-general@postgresql.org
ReSent-Subject: Tidying up vacuums
ReSent-Message-ID: <Pine.BSO.4.10.9911241413120.7921@office.knowledge.com>

Hello,

Can't see an answer to this in the archives either....

I'm automating the vacuum of each database I have every night using a cron
job on a perl script.

To tidy things up I want to put all of the messages received when
performing the vacuum into a log file, but cannot get this to work.

Each time I vacuum (from either the script or the command line), I see
things like:

DEBUG: --Relation pg_indexes--
DEBUG: Pages 0: Changed 0, Reapped 0, Empty 0, New 0; Tup 0: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail.
Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.

Redirecting STDERR or STDOUT somewhere doesn't seem to have any effect on
these messages.

Any ideas anyone?

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Wed Nov 24 09:26:24 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA54241
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 09:25:42 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11qdM7-0006FE-00
for pgsql-general@postgresql.org; Wed, 24 Nov 1999 14:25:11 +0000
Date: Wed, 24 Nov 1999 14:25:11 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: pgsql-general@postgresql.org
Subject: Cleaning up vacuums
Message-ID: <Pine.BSO.4.10.9911241424121.7921-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

Can't see an answer to this in the archives either....

I'm automating the vacuum of each database I have every night using a cron
job on a perl script.

To tidy things up I want to put all of the messages received when
performing the vacuum into a log file, but cannot get this to work.

Each time I vacuum (from either the script or the command line), I see
things like:

Redirecting STDERR or STDOUT somewhere doesn't seem to have any effect on
these messages.

Any ideas anyone?

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Wed Nov 24 09:43:24 1999
Received: from mailbox.reptiles.org (IDENT:root@mailbox.reptiles.org
[198.96.117.155]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA60580
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 09:43:08 -0500 (EST)
(envelope-from jim@reptiles.org)
Received: from localhost (1819 bytes) by mailbox.reptiles.org
via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp
(sender: <jim>) (ident <jim> using unix)
id <m11qdcz-00080yC@mailbox.reptiles.org>
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 09:42:37 -0500 (EST)
(Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27)
Date: Wed, 24 Nov 1999 09:42:37 -0500
From: Jim Mercer <jim@reptiles.org>
To: Mark Jewiss <Mark.Jewiss@knowledge.com>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Cleaning up vacuums
Message-ID: <19991124094236.O17675@reptiles.org>
References: <Pine.BSO.4.10.9911241424121.7921-100000@office.knowledge.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.BSO.4.10.9911241424121.7921-100000@office.knowledge.com>;
from Mark.Jewiss@knowledge.com on Wed, Nov 24, 1999 at 02:25:11PM
+0000

On Wed, Nov 24, 1999 at 02:25:11PM +0000, Mark Jewiss wrote:

Each time I vacuum (from either the script or the command line), I see
things like:

DEBUG: --Relation pg_indexes--
DEBUG: Pages 0: Changed 0, Reapped 0, Empty 0, New 0; Tup 0: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail.
Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.

Redirecting STDERR or STDOUT somewhere doesn't seem to have any effect on
these messages.

Any ideas anyone?

must be something in your perl script.

i do similar things using /bin/sh scripts as:

psql -h host -d database -c "vacuum verbose;" > errors 2>&1
if [ $? -ne 0 ] ; then
Mail -s "vacuum errors" someone < errors
fi
rm -f errors

works fine.

also, if you enable syslog (include/config.h) and set up a pg_options file,
i've noticed that verbose level 2 will put the output of vacuum into
the syslog file.

--
[ Jim Mercer jim@reptiles.org +1 416 506-0654 ]
[ Reptilian Research -- Longer Life through Colder Blood ]
[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ]

From bouncefilter Wed Nov 24 10:30:32 1999
Received: from mail.elp.rr.com (ns1.elp.rr.com [24.92.96.1])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA66283;
Wed, 24 Nov 1999 10:30:02 -0500 (EST) (envelope-from wim@elp.rr.com)
Received: from elp.rr.com (dt01q0n1b.elp.rr.com [24.92.101.27])
by mail.elp.rr.com (8.9.1/8.9.1) with ESMTP id IAA05674;
Wed, 24 Nov 1999 08:29:31 -0700 (MST)
Message-ID: <383C040E.9A20F470@elp.rr.com>
Date: Wed, 24 Nov 1999 08:28:14 -0700
From: Wim van den Berge <wim@elp.rr.com>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general <pgsql-general@postgreSQL.org>,
pgsql-novice <pgsql-novice@postgreSQL.org>
Subject: Re: [NOVICE] Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
References: <Pine.BSF.4.10.9911240123270.63896-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

You for everybodies information. I'm a relative new user of PostgreSQL.
I've only used the 6.5.3 version, and I've only been using it for about
2 weeks. In that time I have converted all of our legacy data (60+ GB)
divided over 8 databases and several hundred tables to PostgreSQL.

Our users have been using the migrated data for a week now, and I
must say I'm very happy. PostgreSQL has consistantly processed
1,200,000 hits /day. We vacume the databases every night, and
PostgreSQL has yet to fail on me once.

Queries range from simple selects, to more complex queries with group,
having, and sub selects.

I am did have some problems with the more complex datatypes, and
I did have to program around a bug in the Operating System. But that
is due to the fact that I'm bound to SCO Open Server 5.0.5.

Wim

The Hermit Hacker wrote:

On Tue, 23 Nov 1999 marten@feki.toppoint.de wrote:

a) Due to the database layouts we are in need of doing all these nice
sql-statements like "group by" and "having" ... and as posted earlier
in this group: they're limited in PostgreSQL.

Since I use 'Group By' quite a bit...Having not so much...can you be more
specific on the problems?

b) We had problems with vacuumdb here and there. Some times it cored.
We've deleted a 300 MB database under psql and the backend cored ...

What version of PostgreSQL?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

************

From bouncefilter Wed Nov 24 10:12:24 1999
Received: from mailhost.stec.org (mailhost.stec.org [207.181.151.10])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA63981
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 10:12:10 -0500 (EST)
(envelope-from hostmaster@stec.org)
Received: from anaconda.stec.org by mailhost.stec.org with SMTP (Microsoft
Exchange Internet Mail Service Version 5.0.1460.8)
id XNJKBWCR; Wed, 24 Nov 1999 09:07:28 -0600
Sender: root
Message-ID: <383C1075.2F26A077@stec.org>
Date: Wed, 24 Nov 1999 10:21:09 -0600
From: hostmaster <hostmaster@stec.org>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

subscribe
end

From bouncefilter Wed Nov 24 11:31:27 1999
Received: from cask.force9.net (cask.force9.net [195.166.128.29])
by hub.org (8.9.3/8.9.3) with SMTP id LAA74246
for <pgsql-general@hub.org>; Wed, 24 Nov 1999 11:30:32 -0500 (EST)
(envelope-from ian@comodo.net)
Received: (qmail 21185 invoked from network); 24 Nov 1999 16:29:57 -0000
Received: from unknown (HELO techserver.comodo.net) (212.56.123.36)
by cask.force9.net with SMTP; 24 Nov 1999 16:29:57 -0000
Received: from Gromit ([192.168.0.20]) by techserver.comodo.net
with SMTP (Mailtraq/1.1.0.1034) id TCHS5728BC9B4
for pgsql-general@hub.org; Wed, 24 Nov 1999 16:33:05 -0000
From: Ian Phillips <ian@comodo.net>
Reply-To: ian@comodo.net
Organization: Comodo
To: pgsql-general@hub.org
Subject: Re: PL/pgsql or C/C++
Date: Wed, 24 Nov 1999 16:21:57 +0000
X-Mailer: KMail [version 1.0.21]
Content-Type: text/plain
References: <199911240406.XAA60272@hub.org>
MIME-Version: 1.0
Message-Id: <99112416284908.07130@Gromit>
Content-Transfer-Encoding: 8bit
X-Hops: 1

On Wed, 24 Nov 1999, you wrote:

Date: Tue, 23 Nov 1999 12:19:53 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
Subject: PL/pgsql or C/C++

This is a general question expecting general answers. I've read the
documentation concerning triggers and functions, as well as the
documentation on the different languages you can use for driving these
triggers and functions. Aside from portability and the lack of having
to explicitly compiling a C/C++ library, what advantages does PL/pgsql
have over C/C++ or even PL/tcl?

^chewie

Ease of use is probably the biggest plus. For running a 'quick and dirty'
trigger, it's a lot easier than compiling a C library or (in my case) learning
TCL. I suppose if you already know TCL, there isn't that much point.

--
Ian Phillips
ian@comodo.net

"The Z80 - The Chip of the Seventies! Today!"

From bouncefilter Wed Nov 24 11:51:30 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA77018
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 11:51:17 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
LAA26492;
Wed, 24 Nov 1999 11:48:21 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911241648.LAA26492@candle.pha.pa.us>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
In-Reply-To: <005d01bf3648$fd31ae60$040101c0@p2400arcane> from Kane Tao at
"Nov
24, 1999 01:55:39 am"
To: Kane Tao <khtao@yahoo.com>
Date: Wed, 24 Nov 1999 11:48:21 -0500 (EST)
CC: Peter Eisentraut <peter_e@gmx.net>,
Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

would you like it to work? What parts are too complicated? If they only
*appear* to be so, then this is a documentation deficiency, otherwise we'd
need to think about it.

I think the concept of user friendly design is universal. There should be
one button in the middle of the screen you push and everything is done for
you :) (refer to technical support if you need to know more :)

I refer to this as "helmet-ware". The software reads your mind, figures
out what you want it to do, and does it.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Wed Nov 24 11:59:26 1999
Received: from atoll.izhcom.ru (root@atoll.izhcom.ru [213.24.0.1])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA78569;
Wed, 24 Nov 1999 11:58:38 -0500 (EST) (envelope-from bar@izhcom.ru)
Received: from izhcom.ru (titan.izhcom.ru [213.24.0.3])
by atoll.izhcom.ru (8.9.3/8.9.3/Izhcom-V1.0b) with ESMTP id UAA04872;
Wed, 24 Nov 1999 20:59:43 +0400 (SAMT)
Sender: bar@atoll.izhcom.ru
Message-ID: <383C1956.FA067ACB@izhcom.ru>
Date: Wed, 24 Nov 1999 20:59:02 +0400
From: Alexander Barkov <bar@izhcom.ru>
Organization: IZHCOM
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org, pgsql-announce@postgreSQL.org
Subject: ANNOUNCE UdmSearch
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit

ANNOUNCING:

UdmSearch Version 2.1.9

Full featured web search engine

WHAT IT IS:

UdmSearch is free SQL-based full-featured web search engine
software. You can use UdmSearch to build search engine
over HTTP, FTP, NTTP servers as well as over local files.
It supports several famous SQL backends, including PostgreSQL

C CGI, PHP3 and Perl search frontends are included in the package.

WHAT'S NEW ?

Changes in 2.1.9:

* Added Solid support
* Added unixODBC support
* Added PostgreSQL PHP frontend with query language
Porting from MySQL by ZioBudda <michel@michel.enter.it>
* MySQL PHP frontends are not installed by default anymore

WHERE CAN I GET IT ?

Documentation and instructions for downloading and
installing can be found at:

http://mysearch.udm.net/

--
Alexander Barkov
IZHCOM, Izhevsk
email: bar@izhcom.ru | http://www.izhcom.ru
Phone: +7 (3412) 51-55-45 | Fax: +7 (3412) 78-70-10
ICQ: 7748759

From bouncefilter Wed Nov 24 12:27:36 1999
Received: from lord.banki.hu (IDENT:unix@lord.banki.hu [193.225.225.14])
by hub.org (8.9.3/8.9.3) with SMTP id MAA84548
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 12:27:21 -0500 (EST)
(envelope-from chexum@lk8rp.mail.xeon.eu.org)
Received: (qmail 5385 invoked by uid 5002); 24 Nov 1999 17:27:07 -0000
Date: Wed, 24 Nov 1999 18:27:06 +0100
From: Janos Farkas <chexum@shadow.banki.hu>
To: Mark Jewiss <Mark.Jewiss@knowledge.com>
Cc: pgsql-general@postgreSQL.org
Subject: Re: Cleaning up vacuums
Message-ID: <priv$943464344.lord@lk8rp.mail.xeon.eu.org>
References: <Pine.BSO.4.10.9911241424121.7921-100000@office.knowledge.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.2i
In-Reply-To: <Pine.BSO.4.10.9911241424121.7921-100000@office.knowledge.com>;
from Mark Jewiss on Wed, Nov 24, 1999 at 02:25:11PM +0000
Errors-To: Janos Farkas
<Janos.Farkas-sys/priv-#p4/1qlHptaH/-errors@lk8rp.mail.xeon.eu.org>

On 1999-11-24 at 14:25:11, Mark Jewiss wrote:

Each time I vacuum (from either the script or the command line), I see
things like:

DEBUG: --Relation pg_indexes--

I think you see the output from the *backend* itself (on the console/tty
it has been started), which is a child of the postmaster; try
redirecting postmaster when starting it...

Janos

From bouncefilter Wed Nov 24 12:56:37 1999
Received: from www.geocrawler.com (sourceforge.net [209.81.8.17])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA89707
for <pgsql-general@hub.org>; Wed, 24 Nov 1999 12:56:03 -0500 (EST)
(envelope-from nobody@www.geocrawler.com)
Received: (from nobody@localhost)
by www.geocrawler.com (8.9.3/8.9.3) id JAA28689;
Wed, 24 Nov 1999 09:56:04 -0800
Date: Wed, 24 Nov 1999 09:56:04 -0800
Message-Id: <199911241756.JAA28689@www.geocrawler.com>
To: pgsql-general@hub.org
Subject: Help on PL/PGSQL
From: "Santiago Martin-Pascual" <archiver@db.geocrawler.com>
Reply-To: "Santiago Martin-Pascual" <smartin@tdn.es>

This message was sent from Geocrawler.com by "Santiago Martin-Pascual" <smartin@tdn.es>
Be sure to reply to that address.

Where can I get information about PL/PGSQL?

How can I create a function or triger with
PL/PGSQL?

Geocrawler.com - The Knowledge Archive

From bouncefilter Wed Nov 24 13:02:37 1999
Received: from rapture.cyberflunk.com (root@rapture.cyberflunk.com
[199.217.80.1]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA90362
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 13:01:45 -0500 (EST)
(envelope-from nikm@cyberflunk.com)
Received: from localhost (nikm@localhost)
by rapture.cyberflunk.com (8.9.3/8.9.1) with ESMTP id KAA26276
for <pgsql-general@postgreSQL.org>; Wed, 24 Nov 1999 10:01:41 -0800
Date: Wed, 24 Nov 1999 10:01:41 -0800 (PST)
From: Nikos Mouat <nikm@cyberflunk.com>
To: pgsql-general@postgreSQL.org
Subject: FORIEGN KEY's, JOIN's, and others
In-Reply-To: <38206FB0.83237D4A@izhcom.ru>
Message-ID: <Pine.C=64.4.21.9911240950150.25693-100000@rapture.cyberflunk.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,
I've been using Postgres for a while for pretty simple schemas.
I'm now trying to clean things up, and start enforcing data integrity at
the SQL level, rather than the application level. I'm now running into the
following:

NOTICE: CREATE TABLE/FOREIGN KEY clause ignored; not yet implemented
ERROR: JOIN expressions are not yet implemented

Is there a time frame for the addition of these features?
I frequently use OID's to reference entries in other tables, for instance:

CREATE TABLE speeds (
speed varchar
);

CREATE TABLE plans (
name varchar,
def_speed oid,
def_price money
);

now plans.def_speed is simply the oid in speeds. How can I make sure that
when an INSERT is done into plans, the value in def_speed is really an oid
in speeds? How can I stop users from deleting an entry in speeds when that
OID is used in plans.def_speed?

Is there some way to do this that I don't know about? (which I assume to
be likely) - Is REFERENCES or FOREIGN KEY the answer that I'm looking for?

Also, is there a way to create sub tables, ie, something like:

CREATE TABLE cust_notes (
note_date date,
added_by oid,
note varchar
);

CREATE TABLE customers (
customer_name varchar,
notes table cust_notes
);

and then allow me to somehow do:

select note_date,added_by,note from customers.notes where customers.oid =
12345;

I currently do this by doing:

CREATE TABLE cust_notes (
note_date date,
added_by oid,
note varchar,
customer_id oid
);

CREATE TABLE customers (
customer_name varchar,
);

select note_date,added_by,note from cust_notes where customer_id = 12345;

but it seems somehow more logical the other way.

Thanks
nm

From bouncefilter Wed Nov 24 13:47:38 1999
Received: from c004.sfo.cp.net (c004-h006.c004.sfo.cp.net [209.228.14.77])
by hub.org (8.9.3/8.9.3) with SMTP id NAA10538
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 13:47:23 -0500 (EST)
(envelope-from bruce.lowery@edventions.com)
Received: (cpmta 21688 invoked from network); 24 Nov 1999 10:47:21 -0800
Received: from w194.z208176060.chi-il.dsl.cnc.net (HELO edventions.com)
(208.176.60.194)
by smtp.edventions.com with SMTP; 24 Nov 1999 10:47:21 -0800
X-Sent: 24 Nov 1999 18:47:21 GMT
Sender: bruce
Message-ID: <383C32C5.1936A174@edventions.com>
Date: Wed, 24 Nov 1999 12:47:33 -0600
From: Bruce Lowery <bruce.lowery@edventions.com>
Organization: Edventions
X-Mailer: Mozilla 4.51C-Caldera [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: deadlock in 6.4.2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

I've noticed some previous postings about deadlocks in 6.4.2. At the
risk of being irritating, I'd like to ask if anyone has seen this
particular version of the problem: postmaster deadlocks leaving
multiple ZOMBIE children with something like the following in the log
file:

NOTICE: Deadlock detected -- See the lock(l) manual page for a possible
cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible
cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction
ERROR: postmaster: StreamConnection: accept: Too many open files in
system

The suggested (and acceptable) solution seems to be to move to 6.5.x,
but I'd hoped to get confirmation others had seen such - the 'too many
open files' seemed new.

Bruce Lowery
Edventions.com

From bouncefilter Wed Nov 24 17:26:39 1999
Received: from gauss.categoricalsolutions.com.au
(IDENT:root@p24-max52.syd.ihug.com.au [206.17.113.88])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA38200
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 17:26:25 -0500 (EST)
(envelope-from sean@categoricalsolutions.com.au)
Received: from Bernoulli (bernoulli.categoricalsolutions.com.au [192.168.1.3])
by gauss.categoricalsolutions.com.au (8.8.7/8.8.7) with SMTP id
JAA22910
for <pgsql-general@postgresql.org>; Thu, 25 Nov 1999 09:26:18 +1100
From: "Sean Carmody" <sean@categoricalsolutions.com.au>
To: <pgsql-general@postgresql.org>
Subject:
Date: Thu, 25 Nov 1999 09:28:08 +1100
Message-ID: <001101bf36cb$2f456040$0301a8c0@categoricalsolutions.com.au>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0012_01BF3727.62B5D840"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01BF3727.62B5D840
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

subscribe pgsql-general

------=_NextPart_000_0012_01BF3727.62B5D840
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_0012_01BF3727.62B5D840--

From bouncefilter Wed Nov 24 17:42:39 1999
Received: from gauss.categoricalsolutions.com.au
(IDENT:root@p24-max52.syd.ihug.com.au [206.17.113.88])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA40215
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 17:42:00 -0500 (EST)
(envelope-from sean@categoricalsolutions.com.au)
Received: from Bernoulli (bernoulli.categoricalsolutions.com.au [192.168.1.3])
by gauss.categoricalsolutions.com.au (8.8.7/8.8.7) with SMTP id
JAA22921
for <pgsql-general@postgresql.org>; Thu, 25 Nov 1999 09:41:56 +1100
From: "Sean Carmody" <sean@categoricalsolutions.com.au>
To: <pgsql-general@postgresql.org>
Subject:
Date: Thu, 25 Nov 1999 09:43:43 +1100
Message-ID: <001601bf36cd$5c918720$0301a8c0@categoricalsolutions.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal

subscribe pgsql-general

From bouncefilter Wed Nov 24 17:52:45 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id RAA41252
for pgsql-general@postgresql.org; Wed, 24 Nov 1999 17:52:15 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "Dan Sepeur" <dan@tag4tag.com>
X-Newsgroups: comp.databases.postgresql.general
Subject: First Steps
Date: Wed, 24 Nov 1999 23:46:28 +0100
Organization: IS Internet Services GmbH
Lines: 13
Message-ID: <cadmium-81hq6r/INN-2.2.1/ceremonial@broadway.news.is-europe.net>
Reply-To: "Dan Sepeur" <dan@tag4tag.com>
X-Trace: broadway.news.is-europe.net 943483931 2612 195.180.197.9 (24 Nov 1999
22:52:11 GMT)
X-Complaints-To: abuse@netsurf.de
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
To: pgsql-general@postgresql.org

Hello,

does anyone knows, where i can find good documentations to install,
administrate and work with an SQL-Database? I don�t know anything about SQL
and i�m bloody beginner.

Fine was sites or infos in german language.

Thanks

Dan

From bouncefilter Wed Nov 24 18:20:40 1999
Received: from cuaima.ica.luz.ve (vegeta@cuaima.ica.luz.ve [150.185.194.30])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA44064
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 18:19:48 -0500 (EST)
(envelope-from vegeta@cuaima.ica.luz.ve)
Received: from localhost (vegeta@localhost)
by cuaima.ica.luz.ve (8.8.8/8.8.8) with ESMTP id TAA14030
for <pgsql-general@postgresql.org>; Wed, 24 Nov 1999 19:24:24 -0400
Date: Wed, 24 Nov 1999 19:24:24 -0400 (VET)
From: Vegeta <vegeta@cuaima.ica.luz.ve>
To: pgsql-general@postgresql.org
Subject: Postgres ODBC driver and BLOBs
Message-ID: <Pine.LNX.4.05.9911241922070.14027-100000@cuaima.ica.luz.ve>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi list,

Is it posible to read and write BLOBs to a PostgreSQL table using
the PostgreSQL ODBC driver?

Thanks in advance,
Guido Urdaneta

From bouncefilter Wed Nov 24 20:13:41 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA58123
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 20:13:13 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id JAA12073;
Thu, 25 Nov 1999 09:13:11 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma012071; Thu, 25 Nov 99 09:13:04 +0800
Message-Id: <3.0.5.32.19991125091343.008d3da0@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 25 Nov 1999 09:13:43 +0800
To: The Hermit Hacker <scrappy@hub.org>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Hers's one with the COPY command ...
Cc: pgsql-general@postgreSQL.org
In-Reply-To: <Pine.BSF.4.10.9911222102080.14653-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

I assume you are copying batches of data at the same time, so hardcoding in
the datetime wouldn't be a big problem right? Kludgy but should work.

Maybe if you did 'now' it might work. Or force it as 'now'::datetime.

Definitely not an expert- plenty to learn about SQL and Postgres, but since
no one has made any suggestions...

Cheerio,

Link.

At 09:07 PM 22-11-1999 -0400, you wrote:

I have a table created as:

=============
DROP TABLE referer_raw_data;
CREATE TABLE referer_raw_data (
counter_id int4,
referer_url_domain varchar(256),
referer_counter int4,
date_added datetime default now());
=============

I wish to copy a stream of data to it as:

5\thttp://thissite\t3\t...

where the date *isn't* part of the copy, since I want to set it as the
date that the record was added...is this possible? now, from the docs, I
realize that it will ignore the default, which I'm okay with, but is there
a way of passing it now(), or something similar, to set the data?

basically, I want to stream web data to the backend as fast as the backend
will take it, with COPY TO being faster then INSERT INTO, but don't want
to have to "create a date" to insert at the same time...

Marc G. Fournier ICQ#7615664 IRC Nick:

Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

************

From bouncefilter Wed Nov 24 21:20:41 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA66195
for <pgsql-general@postgreSQL.org>;
Wed, 24 Nov 1999 21:20:04 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id KAA12583;
Thu, 25 Nov 1999 10:19:57 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma012580; Thu, 25 Nov 99 10:19:25 +0800
Message-Id: <3.0.5.32.19991125102004.00894d20@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 25 Nov 1999 10:20:04 +0800
To: Bruce Momjian <pgman@candle.pha.pa.us>, Kane Tao <khtao@yahoo.com>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission critical
applications?
Cc: Peter Eisentraut <peter_e@gmx.net>,
Jochen Topf <pgsql-general@mail.remote.org>, pgsql-general@postgreSQL.org
In-Reply-To: <199911241648.LAA26492@candle.pha.pa.us>
References: <005d01bf3648$fd31ae60$040101c0@p2400arcane>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:48 AM 24-11-1999 -0500, Bruce Momjian wrote:

would you like it to work? What parts are too complicated? If they only
*appear* to be so, then this is a documentation deficiency, otherwise

we'd

need to think about it.

I think the concept of user friendly design is universal. There should be
one button in the middle of the screen you push and everything is done for
you :) (refer to technical support if you need to know more :)

I refer to this as "helmet-ware". The software reads your mind, figures
out what you want it to do, and does it.

And halfway you change your mind :).

So it's still not fool proof.

You need futureware. It'll predict what is really wanted and do that
instead ;). In fact it doesn't need MVCC and stuff like that, since it
knows what's going to happen. It'll have an Advanced Multi Universe
Concurrency Control.

Seriously tho. For things to be useful, there will always be a need for
humans to make decisions.

For databases and much software a single "Install Yes/No" is not
satisfactory in sufficient cases to require additional decisions to be made
during installation.

The challenge is to organise the decisions/choices in as optimal a way as
possible. For example: The useful and popular choices are more
accessible/apparent, and the less popular ones don't clutter the others. At
the same time, making them obvious and understandable.

Not easy. Easy to go wrong. If you put only one button, sometimes the
actual choice will be "Remove crappy software? (Yes/No)".

Hey, how about putting this option: "Global Thermonuclear War? (Yes/No)".
Of course that is only if Pg compiled with humour.h included.

Cheerio,

Link.

From bouncefilter Wed Nov 24 21:39:42 1999
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA68360
for <pgsql-general@hub.org>; Wed, 24 Nov 1999 21:39:09 -0500 (EST)
(envelope-from jrh@is.com.fj)
Received: from john (test2.is.com.fj [202.62.124.234])
by homer.is.com.fj (8.9.3/8.9.3) with SMTP id PAA23235
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 15:39:04 +1300 (FJDST)
Message-ID: <002a01bf36f6$42a49400$ea7c3eca@john.is.com.fj>
Reply-To: "John Henderson" <jrh@is.com.fj>
From: "John Henderson" <jrh@is.com.fj>
To: <pgsql-general@hub.org>
Subject: memory management
Date: Thu, 25 Nov 1999 15:36:27 +1200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

Hi folks,
"FATAL 1: palloc failure: memory exhausted" is the error and I have already
checked the FAQ and increased my memory allocation to 64M using limit/ulimit
as recommended.

moe: {2187} % limit
coredumpsize unlimited
cputime unlimited
datasize 131072 kbytes (actually a little bit of overkill)
filesize unlimited
maxproc 64
memorylocked 20916 kbytes
memoryuse 62744 kbytes
openfiles 128
stacksize 8192 kbytes

BSDI reports 64M of RAM available...
Nov 24 17:04:45 moe kernel: BSDI BSD/OS 3.0 Kernel #0: Mon Sep 21 23:32:40
FJT 1998
Nov 24 17:04:45 moe kernel: cpu = Pentium Pro model 3, stepping 4
Nov 24 17:04:45 moe kernel: real mem = 67108864 (64.00 MB)
Nov 24 17:04:45 moe kernel: avail mem = 64069632 (61.10 MB)

Systat|Swap reports 262M of virt memory
Disk 1K-blocks Used /0% /10% /20% /30
sd0b 262140 73536 XXXXXXXXXXXXXX

Top looks like this
load averages: 2.53, 1.63, 1.18
10:38:49
58 processes: 4 running, 54 sleeping
CPU states: 25.8% user, 0.0% nice, 7.1% system, 0.0% interrupt, 67.0%
idle
Memory: Real: 48M/50M Virt: 71M/373M Free: 268K
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
19787 postgres 73 0 52M 39M run 0:14 31.70% 28.37%
postmaster

I am running PostgreSQL 6.4 as -su -c
/usr/local/pgsql/bin/postmaster -i -o -eF

When I tried /usr/local/pgsql/bin/postmaster -i -o -eF -d 6 -B 448
Top gave:
Memory: Real: 45M/50M Virt: 78M/374M Free: 332K

I thought I was making progress but It doesn't really look like it.

So here are the questions...
1) Why is the system running out of memory when there is plenty of virtual
memory available?
2) Is the -B flag going to solve this problem if I can get B high enough?
3) Does anyone have a reference of how to increase shared memory on BSD3.0?
(I know I shouldn't ask here but, gee whiz, I've searched everywhere
including the BSD manual and SysAdmin)

Enough whining,
TIA, JOHN

From bouncefilter Wed Nov 24 23:47:44 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA83397
for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 23:47:43 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp53.kross.klever.net
[209.203.65.53]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id VAA04517 for <pgsql-general@postgresql.org>;
Wed, 24 Nov 1999 21:45:25 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <383CBF6B.993B5847@ironmountainsystems.com>
Date: Wed, 24 Nov 1999 20:47:39 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Table names case sensitive?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Having been suitable impressed by the "PostgreSQL ready for mission
critical apps" thread, I decided to bite the bullet and convert our
database from Interbase to PostgreSQL. Almost immediately I encountered
a puzzling problem. To make things easy, I am using the Borland "data
pump" on an NT machine to copy our data from Interbase to PostgreSQL.

Although the PostgreSQL tables are created correctly, the write
operations are failing. It looks like the ODBC driver is attempting to
create tables with upper case names but PostgreSQL is converting the
names to lower case. When the data pump tries to write data into
PostgreSQL, the writes fail because the tables are not found since their
names are in now lower case.

It looks like PostgreSQL is not consistent with table case conversions.
For the heck of it, I hacked postres.c to convert the the SQL strings to
lower case on the fly - this kluge made the import work correctly.

I have searched the lists and FAQs to see if the table name case
disparity is a common problem, but drew a blank.

The attempted data flow is as follows:

Interbase 4.0 (SuSE 6.1 Linux) ---> Data Pump (NT) ---> PostgreSQL(SuSE
6.1 Linux)

Any suggestions?

Yeah, I know this is a convoluted way to copy data over - if you have
any better ideas, I'm all ears!

Steve

From bouncefilter Thu Nov 25 00:21:44 1999
Received: from solaris1.mysolution.com (mail.mysolution.com [216.37.18.103])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA90824
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 00:21:08 -0500 (EST)
(envelope-from death@solaris1.mysolution.com)
Received: from p2400arcane (miyuki1.mysolution.com [216.37.18.145])
by solaris1.mysolution.com (8.8.5/8.8.5) with SMTP id AAA06668;
Thu, 25 Nov 1999 00:11:10 -0500 (EST)
Message-ID: <000901bf3705$829796c0$040101c0@p2400arcane>
Reply-To: "Kane Tao" <khtao@yahoo.com>
From: "Kane Tao" <death@solaris1.mysolution.com>
To: "Stephen Birch" <sbirch@ironmountainsystems.com>,
<pgsql-general@postgreSQL.org>
References: <383CBF6B.993B5847@ironmountainsystems.com>
Subject: Re: [GENERAL] Table names case sensitive?
Date: Thu, 25 Nov 1999 00:25:08 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Try exporting the tables (including table creation stmts) to a text file and
then ASCII ftping the file to the Unix Server to convert the CRLF and import
using pgsql...The documentation has the commands to import files...

----- Original Message -----
From: Stephen Birch <sbirch@ironmountainsystems.com>
To: <pgsql-general@postgreSQL.org>
Sent: Wednesday, November 24, 1999 11:47 PM
Subject: [GENERAL] Table names case sensitive?

Although the PostgreSQL tables are created correctly, the write
operations are failing. It looks like the ODBC driver is attempting to
create tables with upper case names but PostgreSQL is converting the
names to lower case. When the data pump tries to write data into
PostgreSQL, the writes fail because the tables are not found since their
names are in now lower case.

It looks like PostgreSQL is not consistent with table case conversions.
For the heck of it, I hacked postres.c to convert the the SQL strings to
lower case on the fly - this kluge made the import work correctly.

I have searched the lists and FAQs to see if the table name case
disparity is a common problem, but drew a blank.

The attempted data flow is as follows:

Interbase 4.0 (SuSE 6.1 Linux) ---> Data Pump (NT) ---> PostgreSQL(SuSE
6.1 Linux)

From bouncefilter Thu Nov 25 00:38:44 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA93239
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 00:37:51 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
AAA19996;
Thu, 25 Nov 1999 00:35:40 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911250535.AAA19996@candle.pha.pa.us>
Subject: Re: [GENERAL] Table names case sensitive?
In-Reply-To: <000901bf3705$829796c0$040101c0@p2400arcane> from Kane Tao at
"Nov
25, 1999 00:25:08 am"
To: Kane Tao <khtao@yahoo.com>
Date: Thu, 25 Nov 1999 00:35:40 -0500 (EST)
CC: Stephen Birch <sbirch@ironmountainsystems.com>,
pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Try exporting the tables (including table creation stmts) to a text file and
then ASCII ftping the file to the Unix Server to convert the CRLF and import
using pgsql...The documentation has the commands to import files...

All identifiers are changed to lower case unless they are in
double-quotes. If they use double-quotes in the creates, but not in the
queries, you will have problems.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 25 02:47:48 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA05647
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 02:46:58 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp83.kross.klever.net
[209.203.65.83]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id AAA19084; Thu, 25 Nov 1999 00:44:29 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <383CE962.72F97A07@ironmountainsystems.com>
Date: Wed, 24 Nov 1999 23:46:42 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Kane Tao <khtao@yahoo.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Table names case sensitive?
References: <199911250535.AAA19996@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

That explains it. In fact, the creates do not use double quotes, but the queries
do. I'll have to find a way to fix that.

Steve

All identifiers are changed to lower case unless they are in
double-quotes. If they use double-quotes in the creates, but not in the
queries, you will have problems.

From bouncefilter Thu Nov 25 03:22:48 1999
Received: from main.kenken.ro (IDENT:datab@kenken.dntis.ro [193.226.101.140])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA13014
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 03:22:17 -0500 (EST)
(envelope-from datab@main.kenken.ro)
From: datab@main.kenken.ro
Received: from localhost (datab@localhost)
by main.kenken.ro (8.9.3/8.9.3) with ESMTP id KAA07245
for <pgsql-general@postgreSQL.org>; Thu, 25 Nov 1999 10:21:57 +0200
Date: Thu, 25 Nov 1999 10:21:57 +0200 (EET)
To: pgsql-general@postgreSQL.org
Subject: pg_shadow
In-Reply-To: <1A3EA73969FB@ahorn.sgh.uunet.de>
Message-ID: <Pine.LNX.4.10.9911251004490.7154-100000@main.kenken.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi all!

I create a new user: XXX, and give him superuser rights. When the user
execute: "SELECT * FROM pg_shadow" on local machine, works ok. If
try to execute this select in a JAVA aplication on another machine,
doesn't works. Other selects works ok in JAVA application:
"SELECT * FROM pg_database",
"SELECT * FROM pg_opclass"
What can I do?

Thanks,
radu s.

From bouncefilter Thu Nov 25 04:25:47 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA19737
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 04:25:46 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-114.ocis.net [209.52.175.86])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id BAA12721
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 01:25:43 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <383CFFE0.2BB3C261@mail.ocis.net>
Date: Thu, 25 Nov 1999 01:22:40 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: can I do this.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I'm wondering if I can set a trigger or stored procedure that will run a
perl script?

Thanks,
Jason.

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

The Search for Extraterrestrial Intelligence from Home:
http://setiathome.ssl.berkeley.edu

LINUX!

From bouncefilter Thu Nov 25 21:33:35 1999
Received: from mail.toppoint.de (LaForge.toppoint.de [195.244.243.6])
by hub.org (8.9.3/8.9.3) with SMTP id VAA85044;
Thu, 25 Nov 1999 21:33:15 -0500 (EST)
(envelope-from feki.toppoint.de!marten@toppoint.de)
Received: by mail.toppoint.de (Smail3.1.29.1)
id <m11rBC3-0002K4C>; Fri, 26 Nov 99 03:33 MET
Received: (from marten@localhost)
by feki.phoenix-edv.netzservice.de (8.9.3/8.9.3) id KAA02595;
Thu, 25 Nov 1999 10:43:38 +0100
From: marten@feki.toppoint.de
Message-Id: <199911250943.KAA02595@feki.phoenix-edv.netzservice.de>
Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
criticalapplications?
In-Reply-To: <Pine.BSF.4.10.9911240123270.63896-100000@thelab.hub.org> from
The Hermit Hacker at "Nov 24, 1999 1:25: 0 am"
To: scrappy@hub.org (The Hermit Hacker)
Date: Thu, 25 Nov 1999 10:43:38 +0100 (CET)
Cc: marten@feki.toppoint.de, sbirch@ironmountainsystems.com,
pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL47 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 23 Nov 1999 marten@feki.toppoint.de wrote:

a) Due to the database layouts we are in need of doing all these nice
sql-statements like "group by" and "having" ... and as posted earlier
in this group: they're limited in PostgreSQL.

Since I use 'Group By' quite a bit...Having not so much...can you be more
specific on the problems?

This has been discussed on the e-mail lists (sql) this month several times.
Tom also mentioned the reason for that. If I remember correctly:

The having construct in sub-selects are not interpreted correctly and may
not return the result one hope should be the result.

select * from TABLE-A
where AO IN
(select AO from TABLE-B where ... group by AO having 2<count(*))

Statements like these do NOT work.

They mean: return all rows from table-a if you have at least two rows
on table-b having the identical AO value.

b) We had problems with vacuumdb here and there. Some times it cored.
We've deleted a 300 MB database under psql and the backend cored ...

What version of PostgreSQL?

6.5.1

Marten

From bouncefilter Thu Nov 25 05:13:47 1999
Received: from london-exch.visualgroup.com (LONDON-EXCH.visualgroup.com
[195.171.65.10] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id FAA26028
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 05:13:08 -0500 (EST)
(envelope-from didierg@visualgroup.com)
Received: from visualgroup.com (DIDIER_G [10.7.20.14]) by
london-exch.visualgroup.com with SMTP (Microsoft Exchange
Internet Mail Service Version 5.5.2650.21)
id XABKRC2V; Thu, 25 Nov 1999 10:11:23 -0000
Message-ID: <383D0B4A.CE8BF271@visualgroup.com>
Date: Thu, 25 Nov 1999 10:11:22 +0000
From: Didier Gasser-Morlay <didierg@visualgroup.com>
Organization: Visual Communications Group
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: Completely new and discovering PostGresSql
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi everyone,

I've been using MS Sql Server for the last 4 years on NT and I am quite
fed-up with it.
So I am now seriously considering a move towards LINUX and I investigate
the serious DB offering and PostgreSql Seems to come as a really strong
candidate.

however I have some question, which I hope you will not mind answering :

A. In SQl server I use a LOT of stored procedures which to me are a good
way to isolate the front end from the 'business logic'. In order to use
those Stored procedures one has to be able to create variables, cursors
(even outside a transaction). What would be the equivalent in
PostGresSql ?

B. I have seen a fair amount of projects listed on the Web site, but it
does not say much so my question is are there any heavy users of PG so
far (by heavy I mean db with 150+ tables, 150 users, 3000 insert/update
transactions a day + three times as much Selects) .... and really
business-critical apps.

C. Any good books on PGS ?

D. MS Sql server 6.5 has some stupid limitations such as 16 tables max
in a join, 16 indexes per table, 6 (I believe) levbel of cascading
trigger. I couldnot see any of those limits in PGS but did I overlooked
anything ?

E. I am confused about the NT version of PGS. Does it exists natively or
does it requires support DLLs and libraries to work.

I realize this is quite a heavy set of questions and I thank you in
advance for the time you'll spend answering

Didier Gasser-Morlay

--------------------------------------------------------------------------------------------
Any views or opinions are solely those of the author and do not
necessarily
represent those of Visual Communications Group or its principal
operating
divisions (FPG, Telegraph Colour Library, Planet Earth Pictures,
Colorific!, Pix, Giraudon, Bavaria Bildagentur).
--------------------------------------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which
it is addressed, and may contain confidential and/or privileged
material.
If you are not the intended recipient of this message, please do not
read,
copy, use or disclose this communication; and please notify the sender
immediately. It should be noted that any review, retransmission,
dissemination or other use of, or taking action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited.
--------------------------------------------------------------------------------------------

From bouncefilter Thu Nov 25 05:20:48 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA26777
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 05:19:55 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11qvzn-0005HZ-00; Thu, 25 Nov 1999 10:19:23 +0000
Date: Thu, 25 Nov 1999 10:19:23 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: Janos Farkas <chexum@shadow.banki.hu>
cc: pgsql-general@postgresql.org
Subject: Re: Cleaning up vacuums
In-Reply-To: <priv$943464344.lord@lk8rp.mail.xeon.eu.org>
Message-ID: <Pine.BSO.4.10.9911251018550.886-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

On Wed, 24 Nov 1999, Janos Farkas wrote:

I think you see the output from the *backend* itself (on the console/tty
it has been started), which is a child of the postmaster; try
redirecting postmaster when starting it...

Spot on, thanks for that! ;-)

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Thu Nov 25 06:26:00 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id GAA34869
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 06:25:20 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 15713 invoked by uid 417); 25 Nov 1999 11:17:30 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 25 Nov 1999 11:17:30 -0000
Message-ID: <013e01bf3732$91179ec0$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "Didier Gasser-Morlay" <didierg@visualgroup.com>,
"pgsql-list" <pgsql-general@hub.org>
References: <383D0B4A.CE8BF271@visualgroup.com>
Subject: Re: [GENERAL] Completely new and discovering PostGresSql
Date: Thu, 25 Nov 1999 11:46:20 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Hi everyone,

I've been using MS Sql Server for the last 4 years on NT and I am quite
fed-up with it.
So I am now seriously considering a move towards LINUX and I investigate
the serious DB offering and PostgreSql Seems to come as a really strong
candidate.

however I have some question, which I hope you will not mind answering :

A. In SQl server I use a LOT of stored procedures which to me are a good
way to isolate the front end from the 'business logic'. In order to use
those Stored procedures one has to be able to create variables, cursors
(even outside a transaction). What would be the equivalent in
PostGresSql ?

I'm currently in the progress of moving a company database from Access to
PostgreSQL, and am taking the same approach. PostgreSQL has the ability to
create functions, using variables, it's even possible to use C-code, and if
I'm not
mistaken Perl, although I have only been using native SQL and PLPGSQL
for my functions.

B. I have seen a fair amount of projects listed on the Web site, but it
does not say much so my question is are there any heavy users of PG so
far (by heavy I mean db with 150+ tables, 150 users, 3000 insert/update
transactions a day + three times as much Selects) .... and really
business-critical apps.

For this I'd best point you to a recent discussion on this list, concerning
PostgreSQL and mission-critical-applications, since alot of information
about this
has been discussed in that thread.

C. Any good books on PGS ?

Yep, sort of anyway. There are several documents available on the ftp-sites,
and
an online HTML-guide. I've taken the liberty to make a print-out of the
various
documents (900+ pages in total) and they have been of great help to me.

There is also a work-in-progress for a book to be published in early 2000,
although I don't know the specifics at this point. Since I will have to
check thru my
archives for that.

D. MS Sql server 6.5 has some stupid limitations such as 16 tables max
in a join, 16 indexes per table, 6 (I believe) levbel of cascading
trigger. I couldnot see any of those limits in PGS but did I overlooked
anything ?

I'm not familiar with some of the terms you mention, I have read about some
problems with Joins though, but the View-system is a very good alternative
for
me.

E. I am confused about the NT version of PGS. Does it exists natively or
does it requires support DLLs and libraries to work.

It is my understanding that it is possible to compile the server on NT,
using
a certain library, although I seriously advise against using NT for
mission-critical
applications. Especially since NT tends to crash when there are alot of
connections.
(example: NT news-server crashed and went down for nearly a week, after just
20
simultaneous connections)

I realize this is quite a heavy set of questions and I thank you in
advance for the time you'll spend answering

I just hope that the time i spent answering will one day be spent answering
my questions :)

Didier Gasser-Morlay

Joost Roeleveld

From bouncefilter Thu Nov 25 06:16:51 1999
Received: from genesis.sundayta.co.uk (mail.sundayta.co.uk [212.24.70.227])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA33823
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 06:16:43 -0500 (EST)
(envelope-from david@sundayta.co.uk)
Received: from kings.sundayta.co.uk
([192.168.100.31] helo=sundayta.co.uk ident=david)
by genesis.sundayta.co.uk with esmtp (Exim 3.03 #1 (Debian))
id 11qxVD-0005kq-00; Thu, 25 Nov 1999 11:55:55 +0000
Sender: david
Message-ID: <383D18E9.D4B26910@sundayta.co.uk>
Date: Thu, 25 Nov 1999 11:09:29 +0000
From: David Warnock <david@sundayta.co.uk>
Organization: Sundayta Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Birch <sbirch@ironmountainsystems.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Table names case sensitive?
References: <383CBF6B.993B5847@ironmountainsystems.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephen,

Interesting that you are converting from Interbase. We have now reached
the point where we only use 2 commercial pieces of software. Interbase
and Visual SlickEdit. I would like to drop Interbase but currently we
ship quite a few single user systems running on Win 9x.

We have very good experience so far with Postgresql on internal
projects. We use MySql too but only on systems that are pretty much read
only.

My goal is to migrate onto Postgresql as our only dbms, the developments
over the last year or so have been great and I fully expect to achieve
my goal in the next year or so. As the customers for our product that
uses Interbase are charities we think that Linux and Postgresql (plus
Apache and Jserv later Jakarta) make a great fit.

For our importing we have found that is is sooo much faster to dump the
data into the native format that the postgresql copy expects and then do
the load on the server.

By dumping a table at a time in the text format (new line for each row,
tab between columns, \N for null, \\ for \, and \tab for tab) from your
old system you can be loading in one table while dumping the next. We
have found that copy loads the data soo much faster then anything else
that this is definately worthwhile.

Fortunately this text format is common to mysql and postgresql. On mysql
for example we had an import that used a java program and prepared
statements. It took several days to do the import. Using the copy
method we got this down to a few hours.

We had chosen interbase for 5 reasons

- excellent jdbc support (but the postgresql jdbc support is also
excellent)
- support for unicode (but postgresql can now do this although we have
not yet tried it)
- multi-generational engine (postgresql has this since v6.5)
- platform support - Linux, NT, Win 9x and netware (in fact netware is
no longer really a requirement and so win9x is our only problem and I
expect that we will persuade many off that in the next couple of years)
- pricing for VAR's, interbase is good value (postgresql can't be beat
though :-)

We have recently had a few problems with Interbase on Linux so the
pressure is on them (and they are defiantely not moving ahead as fast as
postgresql is, all the recent versions have been very late and some big
bugs have been left in the field for a long time).

Dave

From bouncefilter Thu Nov 25 07:46:49 1999
Received: from gw.rpa.ryazan.su ([193.125.211.254])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA44282
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 07:46:35 -0500 (EST)
(envelope-from rpa.ryazan.su!sled.rpa.ryazan.su!vovk@gw.rpa.ryazan.su)
Received: from rpa.ryazan.su!sled.rpa.ryazan.su by gw.rpa.ryazan.su with UUCP
id PAA01936; (8.9.3/vak/1.9) Thu, 25 Nov 1999 15:46:54 +0300 (MSK)
Received: from hub.sled.rpa.ryazan.su by rpa.ryazan.su with ESMTP id MAA11239;
(8.8.7/vak/1.9) Thu, 25 Nov 1999 12:34:29 GMT
Received: (from root@localhost)
by hub.sled.rpa.ryazan.su (8.9.3/8.9.3) id PAA02299
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 15:37:37 +0300 (MSK)
Received: from vovk.sled.rpa.ryazan.su(192.168.0.1) by hub.sled.rpa.ryazan.su
via smap (V2.1) id xma002293; Thu, 25 Nov 99 15:37:19 +0300
Message-ID: <001501bf3740$fb989a20$0100a8c0@sled.rpa.ryazan.su>
From: "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
To: <pgsql-general@postgresql.org>
Subject: about speed
Date: Thu, 25 Nov 1999 15:31:22 +0300
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Can any tell my, what will fastly - "SELECT ..." statement or function
doing "SELECT..."?
I do query whith storage procedure in MS SQL, and what about postgresql?

Vovk G. Grigoriy.

From bouncefilter Thu Nov 25 07:38:49 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA43135
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 07:38:15 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1)
id 11qy9l-0000CH-00; Thu, 25 Nov 1999 12:37:49 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11qy9e-0001Vy-00; Thu, 25 Nov 1999 12:37:42 +0000
Subject: Re: [GENERAL] Postgres ODBC driver and BLOBs
To: vegeta@cuaima.ica.luz.ve (Vegeta)
Date: Thu, 25 Nov 1999 12:37:42 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Cc: pgsql-general@postgresql.org
Reply-To: prlw1@cam.ac.uk
In-Reply-To: <Pine.LNX.4.05.9911241922070.14027-100000@cuaima.ica.luz.ve> from
"Vegeta" at Nov 24, 99 07:24:24 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11qy9e-0001Vy-00@quartz.newn.cam.ac.uk>

Vegeta wrote:

Hi list,

Is it posible to read and write BLOBs to a PostgreSQL table using
the PostgreSQL ODBC driver?

Thanks in advance,
Guido Urdaneta

I think this is the bit you may need?

The type used in the driver is simply called "lo" and here is the
command used to create it:

create type lo (
internallength=4, externallength=10,
input=int4in, output=int4out,
default='', passedbyvalue
);

quoted from http://www.insightdist.com/psqlodbc/psqlodbc_faq.html under
"Can I use large objects or OLE?"

Cheers,

Patrick

From bouncefilter Thu Nov 25 08:18:50 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id IAA49178
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 08:18:19 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Panter.DoCS.UU.SE (e99re41@Panter.DoCS.UU.SE [130.238.9.114])
by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP id OAA24900;
Thu, 25 Nov 1999 14:18:13 +0100
Received: from localhost (e99re41@localhost) by Panter.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id OAA16514;
Thu, 25 Nov 1999 14:18:11 +0100
X-Authentication-Warning: Panter.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Thu, 25 Nov 1999 14:18:11 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Didier Gasser-Morlay <didierg@visualgroup.com>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] Completely new and discovering PostGresSql
In-Reply-To: <383D0B4A.CE8BF271@visualgroup.com>
Message-ID: <Pine.GSO.4.02A.9911251410060.16412-100000@Panter.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 25 Nov 1999, Didier Gasser-Morlay wrote:

I've been using MS Sql Server for the last 4 years on NT and I am quite
fed-up with it.
So I am now seriously considering a move towards LINUX and I investigate
the serious DB offering and PostgreSql Seems to come as a really strong
candidate.

Of course some might tell you that we run equally well on FreeBSD, etc. No
reason to jump straight to Linux because it's the anti-MS savior. Just so
you know.

A. In SQl server I use a LOT of stored procedures which to me are a good
way to isolate the front end from the 'business logic'. In order to use
those Stored procedures one has to be able to create variables, cursors
(even outside a transaction). What would be the equivalent in
PostGresSql ?

Btw., it's spelled "PostgreSQL".

Anyway, we have all sorts of functions and procedures as well, but they
don't have the exact same functionality as "stored procedures" in other
DBMS's. I recommend that you look through the archives for stored
procedures, because there are _extended_ discussions taking place every so
often, which might explain the details to you.

B. I have seen a fair amount of projects listed on the Web site, but it
does not say much so my question is are there any heavy users of PG so
far (by heavy I mean db with 150+ tables, 150 users, 3000 insert/update
transactions a day + three times as much Selects) .... and really
business-critical apps.

There also was a thread recently whether PostgreSQL is ready for mission
critical stuff. Look through that. The largest database I know of is about
60GB. There a several people having thousands of tables and thousands of
transactions an hour, so you should be safe there.

C. Any good books on PGS ?

One is currently being written. You can follow the progress on the web
site.

D. MS Sql server 6.5 has some stupid limitations such as 16 tables max
in a join, 16 indexes per table, 6 (I believe) levbel of cascading
trigger. I couldnot see any of those limits in PGS but did I overlooked
anything ?

I'm not aware of them.

E. I am confused about the NT version of PGS. Does it exists natively or
does it requires support DLLs and libraries to work.

Requires Cygnus porting library.

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Thu Nov 25 09:06:50 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id JAA55293
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 09:06:48 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 29760 invoked by uid 417); 25 Nov 1999 14:35:54 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 25 Nov 1999 14:35:54 -0000
Message-ID: <00c001bf374e$47f0bf80$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-list" <pgsql-general@hub.org>
Subject: rule's and trigger's
Date: Thu, 25 Nov 1999 15:01:48 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_008D_01BF3755.FF3D0480"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

This is a multi-part message in MIME format.

------=_NextPart_000_008D_01BF3755.FF3D0480
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I was wondering if anyone knows what's being executed first,=20
a Rule on a view, or a trigger set to 'before <something>' on a view?

Eg. what's executed first? The RULE, or the TRIGGER?

Joost Roeleveld

ps. I hope I'm making sense.....

------=_NextPart_000_008D_01BF3755.FF3D0480
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_008D_01BF3755.FF3D0480--

From bouncefilter Thu Nov 25 19:20:57 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id TAA36137;
Thu, 25 Nov 1999 19:20:02 -0500 (EST) (envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "Reto H." <no_spam_4me_cut_here_retoh@dplanet.ch>
X-Newsgroups: comp.databases.postgresql.general,
comp.databases.postgresql.patches
Subject: bug or feature?
Date: Thu, 25 Nov 1999 17:54:32 +0100
Organization: Internet Access AG, Zuerich, Switzerland
Lines: 11
Message-ID: <81jppq$qu3$1@pacifica.access.ch>
X-Trace: pacifica.access.ch 943549050 27587 195.112.64.253 (25 Nov 1999
16:57:30 GMT)
X-Complaints-To: newsmaster@access.ch
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
To: pgsql-general@postgresql.org.pgsql-patches@postgresql.org

Data type 'ABSTIME' seems to have a kind of Y2K bug

Highest date you can store is Dec 31, 2011

Is there a patch out there?

Thanks for any suggestions.

<Reto> retoh@dplanet.ch

From bouncefilter Thu Nov 25 14:18:54 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA98190
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 14:17:56 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA10118;
Thu, 25 Nov 1999 13:21:19 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911251821.NAA10118@candle.pha.pa.us>
Subject: Re: [GENERAL] Table names case sensitive?
In-Reply-To: <383CE962.72F97A07@ironmountainsystems.com> from Stephen Birch at
"Nov 24, 1999 11:46:42 pm"
To: Stephen Birch <sbirch@ironmountainsystems.com>
Date: Thu, 25 Nov 1999 13:21:19 -0500 (EST)
CC: Kane Tao <khtao@yahoo.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

That explains it. In fact, the creates do not use double quotes,
but the queries do. I'll have to find a way to fix that.

I have seen that before. Quotations either preserve case, or they
don't, but it seems some db's don't honor that.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 25 14:21:54 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA98845
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 14:21:10 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA10182;
Thu, 25 Nov 1999 13:23:48 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911251823.NAA10182@candle.pha.pa.us>
Subject: Re: [GENERAL] Completely new and discovering PostGresSql
In-Reply-To: <383D0B4A.CE8BF271@visualgroup.com> from Didier Gasser-Morlay at
"Nov 25, 1999 10:11:22 am"
To: Didier Gasser-Morlay <didierg@visualgroup.com>
Date: Thu, 25 Nov 1999 13:23:48 -0500 (EST)
CC: pgsql-list <pgsql-general@hub.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

B. I have seen a fair amount of projects listed on the Web site, but it
does not say much so my question is are there any heavy users of PG so
far (by heavy I mean db with 150+ tables, 150 users, 3000 insert/update
transactions a day + three times as much Selects) .... and really
business-critical apps.

That is small for us.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 25 14:21:54 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA98838
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 14:21:08 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA10220;
Thu, 25 Nov 1999 13:25:20 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911251825.NAA10220@candle.pha.pa.us>
Subject: Re: [GENERAL] Completely new and discovering PostGresSql
In-Reply-To: <013e01bf3732$91179ec0$8402a8c0@sentec.demon.nl> from "J.
Roeleveld" at "Nov 25, 1999 11:46:20 am"
To: "J. Roeleveld" <j.roeleveld@softhome.net>
Date: Thu, 25 Nov 1999 13:25:20 -0500 (EST)
CC: Didier Gasser-Morlay <didierg@visualgroup.com>,
pgsql-list <pgsql-general@hub.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

There is also a work-in-progress for a book to be published in early 2000,
although I don't know the specifics at this point. Since I will have to
check thru my
archives for that.

Go to our web site at www.postgresql.org, and look at the FAQ &
Documentation page. That is were you should start. The book is there,
and the documentation is there too.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 25 14:15:54 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA98010
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 14:15:10 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA10262;
Thu, 25 Nov 1999 13:28:28 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911251828.NAA10262@candle.pha.pa.us>
Subject: Re: [GENERAL] Table names case sensitive?
In-Reply-To: <383D18E9.D4B26910@sundayta.co.uk> from David Warnock at "Nov 25,
1999 11:09:29 am"
To: David Warnock <david@sundayta.co.uk>
Date: Thu, 25 Nov 1999 13:28:28 -0500 (EST)
CC: Stephen Birch <sbirch@ironmountainsystems.com>,
pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

We have recently had a few problems with Interbase on Linux so the
pressure is on them (and they are defiantely not moving ahead as fast as
postgresql is, all the recent versions have been very late and some big
bugs have been left in the field for a long time).

Yes, we seem to move at lightning speed compared to commercial
databases and MySQL.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Nov 25 13:45:53 1999
Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA94447
for <pgsql-general@postgresql.org>;
Thu, 25 Nov 1999 13:44:58 -0500 (EST)
(envelope-from moray.mcconnachie@computing-services.oxford.ac.uk)
Received: from ermine.ox.ac.uk ([163.1.2.13])
by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 11r3t2-0002jY-00
for pgsql-general@postgresql.org; Thu, 25 Nov 1999 18:44:56 +0000
Received: from ermine.ox.ac.uk ([163.1.2.13] helo=moraypc ident=root)
by ermine.ox.ac.uk with smtp (Exim 2.12 #1) id 11r3t2-00071E-00
for pgsql-general@postgreSQL.org; Thu, 25 Nov 1999 18:44:56 +0000
Message-ID: <003e01bf3775$2a3faa60$760e01a3@oucs.ox.ac.uk>
From: "Moray McConnachie" <moray.mcconnachie@computing-services.oxford.ac.uk>
To: <pgsql-general@postgresql.org>
Subject: problems on INSERTS via ODBC?
Date: Thu, 25 Nov 1999 18:44:54 -0000
Organization: Oxford University
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_003B_01BF3775.29FAD930"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_003B_01BF3775.29FAD930
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

6.5.3 running on RedHat Linux 6.0. Front-end running on MS Access 2000
over ODBC on WinNT

I have recently been experiencing some worrying problems whereby an
"INSERT INTO..." query executed in Access succeeds to all appearances.
Opening the linked table or querying it from Access shows that the
records are present. However, on the server itself these records are
not there, nor are they there if you quit Access and enter it again.

I have debug logs to level 2 off the server, and the psql odbc driver
log. I'm trying to understand them to work out if it was my query
which was somehow causing the problem. I'm not very conscious of where
the responsibility is under ODBC connections to report problems, with
the server, or with the driver.

I think I have solved the problems by dropping all indices, rebuilding
them, and redesigning the problematic queries. (One of the functions
in one had an incorrectly specified parameter - however, Access did
not complain while building the insert, and the final insert looks
correct).

I am worried as to whether this might happen again, and worried that
it could happen at all. I don't know whether the problem is in the
client, the server, or the ODBC driver, but the trouble about this
kind of error is that it is the worst type - records apparently being
inserted correctly, but in fact not being so.

I attach a part of the server log - the inserts seem to be being done
on a one-by-one basis, and the partial log attached contains all
references to one of them. Could someone maybe take a look, and see if
what is recorded in these logs explains the behaviour? It seems
particularly odd, because the final insert appears to have nothing
wrong with it!

Yours,
Moray McConnachie

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk

------=_NextPart_000_003B_01BF3775.29FAD930
Content-Type: text/plain;
name="oneproc.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="oneproc.txt"

postmaster: BackendStartup: pid 774 user moray db maint socket 5
postmaster child[774]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1340
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "regno" ,"typeid" ,"internalid" FROM "internalprphs" WHERE =
("regno" =3D 6229 )=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 774 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 775 user moray db maint socket 5
postmaster child[775]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1341
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "typeid" FROM "machines" WHERE ("regno" =3D 6229 )=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 775 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 776 user moray db maint socket 5
postmaster child[776]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1342
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "price" FROM "prices" WHERE ((("typeid" =3D 6 ) AND =
("subsidyid" =3D 'v' ) ) AND ("validfrom" <=3D '2000-11-30' ) ) ORDER BY =
"prices"."validfrom" DESC=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 776 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 777 user moray db maint socket 5
postmaster child[777]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1343
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "generictypeid" FROM "types" WHERE ("typeid" =3D 6 )=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 777 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 778 user moray db maint socket 5
postmaster child[778]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1344
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "generictype" FROM "subsettypes" WHERE ("generictypeid" =
=3D 0 )=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 778 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 779 user moray db maint socket 5
postmaster child[779]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1345
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "regno" ,"ramsize" ,"hdsize" ,"screensize" FROM "machines" =
WHERE ("regno" =3D 6229 )=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 779 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 780 user moray db maint socket 5
postmaster child[780]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1346
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "name" ,"subsidyid" ,"price" ,"unit" ,"base" ,"validfrom" =
,"priceconstid" FROM "priceconstants" WHERE ((("name" LIKE 'RAM%' ) AND =
("subsidyid" =3D 'v' ) ) AND ("validfrom" <=3D '2000-11-30' ) ) ORDER BY =
"priceconstants"."validfrom" DESC=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 780 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 781 user moray db maint socket 5
postmaster child[781]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1347
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "name" ,"subsidyid" ,"price" ,"unit" ,"base" ,"validfrom" =
,"priceconstid" FROM "priceconstants" WHERE ((("name" LIKE 'HD%' ) AND =
("subsidyid" =3D 'v' ) ) AND ("validfrom" <=3D '2000-11-30' ) ) ORDER BY =
"priceconstants"."validfrom" DESC=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 781 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 782 user moray db maint socket 5
postmaster child[782]: starting with (/usr/local/pgsql/bin/postgres -d2 =
-e -v131072 -p maint )
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
debug info:
User =3D moray
RemoteHost =3D a.b.c.d
RemotePort =3D 1348
DatabaseName =3D maint
Verbose =3D 2
Noversion =3D f
timings =3D f
dates =3D European
bufsize =3D 64
sortmem =3D 512
query echo =3D f
InitPostgres
StartTransactionCommand
query: set DateStyle to 'ISO'
ProcessUtility: set DateStyle to 'ISO'
CommitTransactionCommand
StartTransactionCommand
query: set ksqo to 'ON'
ProcessUtility: set ksqo to 'ON'
CommitTransactionCommand
StartTransactionCommand
query: select oid from pg_type where typname=3D'lo'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SELECT "price" FROM "pricescreens" WHERE ((("size" >=3D 0 ) AND =
("subsidyid" =3D 'v' ) ) AND ("validfrom" <=3D '2000-11-30' ) ) ORDER BY =
"pricescreens"."validfrom" DESC,"pricescreens"."size"=20
ProcessQuery
CommitTransactionCommand
pq_recvbuf: unexpected EOF on client connection
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
StartTransactionCommand
query: INSERT INTO "invoicedebits" =
("regno","accountid","debitdate","amount","genre") VALUES =
(6229,1700,'1999-12-01',23.830000,'renew')
ProcessQuery
CommitTransactionCommand
postmaster: reaping dead processes...
postmaster: CleanupProc: pid 782 exited with status 0
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling reading 5
postmaster: ServerLoop: handling writing 5
postmaster: BackendStartup: pid 783 user moray db maint socket 5

------=_NextPart_000_003B_01BF3775.29FAD930--

From bouncefilter Thu Nov 25 15:23:55 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA08816;
Thu, 25 Nov 1999 15:23:00 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com (ppp84.kross.klever.net
[209.203.65.84]) by onestone.elsinore.klever.net (8.8.7/8.8.0)
with ESMTP id NAA19153; Thu, 25 Nov 1999 13:20:16 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <383D9A8B.EFBAB14C@ironmountainsystems.com>
Date: Thu, 25 Nov 1999 12:22:35 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: Andrzej Mazurkiewicz <andrzej.mazurkiewicz@polkomtel.com.pl>,
"'marten@feki.toppoint.de'" <marten@feki.toppoint.de>,
pgsql-general@postgreSQL.org, pgsql-novice@postgreSQL.org
Subject: Re: [GENERAL] Referencial integrity - Re: Is PostgreSQL ready
formission criti calapplications?
References: <Pine.BSF.4.10.9911240912120.63896-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

How is the referential integrety project progressing?

Any time soon?

Steve

The Hermit Hacker wrote:

On Wed, 24 Nov 1999, Andrzej Mazurkiewicz wrote:

Not using reference integrity tools (triggers, constrains) is in log-term a
very dangerous practice.

Wait, we support both triggers and contraints though...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

************

From bouncefilter Thu Nov 25 15:31:55 1999
Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA10299
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 15:31:47 -0500 (EST)
(envelope-from jaco@gospelsjop.com)
Received: from gospelsjop.com ([212.83.89.116]) by relay02.chello.nl
(InterMail v4.01.00 201-232-112) with ESMTP
id <19991125203053.EHRS25963.relay02@gospelsjop.com>
for <pgsql-general@postgreSQL.org>; Thu, 25 Nov 1999 21:30:53 +0100
Sender: jaco
Message-ID: <383D9DB0.E2A54358@gospelsjop.com>
Date: Thu, 25 Nov 1999 21:36:01 +0100
From: Jaco de Groot <jaco@gospelsjop.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i486)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: drop/rename table and transactions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Every now and then I get the following error:

cannot write block 0 of tablename [username] blind

If this happens, all my database connections get this error when trying
to access the database and I need to restart postgresql. The problem
causing this error needs to be something like this:

create table table2 (col1 text);
insert into table2 (col1) values ('some data');
begin work;
drop table table1;
alter table table2 rename to table1;
commit;

Trying some statements I found an other error, using these statements:

create table table1 (col1 text);
begin work;
drop table table1;
alter table table2 rename to table1;
create table table2 (col1 text);
commit;
select * from table1;

Caused:

couldn't open table1: No such file or directory

I'm using postgresql-6.5.2-1.i386.rpm.

Is the posgresql development team aware of these errors and will
they be fixed?

Gr. Jaco

From bouncefilter Thu Nov 25 16:48:56 1999
Received: from ns1.aprofile.com (h139-142-54-194.ed.fiberone.net
[139.142.54.194]) by hub.org (8.9.3/8.9.3) with SMTP id QAA18553
for <pgsql-general@hub.org>; Thu, 25 Nov 1999 16:48:33 -0500 (EST)
(envelope-from darvin.zuch@autoprofile.com)
Received: (qmail 33949 invoked from network); 25 Nov 1999 21:46:12 -0000
Received: from h139-142-54-195.ed.fiberone.net (HELO zuchdarvinjava)
(139.142.54.195)
by h139-142-54-194.ed.fiberone.net with SMTP; 25 Nov 1999 21:46:12 -0000
From: "Darvin Zuch" <darvin.zuch@autoprofile.com>
To: "'J. Roeleveld'" <j.roeleveld@softhome.net>,
"'Didier Gasser-Morlay'" <didierg@visualgroup.com>,
"'pgsql-list'" <pgsql-general@hub.org>
Subject: RE: [GENERAL] Completely new and discovering PostGresSql
Date: Thu, 25 Nov 1999 14:53:02 -0700
Message-ID: <000601bf378f$72e7ad20$0ddba8c0@zuchdarvinjava.aprofile.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <013e01bf3732$91179ec0$8402a8c0@sentec.demon.nl>

I'm in the midst of Switching form SQL Server 6.5 to PostgreSQL. After
looking at the Procedural Languages in PostgreSQL and the apparent steep
learning curve I opted to segment my business logic into Java Object which
are very Web / Webserver freindly. I'm running with > 2GB of data and
several hundred TSQL stored procedures.
This allows me to easily switch to easily switch to a higher performance DB
engine (like Oracle) in the future with out such a long conversion period or
learning time. Java Objects can be made into .DLL's for C integration.

You might want to consider the same.

Darvin Zuch
AutoProfile - Canda

-----Original Message-----
From: owner-pgsql-general@postgreSQL.org
[mailto:owner-pgsql-general@postgreSQL.org]On Behalf Of J. Roeleveld
Sent: Thursday, November 25, 1999 3:46 AM
To: Didier Gasser-Morlay; pgsql-list
Subject: Re: [GENERAL] Completely new and discovering PostGresSql

Hi everyone,

I've been using MS Sql Server for the last 4 years on NT and I am quite
fed-up with it.
So I am now seriously considering a move towards LINUX and I investigate
the serious DB offering and PostgreSql Seems to come as a really strong
candidate.

however I have some question, which I hope you will not mind answering :

A. In SQl server I use a LOT of stored procedures which to me are a good
way to isolate the front end from the 'business logic'. In order to use
those Stored procedures one has to be able to create variables, cursors
(even outside a transaction). What would be the equivalent in
PostGresSql ?

B. I have seen a fair amount of projects listed on the Web site, but it
does not say much so my question is are there any heavy users of PG so
far (by heavy I mean db with 150+ tables, 150 users, 3000 insert/update
transactions a day + three times as much Selects) .... and really
business-critical apps.

For this I'd best point you to a recent discussion on this list, concerning
PostgreSQL and mission-critical-applications, since alot of information
about this
has been discussed in that thread.

C. Any good books on PGS ?

There is also a work-in-progress for a book to be published in early 2000,
although I don't know the specifics at this point. Since I will have to
check thru my
archives for that.

D. MS Sql server 6.5 has some stupid limitations such as 16 tables max
in a join, 16 indexes per table, 6 (I believe) levbel of cascading
trigger. I couldnot see any of those limits in PGS but did I overlooked
anything ?

I'm not familiar with some of the terms you mention, I have read about some
problems with Joins though, but the View-system is a very good alternative
for
me.

E. I am confused about the NT version of PGS. Does it exists natively or
does it requires support DLLs and libraries to work.

I realize this is quite a heavy set of questions and I thank you in
advance for the time you'll spend answering

I just hope that the time i spent answering will one day be spent answering
my questions :)

Didier Gasser-Morlay

Joost Roeleveld

************

From bouncefilter Thu Nov 25 17:04:56 1999
Received: from wolfheim.wookimus.net (root@wolfheim.wookimus.net
[209.98.23.191]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA20763
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 17:04:37 -0500 (EST)
(envelope-from chewie@wookimus.net)
From: chewie@wookimus.net
Received: from wookimus.net (chewie@localhost [127.0.0.1])
by wolfheim.wookimus.net (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id
QAA06239; Thu, 25 Nov 1999 16:01:50 -0600
Message-Id: <199911252201.QAA06239@wolfheim.wookimus.net>
X-Authentication-Warning: wolfheim.wookimus.net: Host chewie@localhost
[127.0.0.1] claimed to be wookimus.net
To: "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
Cc: pgsql-general@postgreSQL.org, chewie@wolfheim.wookimus.net
Subject: Stored Procedures/Functions (was [GENERAL] about speed)
In-Reply-To: Message from "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
of "Thu, 25 Nov 1999 15:31:22 +0300."
<001501bf3740$fb989a20$0100a8c0@sled.rpa.ryazan.su>
References: <001501bf3740$fb989a20$0100a8c0@sled.rpa.ryazan.su>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1830262945P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 25 Nov 1999 16:01:49 -0600

--==_Exmh_-1830262945P
Content-Type: text/plain; charset=us-ascii

("[n]" denotes a footnote.)

Vovk!

I believe your question was directed toward finding an equivalent to
Micro$oft's Stored Proceedures, correct? In short, yes, Postgresql does
have an equivalent to M$'s stored procedures. Micro$oft cooked up a
procedural language called TSQL. Postgresql has a number of options
where Microsoft only had one. With Postgresql, you can use the PL that
is packaged with the engine called PL/pgSQL [1]http://www.postgresql.org/docs/programmer/xplang1501.htm. If you know Tcl, you
can use PL/Tcl [2]http://www.postgresql.org/docs/programmer/xplang1771.htm. And if you feel real adventurous and would like to
use functions and triggers written using programming language functions
in C or C++ rather than procedural (interpreted) language functions, you
can use the libpg library or the esql library (embedded SQL). Just
check out the Programmer's Manual in the documentation [3]http://www.postgresql.org/docs/programmer/index.html.

I couldn't comment on the speed of things, as I haven't yet tried any of
these methods (it's only a matter of time -- a very short time -- before
I do, though.) I do understand that PL/pgSQL was created with the same
byte-compiling methods that TSQL was. Here's a little snippet from the
PL/pgSQL section of the Programmer's Manual[1]http://www.postgresql.org/docs/programmer/xplang1501.htm:

For all expressions and SQL statements used in the function, the
PL/pgSQL bytecode interpreter creates a prepared execution plan
using the SPI managers SPI_prepare() and SPI_saveplan()
functions. This is done the first time, the individual statement
is processed in the PL/pgSQL function. Thus, a function with
conditional code that contains many statements for which
execution plans would be required, will only prepare and save
those plans that are really used during the entire lifetime of
the database connection.

This looks VERY similar to M$SQL Server's stored procedure
implementation. I looked at the differences between the two languages,
and I don't think there are too many that they cannot be overcome with a
little familiarity. In fact, I think there is more logic to the
PL/pgSQL language than TSQL. Take for example how you assign variables.

In TSQL you must use the following statement:

SELECT @<identifier>=<expression>

Now, doesn't that seem a bit odd? Using the SELECT statement to assign
values to identifiers is certainly a way to confuse the programmer, and
I'm willing to bet that such use of the SELECT statement is not SQL92
compliant. (see question about standards below, please)

In PL/pgSQL you use the following:

And that looks like just a small sample of the language. I'm getting
very anxious to try a bit more. ;-)

Oh, and now on to my question: where can one find an on-line copy of
these often quoted standards, such as SQL92, SQL3, etc?

Chad

Footnotes:
-----------------------------------------------------------------------
[1]: http://www.postgresql.org/docs/programmer/xplang1501.htm
[2]: http://www.postgresql.org/docs/programmer/xplang1771.htm
[3]: http://www.postgresql.org/docs/programmer/index.html

--------------------------------------------------------------------------
Chad Walstrom mailto:chewie@wookimus.net
a.k.a ^chewie, gunnarr http://wookimus.net/~chewie

Gnupg fingerprint = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
--------------------------------------------------------------------------

--==_Exmh_-1830262945P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

("[n]" denotes a footnote.)

Vovk!

In TSQL you must use the following statement:

SELECT @<identifier>=<expression>

In PL/pgSQL you use the following:

And that looks like just a small sample of the language. I'm getting
very anxious to try a bit more. ;-)

Oh, and now on to my question: where can one find an on-line copy of
these often quoted standards, such as SQL92, SQL3, etc?

Chad

Footnotes:
- -----------------------------------------------------------------------
[1]: http://www.postgresql.org/docs/programmer/xplang1501.htm
[2]: http://www.postgresql.org/docs/programmer/xplang1771.htm
[3]: http://www.postgresql.org/docs/programmer/index.html

- --------------------------------------------------------------------------
Chad Walstrom mailto:chewie@wookimus.net
a.k.a ^chewie, gunnarr http://wookimus.net/~chewie

Gnupg fingerprint = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
- --------------------------------------------------------------------------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 (debian)

iD8DBQE4PbHNDMcLGCBsWv0RAjBdAJ9Eqhg0+JnbVUZyciJ823QquTRxUgCfXwW2
B6JXXyEKTnHgb4cCLvqWolo=
=b6Fc
-----END PGP SIGNATURE-----

--==_Exmh_-1830262945P--

From bouncefilter Fri Nov 26 00:27:02 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA13885
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 00:26:24 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id AAA30121;
Fri, 26 Nov 1999 00:23:50 -0500
Sender: mascarm@mascari.com
Message-ID: <383DD367.F0AB3B2C@mascari.com>
Date: Thu, 25 Nov 1999 19:25:11 -0500
From: Mike Mascari <mascarm@mascari.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] drop/rename table and transactions
References: <3.0.5.32.19991126090804.008af890@pop.mecomb.po.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lincoln Yeoh wrote:

If this happens, all my database connections get this error when trying
to access the database and I need to restart postgresql. The problem
causing this error needs to be something like this:

create table table2 (col1 text);
insert into table2 (col1) values ('some data');
begin work;
drop table table1;
alter table table2 rename to table1;
commit;

I did what I did coz I was curious. But creating/Dropping tables in a
transaction does not appear to be a "good thing", and that's not just for
PostgreSQL. I believe doing data definition stuff in transactions is not
recommended.

Is it possible to achieve your goals by using things like
"delete * from table1 where id!=stuffIwant" instead of dropping it?

Cheerio,

Link.

This is one of the few areas that I disagree with the development trend in
PostgreSQL. Every release contains different bugs related to DDL statements in
transactions. The developers appear to want to make them work (i.e., have the
ability to rollback a DROP TABLE, ALTER TABLE ADD COLUMN, etc.). This, in my
opinion, goes far above and beyond the call of duty for a RDBMS. Oracle issues
an implicit COMMIT whenever a DDL statement is found. In fact, one could argue
that those who are porting Oracle apps to PostgreSQL would assume,
incorrectly, than a DROP TABLE in a transaction committed any work done
previously.

I personally believe that PostgreSQL should do the same as Oracle and greatly
simplify the implementation of DDL statements in the backed by issuing an
implicit COMMIT....

Just my opinion, though

Mike Mascari

From bouncefilter Thu Nov 25 20:08:13 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA43086
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 20:07:39 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id JAA22670;
Fri, 26 Nov 1999 09:07:34 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma022664; Fri, 26 Nov 99 09:07:25 +0800
Message-Id: <3.0.5.32.19991126090804.008af890@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Fri, 26 Nov 1999 09:08:04 +0800
To: Jaco de Groot <jaco@gospelsjop.com>, pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <383D9DB0.E2A54358@gospelsjop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

If this happens, all my database connections get this error when trying
to access the database and I need to restart postgresql. The problem
causing this error needs to be something like this:

create table table2 (col1 text);
insert into table2 (col1) values ('some data');
begin work;
drop table table1;
alter table table2 rename to table1;
commit;

What happens if two different connections try to "drop table table1"? Try
doing it step by step in two different connections?

I did a vaguely similar thing.

I did a BEGIN, DROP TABLE, ROLLBACK. And yes I know you're not supposed to
be able to rollback a drop table, but I could not recreate the table- I had
to do a manual file system delete of the table. If a connection gets broken
during a transaction, and you get a rollback, you could encounter the same
problem.

I did what I did coz I was curious. But creating/Dropping tables in a
transaction does not appear to be a "good thing", and that's not just for
PostgreSQL. I believe doing data definition stuff in transactions is not
recommended.

Is it possible to achieve your goals by using things like
"delete * from table1 where id!=stuffIwant" instead of dropping it?

Cheerio,

Link.

From bouncefilter Thu Nov 25 21:49:52 1999
Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207])
by hub.org (8.9.3/8.9.3) with SMTP id VAA87653
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 21:49:25 -0500 (EST)
(envelope-from tesio@easynet.fr)
Received: (qmail 94258 invoked from network); 26 Nov 1999 02:49:24 -0000
Received: from mailgate3.easynet.fr (192.168.1.4)
by mailserver.easynet.fr with QMQP; 26 Nov 1999 02:49:24 -0000
Received: from pop-nice-209.pops.easynet.fr (HELO atesio) (195.114.95.209)
by mrelay3.easynet.fr with SMTP; 26 Nov 1999 04:54:10 -0000
Message-ID: <00fc01bf37b9$10fa9bc0$d65f72c3@atesio>
From: "Alain TESIO" <tesio@easynet.fr>
To: <pgsql-general@postgreSQL.org>
References: <199911230942.KAA18422@feki.toppoint.de>
Subject: A script which drops a column
Date: Fri, 26 Nov 1999 03:50:47 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

Hello,

You may be interested by a script which drops a column as this
feature isn't supported by Postgresql. I guess it could be easier
and nice in Perl or something similar but I'm using what I know.

The parameters are in that order :

the name of the database
the table
the column to drop

Alain

#!/bin/sh

psql -d $1 -c "\d $2" | awk 'BEGIN { keep=1 } /+-/ { keep=1-keep } { if
(keep) { print } }' | grep -v "\-\-" | grep -v "Table *=" | grep -v " $3 " |
sed "s/| $[^ ]*$.*/\1/" | tr -s \\012 "," | sed "s/,$//" | sed
"s/$.*$/select \1 into temp tmp_drop_column from $2 ; drop table $2 ;
select * into $2 from tmp_drop_column;/" > tmp_sql_drop_column
psql -d $1 -f tmp_sql_drop_column
rm tmp_sql_drop_column

From bouncefilter Fri Nov 26 04:27:26 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA60047;
Fri, 26 Nov 1999 04:27:19 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id EAA30763;
Fri, 26 Nov 1999 04:24:39 -0500
Sender: mascarm@mascari.com
Message-ID: <383E0BD9.F00E5C43@mascari.com>
Date: Thu, 25 Nov 1999 23:26:02 -0500
From: Mike Mascari <mascarm@mascari.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <14945.943599152@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom Lane wrote:

Mike Mascari wrote:

This is one of the few areas that I disagree with the development
trend in PostgreSQL. Every release contains different bugs related to
DDL statements in transactions. The developers appear to want to make
them work (i.e., have the ability to rollback a DROP TABLE, ALTER
TABLE ADD COLUMN, etc.). This, in my opinion, goes far above and
beyond the call of duty for a RDBMS. Oracle issues an implicit COMMIT
whenever a DDL statement is found.

So, the limits of our ambition should be to be as good as Oracle?
(Only one-half :-) here.)

I've seen quite a few discussions on the mailing lists about
applications that could really use rollback-able DDL commands.

Personally, I certainly wouldn't give up any reliability for this,
and darn little performance; but within those constraints I think
we should do what we can.

regards, tom lane

Well, I agree that it would be GREAT to be able to rollback DDL
statements. However, at the moment, failures during a transaction while
DDL statements occur usually require direct intervention by the user (in
the case of having to drop/recreate indexes) and often require the services
of the DBA, if filesystem intervention is necessary (i.e., getting rid of
partially dropped/created tables and their associated fileystem files). I
guess I'm worried by the current state of ambiguity with respect to which
DDL statements can be safely rolled back and which can't. I know you added
NOTICEs in current, but it seems less than robust to ask the user not to
trigger a bug. And of course, something like the following can always
happen:

test=# CREATE TABLE example(value text);
CREATE
test=# BEGIN;
BEGIN
test=# DROP TABLE example;
NOTICE: Caution: DROP TABLE cannot be rolled back, so don't abort now
DROP

-- someone just yanked the RJ45 cable from the hub in the T-COM closet --

(which, ludicrous as it might seem, happens)

From an otherwise EXTREMELY happy user :-) (full smile...), I see 3

scenarios:

(1) Disallow DDL statements in transactions
(2) Send NOTICE's asking for the user to not trigger the bug until the bugs
can be fixed -or-
(3) Have all DDL statements implicity commit any running transactions.

1, of course, stinks. 2 is the current state and would probably take
several releases before all DDL statement rollback bugs could be crushed
(look how many times it took to get segmented files right -- and are we
REALLY sure it is?). 3, it seems to me, could be implemented in a day's
time, would prevent the various forms of data corruption people often post
to this list (GENERAL) about, and still allows 2 to happen in the future as
a configure-time or run-time option.

Just some ramblings,

Mike Mascari

From bouncefilter Thu Nov 25 23:37:54 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA03421
for <pgsql-general@postgreSQL.org>;
Thu, 25 Nov 1999 23:37:34 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
XAA26312;
Thu, 25 Nov 1999 23:36:42 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911260436.XAA26312@candle.pha.pa.us>
Subject: Re: [GENERAL] A script which drops a column
In-Reply-To: <00fc01bf37b9$10fa9bc0$d65f72c3@atesio> from Alain TESIO at "Nov
26, 1999 03:50:47 am"
To: Alain TESIO <tesio@easynet.fr>
Date: Thu, 25 Nov 1999 23:36:42 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

[Charset iso-8859-1 unsupported, filtering to ASCII...]

Hello,

You may be interested by a script which drops a column as this
feature isn't supported by Postgresql. I guess it could be easier
and nice in Perl or something similar but I'm using what I know.

The parameters are in that order :

the name of the database
the table
the column to drop

Alain

#!/bin/sh

psql -d $1 -c "\d $2" | awk 'BEGIN { keep=1 } /+-/ { keep=1-keep } { if
(keep) { print } }' | grep -v "\-\-" | grep -v "Table *=" | grep -v " $3 " |
sed "s/| $[^ ]*$.*/\1/" | tr -s \\012 "," | sed "s/,$//" | sed
"s/$.*$/select \1 into temp tmp_drop_column from $2 ; drop table $2 ;
select * into $2 from tmp_drop_column;/" > tmp_sql_drop_column
psql -d $1 -f tmp_sql_drop_column
rm tmp_sql_drop_column

The fact is that internally this is exactly what we would have to do to
drop a column. Now that we have temp tables, maybe someone could code
up some C to do this, or just an pg_exec_query_dest() call to do the
job.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Fri Nov 26 00:52:23 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA18131;
Fri, 26 Nov 1999 00:52:06 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id MAA12889;
Fri, 26 Nov 1999 12:46:35 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <383E1EB9.520B5154@krs.ru>
Date: Fri, 26 Nov 1999 12:46:33 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Mike Mascari <mascarm@mascari.com>
CC: Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [GENERAL] drop/rename table and transactions
References: <3.0.5.32.19991126090804.008af890@pop.mecomb.po.my>
<383DD367.F0AB3B2C@mascari.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike Mascari wrote:

This is one of the few areas that I disagree with the development trend in
PostgreSQL. Every release contains different bugs related to DDL statements in
transactions. The developers appear to want to make them work (i.e., have the
ability to rollback a DROP TABLE, ALTER TABLE ADD COLUMN, etc.). This, in my
opinion, goes far above and beyond the call of duty for a RDBMS. Oracle issues
an implicit COMMIT whenever a DDL statement is found. In fact, one could argue
that those who are porting Oracle apps to PostgreSQL would assume,
incorrectly, than a DROP TABLE in a transaction committed any work done
previously.

I personally believe that PostgreSQL should do the same as Oracle and greatly
simplify the implementation of DDL statements in the backed by issuing an
implicit COMMIT....

Just my opinion, though

And I agreed with this.
But I would like to preserve ability to CREATE TABLE, mostly
because I think that SELECT ... INTO TABLE ... is very usefull
thing.

Vadim

From bouncefilter Fri Nov 26 01:42:27 1999
Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net
[207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA24409
for <pgsql-general@postgreSQL.org>;
Fri, 26 Nov 1999 01:42:19 -0500 (EST)
(envelope-from sbirch@ironmountainsystems.com)
Received: from ironmountainsystems.com ([209.234.201.38]) by
onestone.elsinore.klever.net (8.8.7/8.8.0) with ESMTP id
XAA27697; Thu, 25 Nov 1999 23:39:53 -0800
Sender: sbirch@onestone.elsinore.klever.net
Message-ID: <383E2BC1.7D9426EE@ironmountainsystems.com>
Date: Thu, 25 Nov 1999 22:42:09 -0800
From: Stephen Birch <sbirch@ironmountainsystems.com>
Organization: Iron Mountain Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Warnock <david@sundayta.co.uk>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Table names case sensitive?
References: <383CBF6B.993B5847@ironmountainsystems.com>
<383D18E9.D4B26910@sundayta.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We have started porting our application suite away from Interbase and over
to PostgreSQL. Our main concern with Interbase was not money, but the
inconvenience of dealing with user licenses. A great deal of our database
interaction is machine to machine and does not fit the standard model of
users.

Porting our customers' data was fairly easy once we understood why the
initial attempts were failing. To facilitate the conversion, we created a
temporary modification to the PostgreSQL back end which strips out the
problem quotes. Then the conversion using Borland's data pump ran like a
champ. Ok - it isn't fast, but speed is not an issue for us. Rather, we
want to be able to convert data with the least amount of [human] effort.
Our plan is to keep using Interbase until all of our applications are
ported, grabbing updates periodically. Finally, we will do a last
conversion and shut down Interbase - and kiss irritating license files
good-bye forever.

Converting our Win32 front end (built with BCB4 C/S) from IB to PG only
took a couple of days. We snapped the PG ODBC driver in place on the NT
box, fired up the Linux/PG postmaster with -d 3 and then corrected minor
incompatibilities as they popped up.

From the little experience we have with PG so far, it looks damn good.

Gone are the black-box GUIs of windows, to be replaced with super cool psql
- which we love (far more than isql). The PG man pages and on-line help
are also fantastic.

We are looking forward to the day when we can pull the plug from our last
Windows machine and the repercussions of our terrible decision to trust NT
will finally come to and end. As a digression - I will never, ever forget
the disbelief on our programmers faces when they realized that the
Microsoft "flagship server" we had just committed to (NT) really did not
include the basic services such as telnetd, nfsd, or UUCP. What a joke.

I just wish PostgreSQL had foreign keys (referential integ) - oh well, real
soon now!

Steve

PS What sort of problems did you have with IB - we only had one (growing
log files) and have a solution to that. From every other respect IB has
served us well. In fact, if Interbase hadn't broken user SuSE 6.2, we may
have stuck with it.

David Warnock wrote:

Stephen,

Interesting that you are converting from Interbase. We have now reached
the point where we only use 2 commercial pieces of software. Interbase
and Visual SlickEdit. I would like to drop Interbase but currently we
ship quite a few single user systems running on Win 9x.

We have very good experience so far with Postgresql on internal
projects. We use MySql too but only on systems that are pretty much read
only.

My goal is to migrate onto Postgresql as our only dbms, the developments
over the last year or so have been great and I fully expect to achieve
my goal in the next year or so. As the customers for our product that
uses Interbase are charities we think that Linux and Postgresql (plus
Apache and Jserv later Jakarta) make a great fit.

For our importing we have found that is is sooo much faster to dump the
data into the native format that the postgresql copy expects and then do
the load on the server.

By dumping a table at a time in the text format (new line for each row,
tab between columns, \N for null, \\ for \, and \tab for tab) from your
old system you can be loading in one table while dumping the next. We
have found that copy loads the data soo much faster then anything else
that this is definately worthwhile.

Fortunately this text format is common to mysql and postgresql. On mysql
for example we had an import that used a java program and prepared
statements. It took several days to do the import. Using the copy
method we got this down to a few hours.

We had chosen interbase for 5 reasons

- excellent jdbc support (but the postgresql jdbc support is also
excellent)
- support for unicode (but postgresql can now do this although we have
not yet tried it)
- multi-generational engine (postgresql has this since v6.5)
- platform support - Linux, NT, Win 9x and netware (in fact netware is
no longer really a requirement and so win9x is our only problem and I
expect that we will persuade many off that in the next couple of years)
- pricing for VAR's, interbase is good value (postgresql can't be beat
though :-)

We have recently had a few problems with Interbase on Linux so the
pressure is on them (and they are defiantely not moving ahead as fast as
postgresql is, all the recent versions have been very late and some big
bugs have been left in the field for a long time).

Dave

From bouncefilter Fri Nov 26 01:54:24 1999
Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA26747;
Fri, 26 Nov 1999 01:54:04 -0500 (EST)
(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id BAA14947;
Fri, 26 Nov 1999 01:52:32 -0500 (EST)
To: Mike Mascari <mascarm@mascari.com>
cc: Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-reply-to: Your message of Fri, 26 Nov 1999 12:46:33 +0700
<383E1EB9.520B5154@krs.ru>
Date: Fri, 26 Nov 1999 01:52:32 -0500
Message-ID: <14945.943599152@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Mike Mascari wrote:

This is one of the few areas that I disagree with the development
trend in PostgreSQL. Every release contains different bugs related to
DDL statements in transactions. The developers appear to want to make
them work (i.e., have the ability to rollback a DROP TABLE, ALTER
TABLE ADD COLUMN, etc.). This, in my opinion, goes far above and
beyond the call of duty for a RDBMS. Oracle issues an implicit COMMIT
whenever a DDL statement is found.

So, the limits of our ambition should be to be as good as Oracle?
(Only one-half :-) here.)

I've seen quite a few discussions on the mailing lists about
applications that could really use rollback-able DDL commands.

Personally, I certainly wouldn't give up any reliability for this,
and darn little performance; but within those constraints I think
we should do what we can.

regards, tom lane

From bouncefilter Fri Nov 26 02:12:25 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA30497
for <pgsql-hackers@postgreSQL.org>;
Fri, 26 Nov 1999 02:12:13 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id JAA18626; Fri, 26 Nov 1999 09:16:07 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
JAA16390; Fri, 26 Nov 1999 09:12:09 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <383E32C9.7533ABF2@albourne.com>
Date: Fri, 26 Nov 1999 09:12:09 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <maillist@candle.pha.pa.us>
CC: Postgresql <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] Update of bitmask type
References: <199910091020.GAA05654@candle.pha.pa.us>
Content-Type: multipart/mixed; boundary="------------9E38936425C3CD788D4FE732"

This is a multi-part message in MIME format.
--------------9E38936425C3CD788D4FE732
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

I can integrate the type for you into the include/catalog files if
everyone agrees they want it as a standard type and not an contrib type.

Hi,

Attached are the C-routines that implement a BIT and BIT VARYING type.
I know Bruce said he would integrate them, but he is writing a book at
the moment as well, so if somebody can explain to me how to go about
integrating it, or would like to have a go, go ahead.

If any functions are missing, let me know and I will add them. This
should implement concatenation and substr as defined in the SQL
standard, as well as comparison operators. I've also added all the
normal bit operators.

I developed the C routines outside the postgres source tree, only using
postgres.h and copying bits from ctype.h. I hope it will be fairly easy
to integrate.

Any comments welcome.

Adriaan
--------------9E38936425C3CD788D4FE732
Content-Type: application/octet-stream;
name="bitstr.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="bitstr.tgz"

H4sIAHwqPjgAA+w9/VvbRtL91f4rtrQEyZbBMgSSGLtHSEh4LoG8wPWlbdo8sr3GCrakSnKA
Jrm//WZmP7SSP4AEuF6LnwRk7e7M7Ox870p0/DRJ45VvbvPD1uobG3X2DWu46411+M0ebrhr
+Ft96oxt1N2NtcZD92GDMdd9WF//hj28VarkZ5ykXszYN14v9j0vmNkv4Sf9YXoXFN3ppyPW
/4MXw9Xy4FZwuPX6+vrs9V996K6K9V+tr6+tP4T1X208XP2G1W+FmsLnb77+3/lBdzjucbYQ
hUl6EvNkebBQLqcXEe/xPkPxeMRY5UcvfuqnTX1/7AfpaoPBvd2gx8+b5fJ3cNsPOHv5/PjZ
7gvrDxuXFn5tunX2A7PgqrpUX7LZE7quufXq0taSXc4GPt09Onzz/ODpT0fPS6VH+vaPWwfQ
8vLZweHPpVLi/8HDvkXI7fJKhe2NRx0es1BQyvyApQM/wS8MxNoPTlhlpQDq1fM9683RgV0q
WZYFncbdlIH4D3ngsYoNfZ5tHW1RD7vW/jB8Bw2E6k0IaAFXGgEOzvp+nKSsc5Fy1g2D1PMD
xGYg7nmpN4n98Fq4AUZxmoBQzpMLFAnvpn4YYKM3d+LIWYnegjuHuz8/p2+shh2Iw+JS8VtM
2+v1EByAR5QGAi+lOzzoTeJ6s/VMTbSIvGIstManFmXqbAMOMtdjaQiYw5jnp0nTPvE/8IAB
G0/SwSQxyFREIPDA7MXFiklIlb0tl+ADMitaF83WNkMhdkF467buWtJcq05wLZLC0uEXIfBH
8WmSidbQP6U2y8ZVPTx6pcSJx4k9OZfne5qxllDOis3wjiBCL6rg5GsvOQWMsFJn/nAIkD8A
Tfzc66bDCxYCUGSww/xlvmzqn1AmAze0vd46/CfMuX6+s2Pefrn74iUrfurnj+qg2d0BWNYK
+yMCcH5gia8JoAtS1huPRhcOY8KOeGkKlmUU9uxmblQ4TtWwQksytUm4savj6oThECfLf2dy
iBefuA7T1w2jE0z48k4nV+qUXqHT8CqQhvMg4dyhT3cUzekkOQf9PBBQ2Y+ZHdlEzzC+Ysfz
K/cMwtTsmWtLBn4ftOVkkOsi1jYZ9NPJzkPev0rfrjePfQbMcQfU1ejqSFlK1MUQ+v+3XfkX
ffLxX/dWcGD8tzYz/ltb32hsqPh/bWNtA+O/VYz/7+O/2/+sVGo39SmzSlnb4OUuXIM33RkH
FJ4krA+2gJzf2B+mNYxgIJZE7QLPh6YHxl3IEMqylyWw3WfP9452d3a3t4529/cEyO9fcq/H
4+9Fl5skHxze1HA4u6vypAXwrsZtr9vlSbIySMdRvj9YGG8YnqxEJ+9wuvnGceoPkxXihx8Q
IqAAPuC4y6AYb2Lwsuc8eVImPfkjwp+1GvuDx2EtgrAMYiLs0FOBTxZWiBEfULBxhMFa1QF7
eNIRYhcZdCS0RBLeZLQCq4YGw2GwlrCe5YLfN/AIQCPv3B+NRxLgMiO0RzpypQB4HPM89n44
HIZnCIcP+YgHqeIAG9DC05TyJJ4NwuEEUAsZLcfYRVIZzQXDy2VmeQnERwDNgxhJzUEiQJi4
comCkIu5gZAo9j94aSEW17KOjMiTlWSUkJMnLHJC4OBm8rxcwl8ESzLAg/wj8U8Cv+93vUDm
IiItkYuM4rRCeiRjMFYrCx0ChkMoCMR5Cg1E14iYwtbAG7KYR0AscN/LZReiN6qnmsVRJjCQ
efU4jB9BcNgDeghikE/RYv772I+hORqOEwOMDqZFzI8CFoejLFoD4SHKrePjYxHRIboBh4Xu
8K43TkAKOIu8JCHDApLDPCFPsCgYg4PbHqM0MQMprpMXx97FOz9YBqZEPuYZkEE6LAiZ3+Me
iBYECbAaI+4FyQ8/2GQmRCBQvlZkW/4IKy96AmPHw9QhLYdxUbNUMnIG+CnWAjtDqA635Boh
aiZz8krcLBMSZL5DAF5drhMEQEmeGDUthc4JIFOjEhjTnILJD6Kx0Vt8aIyMQN9BdPduwM+b
ogkA1FkL1u5cD3JbOYQ5AL7DOl3gLZi8pp7+ucMummW0J36fWQlrtdjev169Eloac5hsQDea
2AUQbg94V6ZCWfaeMdhHTeig1HkBO5e4EfAv9V9braXOEvv0ickvT5dsVtYarOYGE3KRPD4E
STSGnptDj2cNreuh1MzBZ1jPDw72Dxy2IKXsCVtMkE6MlD0wU0O/lynkgoNZUFmsEcCDu3Bh
JZjcE1nAgmdKNQ3DQzqWWz8lYhIOLrnkxbcGybYhRqzSYmvYSaA5DEc89Uegw1r2FdnJOIqG
oGLLbLePOgW31S1UXszz0Q6NvFMuuJSgzOpF07OF5UvBbu+FqdGa2Rk/6HO0MCTPYBoFrA6Y
KbABWMEZeEFhCEjB2BuKEaLcAEIHTAkDSJRh8kCdF8vFAfHyqCTimSKMIQzOEazeKBRUB2xV
uksvyXfGekUioeFAiB/GMXoRuSzjCNiwptNwwf+MnSDsNVcsgXFTLoeSJGrGceJ2O+v54EFO
+kA8i12qq9gpv+ClWWKZL8ZgiY4t9pDvxA4wRLGfpiAmZNdwStZiz15wEKDhBh0zL0dJFgKY
r+Dk+ojZYbc2e+2db6VpfAjI7TkalEUNIu4cjRMiccjRbeCKLfaIMssAWFOuqWZWecwylqBG
WHWgWfoDG7wRRDJdJNGWOpjwFCW8zpJQSG5F2J7hmXeBthfIBMVOQHhRLIir2G6GfCQPIz4C
UJZyJHWHKSSqCCSabCBHykRWaMuaND+Vmfz/TAtRyotqh9ZC1rJIqEEtREnOT2VAIvV2aliy
zBLh5BIVbVBbh/eFwuDliR8EOoDNgiHTOCURGqYqmbUY2a3rYKrEKieoDJcpxoLAj2Xtid54
ccK1y5uMeiiCMLDLYcCo0yA8w4n3lYpLc3gGl91wFHmxYGSmeBoAmnxZPGuWs1DE6nTJF+AU
v8U5ovmFicL3ahW9YLUKevgRNQfnBZED+BR3yRaqBKL0qcXOm6q50221Nmz2UbRK0OJLDj/d
iatVuvosvZDs1m6TWyt9FlR+znmpqVxEi3I1Ll4648Jc262l+hLaJbjebC09Rl+qZyOEwKaO
4PNwq6EpTJZ0xwLAlgFgZy6ArSWs9Lr1aVA8A0p/LhRvAoroa5inhW1hKSNi4WI3cxY9/8RP
FxwAZRuLOn1FK7CA2fLLVdQd5eKSjECfzc010U0t7Ody2fQVYFAzSyuXuRhDgVXqo13XUp1X
RamDMHmEB0GILQQdozht1nGXwNBVQoLpRCdMU4xLsC/5QGUI0FyIMJk0C3xtrO0VmHE0k4qc
FQryITsL0r618BRHLh6D8cDyIF4t9t4GwNvYsYAnm5vMelRDfLbNHqhyt3BRs9txW0ASLpEi
Cy01wHAQE0NtGisV4VK3moahiF1IZ9B1gQcVoT3mOtKXms5RLqkMhAWPm+XPVFtQlXVWk5mQ
ylYxagM2IkZMpZB1jEOaeAGrjRFOYoQwwuKRGMA/3MSAQEnCE4tBURDZwW4qfGs2IxwN/g3y
sgTSQTAUMHg07g7EIN4H1+HDXYO+YQgUyMETKZi5F6DTrBKJu3SQIlsSu5jonyKZPGEnn5yn
Y4RP07MKZe5m+vmG3cx1gZgfei3Vlgq3Xbr9ti7vK6OaQ6Ij8MxtJxq8aBFdVtZAx6TeLq61
s32q5mXkIpQqW9Mdya9OOtMMLWq4EiVxh6wOzOV4qXjn7ZK+BSJ3hsks9yg6RrdJQk3bUiqA
6I+HQ5n6kxabwY52Fn4LPIW/iavE/Gqr4Qg3gXZO4pW7z2h+7XYb5zatBfSwfr6j5/U5I/QF
iK4HRg73xpKURzL2J13AoIw0QKYNYgKeSG3AeqeghRMRixdckEzriaBg+a0WuTlwcHGtNod1
ZK7zkjJbpRNTp9/EIs7K/K4o30zoTvKFyiNPBjD0OKYqnTrsz6NFs1XoLrTi6TytKAh0zfAW
JNzGd0PMMcbAglG5RONPcfzpZm7sKXZFh/DRiAxgCufC+2DMZ4ORgLgRzMQSsk9GL5ubItbL
FEL91lgN0k9bPqImXTzNYrUrYctwff5K2ZflTbXvS+J/E+XNTEmut6V8X+RT5uC+bHdftrsv
2+XKdm1dtbvFspyyV9esy5lbd19enxNdr1ecywi+r87lq3MqIflfK81hxUMX50TYeHe1ub9W
ae2+RnZfI7u9GtkNlKumupt8vco82PMVdSu4jfPT1asYfkBUlJCHp+OoBWSJMIPDIRPnakSq
sE2VeT9BCxJx8N5hnMjDRmBhKXAgblEFgNOBjO6UIaoSl6+GqUiADjYgXWSCeyreTrwRuF3v
ggabXqNw/kkVuujMA4LKh0wJHtX0Yh2fjQNv1PFPxuEYptxB3lBikVHd4ekZBxGjkyAGWgNV
kQRNwW4/Ix2i1zFHrDJ0QHgUPXi5oo1R/UhU+wRoEajRiuJQBDUxfADjT8DZYagvGOugO6Oz
zB10CicQF2om/QxwkswRaodVSO5UBJT4owgWG+CAR8RVUmt4gcBGHjVhWWfiZD2ySrYb3nSZ
Sit0MrfcmXukmJJEmTXBtFzHiMobWa5UiWBYJWroaOpb+QjCbvIjphEWArYxTpzS0LBzOZWF
ZNkiX5FYc4URApU1NoqNDdNh0+hvVXzSmIlIxC05IcPT+yKayjTDE8W/oHDqn2yUhAoBVXcU
WdaHELInelCCYgmi2plyt2GDaSmZTx5QVxvzzTrZE7VMcw51/w2Wyf2TLtO3apkEYQAUdTIz
34A3PQsNO0U6KahIIMuimNtlPR5BOEwmIGBnAw7KHWd1BASnztjBREeQDvDYYfx3SCnphKOw
L1neKQ6SLbOtoUw5PXF0MfF7mLiSzcessNfzMUKFxJRMG3VFe4EJsqwsE1aJcqWY34ZIp4Pg
OD7W4pMF9vMeg0wxGOJwPOyhIVI2Wp7M2wrkpg3MjCaE3n8ciOc2esJUoWiXO/OfD5jQAVr1
CW3Qt6fqhYAAaG5cRSQtWg0MIWqSYCuyJnsIVcFq3QiTFim6eZHNi+prP7D07BVgW2scDG+1
6ioUnKu9l+jvTA1WRSjJCtVjU4P7AWSfPRFqbRRMifWG0Zvz1AgteJ7VlpARIt+hTvIAUh7m
JYb0UpibLdq0MkDOeZbmaiDbkyBvYOZy4ivqERJhlgK44oFOTQ1zam65dOY/dDJF3QoKRndc
MAJ00aDt7Gah5mzqYIw66N2E4umy7Jc6pkwdZ9SN3KoSdKmaM2s2Ek5FPg8qEsoZBRbZd36R
RaPGburQwGKPiX94UmDCwDiF2TtZvia8mCwqbYfRhfnEqI5DwaeqalE3urAKBRJnmikynWQR
vDzmbMSpqibsFvNJvVrSzmAHsl252sN0uqqzGJF5dBo9YW7t/D6dYeMa7Xp+bzBf7RJHNvBs
Pk5TkEFlKsits7qP1gZRfzGeMJUTVNWgyJtWljKMLwrAnMrVJANqbq7SxJqIY9N4YFMAh7tq
s5oQ4M9PkICDfrJ2O5uAmXc3y6VI1I+QXTDABCsJohqVAEmwNjfVlA1I+b3u2YdDOuppN7Rq
0CP2IQbBbTS6mas0ZpJGKRglqQ6jzQ631vESEWeww/97xXqxBwuzvuzW2WPzBD3FH1d5uq5g
GEXwEZtf9AXWLuQVsVNeqzAESQS7yt3MarKi2Rx5ySlue6PtTObZzrkWsmgDSbw4nV0c4mWC
JvS1d24ljtBGTjcgyuCOgFDNtDRx2xIqGGvubrqT1dI9XR0majwI1UFnivXRaeb3aodFdKdp
ZrRuNE6vcGPFbWqNE0jf/6fDzvgSSNoJbZOl8ZgbIoeP6KXykfMoTCi6BvZBrIPxNoi/jPLN
Zo7NetaxXhK4n2h9ncaMWG9ifCVLYlW/v5QxxIOtmJ5g6YI912rmyTJ8OMaCz8UP+WMkFrLA
Nh9UF0ZcVIQB5E88ctQemIKrs7aSmH6tlT16k3uOnaqfl/smuyrIMJ+mdwRrSp9VwCqruoqu
Hf8EdwixUjUIz8TJr7OiwRc+DU+HdbGqKUn2lY2fnDwRPH/PATpEyQzzj0XoyanQmCmHj6qq
ov1R7ZNVpAFOwAD7RUPeVL1o3arVKLGLHgLteElsNCCQdjtfkRUQNZxYl6s/Z6cocLc4NDmJ
jj97TYMpPnNLzPKUEvbBuq9aOTSLwrvS6UfwM2JzH91PUUSMojZ70KKhzVwlfZb3AY2mWiCP
geuoAcPwxO9CAru19wzTeJn3ZyXSIx0U0F7dOA1HEIXDiCEV8sCUUGjeUxtbySCM6dUMxtOS
uQB9/nPw2hNlDmde/O2qAyBRQ13FN5sGl5UZQ8+hjIwOzNQ3GX9dasyutUEpMU6JgnXYL+L+
yJ16iErHoVFjVrsIyi495m9qaEbVZJCai0dJjeWa0PEjWC74/QAXC9VLlcbUK1BkuV2+jsRL
oCdkenXSMmirC/WaI9thPF209w9uSbKXC6I993UMNyLZZgh1L+d/ajn/pORcS7mRYMnUdMLi
T/UY4LW0jZ+rAOezNOD4zlRg/itJ7nXgL68DKu3I6cJvmc2X8ckdaQQ4lOkasbd/hBrh5fSh
IMvFl+aY0jtPbL9AVudI5Ew5M0RyVnHO7DJL8opJNMrQLBG6hgRhmWYiBod7eBwozgwmwPp3
JbpLI6nfYISC0cPNc3qdkUh8LHpXlzqjZW5xZ4eh7Mm3SBQE57KXJGXlFsgW34kyiiqnXEO4
vkicqJJxAlb+A5dzplO+MikUExcvg8qO+wLNsJSqgJltj2RvjrJogjX5Cqj/gtReKpZlZnAb
q0RAaj4TNbJfmvEiKzSTWkzXC0zIMvBSAinLkyBxqyQ7xnQY8a4PVqjrJfwJlSW8QMiiqAio
TNIsoGh7i6eX87h0ISF2WJSdhsxOSlZpa6PuGOPEaSB1SAs7z1PbWJRWjVS8EulE3MxqMfme
mnur1Htm5i1cg0nI1HIsI2KY3qyrZOsuty3nV1+1yGr1F9J+4/o/741qf3YDQLbrivqPff8+
6j/DKwq+HnLzOQp1uMlwaHT6OXeGeZpWTjMdudjqGhbkGjYksyJVUyxzBmVGjTlm1dYUeKSb
9aYkeVcf8Dbf7pp/BHGW1lPgIJ9E1HaEKfNTkpYntmdv4MjyIRitaebnmls5V37/W0e//y/l
yS29AHD++5/dRt1d1+9/3qiv4fv/1tbd+/f/3cXn6i+80/c2k7Tnh8uDdrmMh59S8hN4LAwE
+FETj9mK28Kwdn7B5zQ/soWn9bpbX3DgwnXr9I++1OE2Xhyv7rgNumhsUMOCI+U8/1k4lgNB
qly4/Czec6oPEQt0eARM/s//Y9AfXeE1KHQzEp/dIIlsw2GPHbbuMPcR/HfpUtCMRJbLdF6O
ziK86/HU84cJs8YBnjjlPaae2GXaU/vZ0QVmLciH99RL7pCsJ/KdB8p9JcK/FYfIZwQpbDCG
PFVP0Jo5+CPMwTN4amMEsWmwi8eLx2zBSX7xf2231+j3A/X0tTppATjEoRqcc3nkAdmWOTWH
vc8ijuQXFLZfyaflqwF4X9LwMU/ELj4rh4/i4Ww6QIJ0F0gNLIZ6kRu2kMPL1kp3XVnJrYWV
ZE3ZXHFzSSDRLyagfk72rDV9z46667Fvg+3912+2DnYP9/cOnwiOzJpeNvP3LR8fBXkvG9+r
RuMUS8I2W20mSOtp0pLptL3/VZ/gkIefsI9DDTL3Ngne294CT0Yv57xZkj99YkVmXk5xdluc
szJpN4lH2g//9fTw6EATbaC2FnsOPqdATCtiXwVsrvMIMeawic1q6oDttn1tqI8vgfpYQb0e
qY8vIfXx9YGuOg/nAoX2LwE6n9LVL6PU3bgEqrthF+zg2+DV/ovd7a1XuOV4s1L94GuF2gt6
s4Q6R/n+wQ2r49cSHsZXovv4pgn/7WsJP5+gnPKfKbTv7R9dhXZF3L+vRJio8kqnIZ+8NXAf
vtzdOWKvnu9chjrnEJEzU9BKbyaZW0fWtgzPT/5uGpvfpourPfhBMN/nic8ycGLie3u66xPz
ONh98fJPPRFRSpw7k7cBq+gP5no/7e69MG5dY3aXxy365RRzA5dKIXCxmzKnNeKWyZBlMraZ
xen7OOY+jrmPY+7jmPs45j6OuY9j/nfjmGuUje8/f5GPrP+/9k553x/yW8Ex/+//MNbI/v7P
Qxc64N9/bKzd1//v4rO982rrxSEY8NpJWb7r7glTu0Gh+mM+Ybn0vbW9bTP4SQNsVgvZ9/9g
3/+mRi2HT/Sf/lEXg7KGlAE1WsvdIfeCJ+VSPGK1PqtohPeG6K4+Uv+zzZ9bwHHZ339dbbiM
rW9srLsb69gA+r++dq//d/L5zu/jWwHYm/3DoxcHzw/fvdR/3dG4NXXzT/0tWNqVwQMc2Z+H
NTepICR5NNFC53SxyV2faKMdH3zur4lnYhQ1+HAd06+WYHXb+POU/2nv7HrbtqEwfG3+Cg0D
FjtwvC5Lt6AusiVbLwys2JYEw4AgHWSZjrVKlquPJt7Xb995zyEpylGUBeiGXYgXqUqRFL9J
WTzPi1OgIEuOgtoNh3f42D7cAj+K6xe4HtVxwrv2OCcPx9k5xmJYniNzfEUytz+q/T+ydMu6
stwHPJTy+3hRl54rA38PG36fH+LvUe23TLKwlL+e7yKr5okWb6+6m98LK24L+U0IxzaOHarw
XnhpoEpayIan/D0YAeURVWDvAZT5exGQBzkrNA1aHEU8ac2Z1A+8OUft8dpyKJUIb5O3tohe
TpVf/UdBGCVxqVNP4ni2Zowntd5g8Mz50n9tx8jmv+qonNEbPY7jCUrA+qFT1AlQ58K5r2pN
e/yyWoelTrZjsL1WQa5vNnkWsYnjub75ga71AmZzsOarCoGK2ZxSUjbCtOHpx5zujNn94XB/
Wa2jXzYlOrG8ltni+BFdhx8NvFJuJO8fQHcPYroXRjrt8MWA9gBxiN5sgJAMVYFKF1PDmK31
QcT+WjLPmWkKM7c9jqPvBPtdDbinDQYiGj1VAyZpD0TH+eqz66n60+tFP3lqva1y0Lsa1F5E
JxP9WEQWkPYitupo1xNwMyWcHAinD90t9V05bYwVnqkOj6+Or5t9kGZF8XQ5YXocJbjQee48
wZULlvIOq/x52qI+A5zEeFbfkhN7Qcr/qI9hBLzsd45Pc2b/d/7q9NvXr/6lZzzy/vf8+bMv
nP4rbf1wJOzoy/7813/iTi3k8JsaqFhmAdh4rL0JsPbFj98dgCaYxOHaB5iwoqlSl3ygNNH1
619DzjM6WDoN2EbKvMqdzS4xvyv8az6WTYIz3OG5nhc7F0VAZLoABDaGDViDqjhW+i7Sm1JA
iUgwbopJMIiwwLnUZexUUyfBDNwBgC4QQjGki9GdUUb7XSYYCkeMawOY3KKIsTr5wE1LJwTT
kF5fKfa7KmYQpwls4Y25dmjBPKMbaQErnzSMVlL1CLbI1nulWoWULdkHfcrPGIaC4mWsJBCI
4XpL9QM2wFcjaofZ2gO1u8acBZxQWBRVyuKWxh6cUap5oEOjEvGuyuj1XFH9nu1NJpM9ANB+
5ivTxOB4OPIkczJlGi480uQ4kM9RVt2lZiIpR84U6Rd6ZKEla3OgKb02phZZO4gac1+MTVSd
RntEI2T/1/iP8SfjN+OXL/lJJycwI2SdGkXbpmWV4PAyMGy3oeEdQ4JXyDkwz6mhlzBH9Jl4
sLfKlsp1OrM/4QPp2fqmZvjT02rTxKG5RGluBTGpuP5yHSZBtsENZk9ujJ0xa9H+xjTLiPlu
4I7THpEWRupUuDYQHIVfht+MbIXaQ9yrsE3G15pGWmSLlDHXik/XG1lWHpisikp9izl0gRu9
OGYNHVRWcJFWnAmLE62hYLqWvaXO8lo0XhK9uOFBYn9bcLjSDc8D1GI31JpCZMdgHwO7PdtL
g1W2gckCd9UiS/U8W2z5+LiNYwYoC0gjs6lmXh9XE+UPcQIaT0yAVfQs1nCF2XZhILg0wjQb
l1IfdCPlFiNrod/TPmQDAGxVAuzHzeWKUGRVHmG20PRI0Qym0kdvQeTTeWHgX/WvKWLBKhrE
CpNkweOedrcGM8t5DdNUCCZmqJmX7UUgMRhhb39mW5lV8+DARz0ZZWTUiHLTsAvIfcMUU9W/
w9nbYbDUtwGMah39218LzAzvVJkb4N3wfRgn2KxD3NmYkjxJFpe2yefAmTNhcoci6+HrRRg6
T82chOaWeYo/fTSe7AvaUOqshPNw2vRccKQl2WYRiienNI/XYb61ObOJPU1CpFEhO2rU/7RO
1NUlrxM84qSjYZwUmuZpDB8qGBaJZUOc3UP08nSkatYyj3IRBKOHpkxuibI8p3e2ZHvtCjrv
pttRyc7isrkueN3GfdLuRkFRKheODLSD5p0I6Q8+HfzdqQvUQX+tA3VgCL1AXcW2gToYiV6g
rpQMAqsL2Un108q49qq5m3Ay9UJ2Gsv7AbvN6v2Qu0bL/r1H7dLuBe4wYjXdTWoAvRx7pCVW
NkGjspXQ7qowDjZQS9D+WkfxTuXtgPZgcvF1mMxpKaBVhDY/o/6ls3e9613vete73vWud73r
Xe9617ve/Y/d32Su5EYAoAAA
--------------9E38936425C3CD788D4FE732--

From bouncefilter Fri Nov 26 02:41:25 1999
Received: from test133.ee.ic.ac.uk (IDENT:root@test133.ee.ic.ac.uk
[155.198.133.240]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA33776
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 02:40:57 -0500 (EST)
(envelope-from smacedo@ic.ac.uk)
Received: from localhost (smacedo@localhost)
by test133.ee.ic.ac.uk (8.9.3/8.9.3) with ESMTP id HAA00820
for <pgsql-general@postgresql.org>; Fri, 26 Nov 1999 07:40:01 GMT
X-Authentication-Warning: test133.ee.ic.ac.uk: smacedo owned process doing -bs
Date: Fri, 26 Nov 1999 07:39:59 +0000 (GMT)
From: Silvio Macedo <smacedo@ic.ac.uk>
X-Sender: smacedo@test133.ee.ic.ac.uk
To: pgsql general mailing list <pgsql-general@postgresql.org>
Subject: Postgres on Ultrasparc
Message-ID: <Pine.LNX.4.10.9911260736010.803-100000@test133.ee.ic.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello folks!

I would very much like to know if anybody has any experience in running
Postgres on Linux, on a Ultrasparc machine. Any version of Postgres, any
version of the Linux Kernel, any model of Ultrasparc.

My system still halts completely when I run regression tests.

Any information ?

Thank you!

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
``````````````````````````````````````````````````````````````````````````
Silvio Emanuel Nunes Barbosa de Macedo

smacedo@ic.ac.uk smacedo@inescn.pt
Imperial College, University of London INESC Porto
Intelligent and Interactive Systems Telecom. and Multimedia
Exhibition Road, Pc da Republica, 93
London SW7 2AZ, England 4050-497 PORTO PORTUGAL
Tel:+44 171 5946323 Tel:+351 22 2094220

From bouncefilter Fri Nov 26 03:47:25 1999
Received: from fep132.fep.ru (mail@fep132.fep.ru [195.230.89.88])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA54796
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 03:46:28 -0500 (EST) (envelope-from phd@phd.russ.ru)
Received: from localhost [127.0.0.1] (phd)
by fep132.fep.ru with esmtp (Exim 2.05 #1 (Debian))
id 11rH1A-0005zo-00; Fri, 26 Nov 1999 11:46:12 +0300
Date: Fri, 26 Nov 1999 08:46:12 +0000 (GMT)
From: Oleg Broytmann <phd@phd.russ.ru>
X-Sender: phd@fep132.fep.ru
Reply-To: phd2@earthling.net
To: Silvio Macedo <smacedo@ic.ac.uk>
cc: pgsql general mailing list <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Postgres on Ultrasparc
In-Reply-To: <Pine.LNX.4.10.9911260736010.803-100000@test133.ee.ic.ac.uk>
Message-ID: <Pine.LNX.4.21.9911260838310.22985-100000@fep132.fep.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 26 Nov 1999, Silvio Macedo wrote:

I would very much like to know if anybody has any experience in running
Postgres on Linux, on a Ultrasparc machine. Any version of Postgres, any
version of the Linux Kernel, any model of Ultrasparc.

My system still halts completely when I run regression tests.

Sure. All versions of Postgres, all linucies, all sparcs - no problem.

Host oper.med.ru - Pentium, linux, Debian 2.1. Postgres 6.4.2.
Recently the system got major hardware problem (overheated processor and
damaged memory or motherboard). The system got down to its knees, but I
moved the disk to another system. Filesystem was slightly corrupted, but
fsck restored it, postgres started up and now it is alive and well.

Host www.indicator.ru (now closed due to lack of manager's interests).
Pentium, linux, Redhat 5.2. Postgres 6.4.0 and 6.4.2. No problem.

Host sun.med.ru - Ultra-1, Solaris 2.5.1 with some Sunsolve patches. It is
my debugging environment, so there were all versions of Postgres - 6.3.2,
6.4, 6.4.2, 6.5.1. All went well, including regression tests.

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.

From bouncefilter Fri Nov 26 04:04:26 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA57137
for <pgsql-general@postgreSQL.org>;
Fri, 26 Nov 1999 04:04:03 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id RAA30115
for <pgsql-general@postgreSQL.org>; Fri, 26 Nov 1999 17:03:59 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma030110; Fri, 26 Nov 99 17:03:30 +0800
Message-Id: <3.0.5.32.19991126170409.00841b20@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Fri, 26 Nov 1999 17:04:09 +0800
To: pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] locking/insert into table and transactions
In-Reply-To: <3.0.5.32.19991126090804.008af890@pop.mecomb.po.my>
References: <383D9DB0.E2A54358@gospelsjop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

I'd like to prevent duplicate ids from being inserted into a table. I can
let the database enforce it by using UNIQUE or PRIMARY KEY. But assuming I
prefer to catch such things with the application, what would be the best
way of doing it?

The only way I figured to do it was to use:
begin;
lock table accounts;
select count(*) from accounts where id=$number;
if count=0, insert into accounts (id,etc) values ($number,$etc)
commit;

Is this a good idea? Or is it much better and faster to let the database
catch things?

Is it faster to use "select count(*) from accounts" or "select id from
accounts"?

Apparently count(*) has some speed optimizations in MySQL. So wondering if
there are similar things in Postgres.

Thanks,

Link.

From bouncefilter Fri Nov 26 04:30:26 1999
Received: from test133.ee.ic.ac.uk (IDENT:root@test133.ee.ic.ac.uk
[155.198.133.240]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA60258
for <pgsql-general@postgreSQL.org>;
Fri, 26 Nov 1999 04:29:53 -0500 (EST)
(envelope-from smacedo@ic.ac.uk)
Received: from localhost (smacedo@localhost)
by test133.ee.ic.ac.uk (8.9.3/8.9.3) with ESMTP id JAA06879;
Fri, 26 Nov 1999 09:29:00 GMT
X-Authentication-Warning: test133.ee.ic.ac.uk: smacedo owned process doing -bs
Date: Fri, 26 Nov 1999 09:28:59 +0000 (GMT)
From: Silvio Macedo <smacedo@ic.ac.uk>
X-Sender: smacedo@test133.ee.ic.ac.uk
To: phd2@earthling.net
cc: pgsql general mailing list <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Postgres on Ultrasparc
In-Reply-To: <Pine.LNX.4.21.9911260838310.22985-100000@fep132.fep.ru>
Message-ID: <Pine.LNX.4.10.9911260921500.5832-100000@test133.ee.ic.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi Oleg!

Thank you for your email.
Maybe I was not clear enough.

I wanted to know information about running Postgresql on Linux on a
Ultrasparc. Like this:

Postgresql on top of
|| | | | |
Linux Kernel on top of
| | | | |
Ultrasparc Hardware

So, no Linux/Intel , no Solaris/Sparc , but Linux/Sparc.

I have my Linux Kernel (2.2.5 || 2.2.12 || 2.2.13 ) running on a
Ultrasparc without any problems ( I run httpd, ftpd, nfs, samba, gnome,
lpd, etc etc, compiled a few kernels, etc) but when I run postgres and
start the regression tests... BOOM! Not even SysReq, register dump..
nothing...

Thanks anyway!
It's always good to know that Solaris will always be a solution...

On Fri, 26 Nov 1999, Oleg Broytmann wrote:

On Fri, 26 Nov 1999, Silvio Macedo wrote:

I would very much like to know if anybody has any experience in running
Postgres on Linux, on a Ultrasparc machine. Any version of Postgres, any
version of the Linux Kernel, any model of Ultrasparc.

My system still halts completely when I run regression tests.

Sure. All versions of Postgres, all linucies, all sparcs - no problem.

Host oper.med.ru - Pentium, linux, Debian 2.1. Postgres 6.4.2.
Recently the system got major hardware problem (overheated processor and
damaged memory or motherboard). The system got down to its knees, but I
moved the disk to another system. Filesystem was slightly corrupted, but
fsck restored it, postgres started up and now it is alive and well.

Host www.indicator.ru (now closed due to lack of manager's interests).
Pentium, linux, Redhat 5.2. Postgres 6.4.0 and 6.4.2. No problem.

Host sun.med.ru - Ultra-1, Solaris 2.5.1 with some Sunsolve patches. It is
my debugging environment, so there were all versions of Postgres - 6.3.2,
6.4, 6.4.2, 6.5.1. All went well, including regression tests.

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
``````````````````````````````````````````````````````````````````````````
Silvio Emanuel Nunes Barbosa de Macedo

From bouncefilter Fri Nov 26 04:42:26 1999
Received: from genesis.sundayta.co.uk (mail.sundayta.co.uk [212.24.70.227])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA62296
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 04:42:23 -0500 (EST)
(envelope-from david@sundayta.co.uk)
Received: from kings.sundayta.co.uk
([192.168.100.31] helo=sundayta.co.uk ident=david)
by genesis.sundayta.co.uk with esmtp (Exim 3.03 #1 (Debian))
id 11rIVH-0006hk-00; Fri, 26 Nov 1999 10:21:23 +0000
Sender: david
Message-ID: <383E543E.E93E8A30@sundayta.co.uk>
Date: Fri, 26 Nov 1999 09:34:54 +0000
From: David Warnock <david@sundayta.co.uk>
Organization: Sundayta Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Birch <sbirch@ironmountainsystems.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Table names case sensitive?
References: <383CBF6B.993B5847@ironmountainsystems.com>
<383D18E9.D4B26910@sundayta.co.uk>
<383E2BC1.7D9426EE@ironmountainsystems.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephen,

From the little experience we have with PG so far, it looks damn good.

Gone are the black-box GUIs of windows, to be replaced with super cool psql
- which we love (far more than isql). The PG man pages and on-line help
are also fantastic.

Postgresql is certainly an easier db to work with than interbase with
that absolutely terrible isql also as you say the docs are a more
accessible.

We are looking forward to the day when we can pull the plug from our last
Windows machine and the repercussions of our terrible decision to trust NT
will finally come to and end. As a digression - I will never, ever forget
the disbelief on our programmers faces when they realized that the
Microsoft "flagship server" we had just committed to (NT) really did not
include the basic services such as telnetd, nfsd, or UUCP. What a joke.

The advantage of running my own company is that we have managed to keep
right away from MS rubbish.

Dave

PS What sort of problems did you have with IB - we only had one (growing
log files) and have a solution to that. From every other respect IB has
served us well. In fact, if Interbase hadn't broken user SuSE 6.2, we may
have stuck with it.

Our biggest problems are with installation of the jdbc stuff on newer
versions of Debian.

From bouncefilter Fri Nov 26 04:37:26 1999
Received: from fep132.fep.ru (mail@fep132.fep.ru [195.230.89.88])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA61485
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 04:37:24 -0500 (EST) (envelope-from phd@phd.russ.ru)
Received: from localhost [127.0.0.1] (phd)
by fep132.fep.ru with esmtp (Exim 2.05 #1 (Debian))
id 11rHoQ-000652-00; Fri, 26 Nov 1999 12:37:06 +0300
Date: Fri, 26 Nov 1999 09:37:06 +0000 (GMT)
From: Oleg Broytmann <phd@phd.russ.ru>
X-Sender: phd@fep132.fep.ru
Reply-To: phd2@earthling.net
To: Silvio Macedo <smacedo@ic.ac.uk>
cc: pgsql general mailing list <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Postgres on Ultrasparc
In-Reply-To: <Pine.LNX.4.10.9911260921500.5832-100000@test133.ee.ic.ac.uk>
Message-ID: <Pine.LNX.4.21.9911260933320.23352-100000@fep132.fep.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 26 Nov 1999, Silvio Macedo wrote:

Thank you for your email.
Maybe I was not clear enough.

I wanted to know information about running Postgresql on Linux on a
Ultrasparc.

Wow, this is danger. I usually avoid Linux on non-x86. And I avoid Linux
on x86 with high load - I use FreeBSD (but not with Postgres - MySQL).
I heared there are major problems in Linux SCSI subsystem, making it
inapropriate for high load situations. It is possible that you touched one
of these bugs.

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.

From bouncefilter Fri Nov 26 04:54:26 1999
Received: from io.worldonline.be (io.worldonline.be [212.233.1.146])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA64748
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 04:54:25 -0500 (EST)
(envelope-from mlennert@club.worldonline.be)
Received: from secr-tariat (dp48-239.worldonline.be [212.233.48.239])
by io.worldonline.be (8.8.5/8.8.5) with SMTP id KAA22422
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 10:53:07 +0100 (MET)
Message-Id: <3.0.6.32.19991126105554.0079bc10@pop3.worldonline.be>
X-Sender: fr018281@pop3.worldonline.be (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 26 Nov 1999 10:55:54 +0100
To: pgsql-general@postgresql.org
From: Moritz Lennert <mlennert@club.worldonline.be>
Subject: exporting tables from Postgres
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi !

I have a database at home on postgresql and I have to tranfer it to MS
Access at work.
Is there a way to export it with all the definitions ? If it is through
pg_dump, how do import it into Access ?
Is there a possibility to export single tables with field definitions (if I
understand correctly, copy doesn't export definitions) ?

Thanks !

Moritz

From bouncefilter Fri Nov 26 05:16:27 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id FAA69345
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 05:16:18 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 19625 invoked by uid 417); 26 Nov 1999 10:45:33 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 26 Nov 1999 10:45:33 -0000
Message-ID: <00f301bf37f7$41de4a00$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-list" <pgsql-general@hub.org>
Subject: adding users to a group
Date: Fri, 26 Nov 1999 11:14:34 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_00F0_01BF37FF.6B53B7A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

This is a multi-part message in MIME format.

------=_NextPart_000_00F0_01BF37FF.6B53B7A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

how can I add existing users to a group?

Joost Roeleveld

------=_NextPart_000_00F0_01BF37FF.6B53B7A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_00F0_01BF37FF.6B53B7A0--

From bouncefilter Fri Nov 26 05:52:27 1999
Received: from ara.zf.jcu.cz (zakkr@ara.zf.jcu.cz [160.217.161.4])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA74597
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 05:51:29 -0500 (EST)
(envelope-from zakkr@zf.jcu.cz)
Received: from localhost (zakkr@localhost)
by ara.zf.jcu.cz (8.9.3/8.9.3/Debian/GNU) with SMTP id LAA23121;
Fri, 26 Nov 1999 11:38:14 +0100
Date: Fri, 26 Nov 1999 11:38:14 +0100 (CET)
From: Karel Zak - Zakkr <zakkr@zf.jcu.cz>
To: "J. Roeleveld" <j.roeleveld@softhome.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] adding users to a group
In-Reply-To: <00f301bf37f7$41de4a00$8402a8c0@sentec.demon.nl>
Message-ID: <Pine.LNX.3.96.991126111746.21790A-100000@ara.zf.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 26 Nov 1999, J. Roeleveld wrote:

Hi,

how can I add existing users to a group?

Example (add user 'gogo' to group 'mygr'):

ALTER USER gogo WITH PASSWORD "QwEr" IN GOUP mygr;

SELECT * FROM pg_user;
-----> see usesysid for 'gogo'

UPDATE pg_group SET grolist='{1000}' WHERE groname='mygr';
------> where 1000 is usesysid for 'gogo'
(for more users in one group: '{1000,1001, .. }'

It is a little terrible, because this is incomplete in the PgSQL. (All it
is probably job for a ALTER/CREATE USER, but in the current PgSQL still
not). In version 7.0?

Karel

From bouncefilter Fri Nov 26 06:32:28 1999
Received: from hipernet.com.br (nautilus.hipernet.com.br [200.246.90.107])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA79669
for <pgsql-general@postgreSQL.org>;
Fri, 26 Nov 1999 06:32:24 -0500 (EST)
(envelope-from roberto@mha.com.br)
Received: from pc35.mha.com.br (e1025.hipernet.com.br [200.246.138.121])
by hipernet.com.br (8.9.3/8.9.3) with SMTP id JAA05158;
Fri, 26 Nov 1999 09:33:26 -0200 (EDT)
Message-Id: <3.0.5.32.19991126093108.007db2f0@pop.hipernet.com.br>
X-Sender: roberto@pop.hipernet.com.br
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Fri, 26 Nov 1999 09:31:08 -0200
To: Silvio Macedo <smacedo@ic.ac.uk>
From: Roberto Joao Lopes Garcia <roberto@mha.com.br>
Subject: Re: [GENERAL] Postgres on Ultrasparc
Cc: pgsql-general@postgreSQL.org
In-Reply-To: <Pine.LNX.4.10.9911260736010.803-100000@test133.ee.ic.ac.uk

Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 07:39 26/11/99 +0000, you wrote:

I use PostgreSQL 6.5.2 in an Netra UltraSparc Solaris 2.5 and it works very
fine.

Roberto

Hello folks!

I would very much like to know if anybody has any experience in running
Postgres on Linux, on a Ultrasparc machine. Any version of Postgres, any
version of the Linux Kernel, any model of Ultrasparc.

My system still halts completely when I run regression tests.

Any information ?

Thank you!

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
``````````````````````````````````````````````````````````````````````````
Silvio Emanuel Nunes Barbosa de Macedo

smacedo@ic.ac.uk smacedo@inescn.pt
Imperial College, University of London INESC Porto
Intelligent and Interactive Systems Telecom. and Multimedia
Exhibition Road, Pc da Republica, 93
London SW7 2AZ, England 4050-497 PORTO PORTUGAL
Tel:+44 171 5946323 Tel:+351 22 2094220

************

From bouncefilter Fri Nov 26 08:56:29 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id IAA95122
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 08:56:00 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 239 invoked by uid 417); 26 Nov 1999 14:25:15 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 26 Nov 1999 14:25:15 -0000
Message-ID: <014901bf3815$f2984f80$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-list" <pgsql-general@hub.org>
Subject: Corrupted Password-file
Date: Fri, 26 Nov 1999 14:55:45 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0146_01BF381E.516AEEC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

This is a multi-part message in MIME format.

------=_NextPart_000_0146_01BF381E.516AEEC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I just got a corrupted Password-File with PostgreSQL, blocking all =
ODBC-stuff.
Does anyone have any clue as to how this happened?

The error I got when trying to alter a password was that there was an =
error
at line 2.

Joost Roeleveld

------=_NextPart_000_0146_01BF381E.516AEEC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_0146_01BF381E.516AEEC0--

From bouncefilter Fri Nov 26 09:35:30 1999
Received: from charleston.softhome.net (qmailr@charleston.SoftHome.net
[204.144.231.41]) by hub.org (8.9.3/8.9.3) with SMTP id JAA09909
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 09:34:42 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 3025 invoked by uid 417); 26 Nov 1999 15:03:57 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtp.softhome.net with SMTP; 26 Nov 1999 15:03:57 -0000
Message-ID: <017c01bf381b$5a8066a0$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-list" <pgsql-general@hub.org>
Subject: Stuck while attempting to automate User adding to existing groups...
Date: Fri, 26 Nov 1999 15:34:30 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0179_01BF3823.BAED7C00"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

This is a multi-part message in MIME format.

------=_NextPart_000_0179_01BF3823.BAED7C00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I'm trying to write a function to make my life easier when adding user's =
to existing groups,
but I'm stuck.

I need to know how to add an Item to an array in a table.
eg. for this particular case:
in 'pg_group' there is an array called 'grolist', how do I add a number =
to that array?

Joost Roeleveld

ps. once I get this to work, I'll post the function on here....

------=_NextPart_000_0179_01BF3823.BAED7C00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_0179_01BF3823.BAED7C00--

From bouncefilter Fri Nov 26 12:49:33 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA38588
for <pgsql-general@postgreSQL.org>;
Fri, 26 Nov 1999 12:48:35 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id MAA15336
for pgsql-general@postgreSQL.org; Fri, 26 Nov 1999 12:39:25 -0500 (EST)
Received: from renoir.op.net (root@renoir.op.net [209.152.193.4])
by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id LAA13593
for <pgman@candle.pha.pa.us>; Fri, 26 Nov 1999 11:01:11 -0500 (EST)
Received: from depredador.sefes.es ([194.179.85.3]) by renoir.op.net
(o1/$Revision: 1.18 $) with ESMTP id KAA11099 for
<pgman@candle.pha.pa.us>; Fri, 26 Nov 1999 10:57:39 -0500 (EST)
Received: from perti.com ([195.77.50.22]) by depredador.sefes.es
(Netscape Mail Server v2.0) with SMTP id AAA12609
for <pgman@candle.pha.pa.us>; Fri, 26 Nov 1999 16:54:48 +0200
Received: (qmail 2346 invoked from network); 26 Nov 1999 17:49:54 -0000
Received: from e25.localnet.net (192.168.1.25)
by sl1.localnet.net with SMTP; 26 Nov 1999 17:49:54 -0000
Reply-To: <hcuevas@perti.com>
From: "Horaci Cuevas" <hcuevas@perti.com>
To: <pgman@candle.pha.pa.us>
Subject: PostgreSQL
Date: Fri, 26 Nov 1999 16:49:55 +0100
Message-ID: <NABBJFCKFCOHFBNGLGHOAEGDCDAA.hcuevas@perti.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by candle.pha.pa.us id LAA13593
Sender: pgman@candle.pha.pa.us

Hi!

I'm using PostgreSQL for a search-web based database, and i saw a missing
function mostly found in DB2 and others, where, you can get results from
a query having a WHERE condition to exist or not in another SQL sentence .

In DB2 is:

SELECT field1, field2 FROM tab1 WHERE field1 IN ( select field3 from tab2 )
or
SELECT field1, field2 FROM tab1 where field1 NOT IN ( select field3 from tab2 )

PostgreSQL already has that, but only allows to return 1 result, ex:

SELECT field1, field2 FROM tab1 where field1 =
( select field 3 from tab2 where id=1 )

Would be great if that where added to the TODO as a future Feature.

Thanks in Advance.
Horaci Cuevas.

From bouncefilter Fri Nov 26 11:15:31 1999
Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA26052;
Fri, 26 Nov 1999 11:14:59 -0500 (EST)
(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA15862;
Fri, 26 Nov 1999 11:13:44 -0500 (EST)
To: Mike Mascari <mascarm@mascari.com>
cc: Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-reply-to: Your message of Thu, 25 Nov 1999 23:26:02 -0500
<383E0BD9.F00E5C43@mascari.com>
Date: Fri, 26 Nov 1999 11:13:44 -0500
Message-ID: <15860.943632824@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Mike Mascari <mascarm@mascari.com> writes:

Well, I agree that it would be GREAT to be able to rollback DDL
statements. However, at the moment, failures during a transaction while
DDL statements occur usually require direct intervention by the user (in
the case of having to drop/recreate indexes) and often require the services
of the DBA, if filesystem intervention is necessary (i.e., getting rid of
partially dropped/created tables and their associated fileystem
files).

And forced commit after the DDL statement completes will improve that
how?

I see 3 scenarios:

(1) Disallow DDL statements in transactions
(2) Send NOTICE's asking for the user to not trigger the bug until the bugs
can be fixed -or-
(3) Have all DDL statements implicity commit any running transactions.

1, of course, stinks. 2 is the current state and would probably take
several releases before all DDL statement rollback bugs could be crushed

It's not an overnight project, for sure.

3, it seems to me, could be implemented in a day's
time, would prevent the various forms of data corruption people often post
to this list (GENERAL) about,

I don't believe either of those assumptions. We've had problems with
VACUUM's internal commit, and I don't think it'd be either quick or
inherently more reliable to apply the same model to all DDL commands.

A more significant point is that implicit commit is not a transparent
change; it will break applications. People use transaction blocks for
two reasons: (1) to define where to roll back to after an error, (2) to
ensure that the results of logically related updates become visible to
other backends atomically. Implicit commit destroys both of those
guarantees, even though only the first one is really related to the
implementation problem we are trying to solve.

As a user I'd be pretty unhappy if "SELECT ... INTO" suddenly became
"COMMIT; SELECT; BEGIN". Not only would that mean that updates made
by my transaction would become visible prematurely, but it might also
mean that the SELECT retrieves results it should not (ie, results from
xacts that were not committed when my xact started). Both of these
things could make my application logic fail in hard-to-find, hard-to-
reproduce-except-under-load ways.

So, although implicit commit might look like a convenient workaround at
the level of Postgres itself, it'd be a horrible loss of reliability
at the application level. I'd rather go with #1 (hard error) than
risk introducing transactional bugs into applications that use Postgres.

Since ORACLE has 70% of the RDBMS market, it is the de facto standard

Yes, and Windows is the de facto standard operating system. I don't use
Windows, and I'm not willing to follow Oracle's lead when they make a
bad decision...

regards, tom lane

From bouncefilter Fri Nov 26 14:52:34 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA84737;
Fri, 26 Nov 1999 14:52:19 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from ferrari (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id OAA02196;
Fri, 26 Nov 1999 14:49:38 -0500
Message-Id: <199911261949.OAA02196@corvette.mascari.com>
From: "Mike Mascari" <mascarm@mascari.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgreSQL.org>,
"PostgreSQL Developers List" <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Fri, 26 Nov 1999 14:48:20 -0500
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1161
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Tom Lane <tgl@sss.pgh.pa.us> writes:
Mike Mascari <mascarm@mascari.com> writes:

Well, I agree that it would be GREAT to be able to rollback DDL
statements. However, at the moment, failures during a transaction

while

DDL statements occur usually require direct intervention by the user

(in

the case of having to drop/recreate indexes) and often require the

services

of the DBA, if filesystem intervention is necessary (i.e., getting rid

partially dropped/created tables and their associated fileystem
files).

And forced commit after the DDL statement completes will improve that
how?

Because 99% of the instances of index and data corruption I've seen
have come from rolled-back DDL statements - usually because the on
disk representation no longer matches the system catalogue. A forced
commit on DDL changes against tables and indexes with access
exclusive locks will make that operation as close to "atomic" as
possible...

As a user I'd be pretty unhappy if "SELECT ... INTO" suddenly became
"COMMIT; SELECT; BEGIN". Not only would that mean that updates made
by my transaction would become visible prematurely, but it might also
mean that the SELECT retrieves results it should not (ie, results from
xacts that were not committed when my xact started). Both of these
things could make my application logic fail in hard-to-find, hard-to-
reproduce-except-under-load ways.

What does ORACLE do here?

So, although implicit commit might look like a convenient workaround at
the level of Postgres itself, it'd be a horrible loss of reliability
at the application level. I'd rather go with #1 (hard error) than
risk introducing transactional bugs into applications that use Postgres.

Since ORACLE has 70% of the RDBMS market, it is the de facto standard

Yes, and Windows is the de facto standard operating system. I don't use
Windows, and I'm not willing to follow Oracle's lead when they make a
bad decision...

regards, tom lane

So I guess I should file away my other suggestion to use DCOM as
the object technology of choice instead of CORBA? ;-)

From bouncefilter Fri Nov 26 15:10:34 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA87010;
Fri, 26 Nov 1999 15:09:35 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from lorc.wgcr.org ([207.144.78.58])
by www.wgcr.org (8.8.7/8.8.5) with SMTP id PAA00394;
Fri, 26 Nov 1999 15:09:12 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: Little to None
To: "Mike Mascari" <mascarm@mascari.com>, "Tom Lane" <tgl@sss.pgh.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Fri, 26 Nov 1999 15:04:20 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: "Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgresql.org>,
"PostgreSQL Developers List" <hackers@postgresql.org>
References: <199911261949.OAA02196@corvette.mascari.com>
In-Reply-To: <199911261949.OAA02196@corvette.mascari.com>
MIME-Version: 1.0
Message-Id: <99112615114107.00541@lorc.wgcr.org>
Content-Transfer-Encoding: 8bit

On Fri, 26 Nov 1999, Mike Mascari wrote:

Tom Lane <tgl@sss.pgh.pa.us> writes:

What does ORACLE do here?

Since ORACLE has 70% of the RDBMS market, it is the de facto standard

Yes, and Windows is the de facto standard operating system. I don't use
Windows, and I'm not willing to follow Oracle's lead when they make a
bad decision...

So I guess I should file away my other suggestion to use DCOM as
the object technology of choice instead of CORBA? ;-)

This is a Free Software project -- PostgreSQL is not bound by the decisions of
the 'market leader' any more than Linux is bound by the standards of Microsoft.

Having said that, at the same time, a run-time option to mimic Oracle's
behavior might be useful to all of those folk who are trying to port Oracle
applications over to PostgreSQL -- particularly if the SQL is compiled in.

However, someone who is interested in such an option will probably have to
implement it as well, as it certainly appears to not be a priority issue at
this point.

In cases where Oracle diverges from the SQL-92 or SQL3 standards, should we go
'standard' -- or go 'non-standard' -- the choice should be clear.

We are not competing directly against Oracle, AFAICT -- we serve a different
role altogether.

And I say that while I want an Oracle-specific application to run under
PostgreSQL.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Fri Nov 26 15:39:36 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA90548;
Fri, 26 Nov 1999 15:39:29 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from ferrari (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id PAA02358;
Fri, 26 Nov 1999 15:30:39 -0500
Message-Id: <199911262030.PAA02358@corvette.mascari.com>
From: "Mike Mascari" <mascarm@mascari.com>
To: "Lamar Owen" <lamar.owen@wgcr.org>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgresql.org>,
"PostgreSQL Developers List" <hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Fri, 26 Nov 1999 15:32:04 -0500
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1161
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

From: Lamar Owen <lamar.owen@wgcr.org>
On Fri, 26 Nov 1999, Mike Mascari wrote:

Tom Lane <tgl@sss.pgh.pa.us> writes:

What does ORACLE do here?

Since ORACLE has 70% of the RDBMS market, it is the de facto

standard

Yes, and Windows is the de facto standard operating system. I don't

use

Windows, and I'm not willing to follow Oracle's lead when they make a
bad decision...

So I guess I should file away my other suggestion to use DCOM as
the object technology of choice instead of CORBA? ;-)

This is a Free Software project -- PostgreSQL is not bound by the

decisions of

the 'market leader' any more than Linux is bound by the standards of

Microsoft.

The DCOM remark was just a joke ;-). My remark concerning ORACLE was in
response to Andreas' comment that implicit COMMITs of DDL statements was
absurd. I wanted to simply point out that, since ORACLE has 70% market
share,
most corporate database developers EXPECT their DDL statements to commit
their transactions (if they've RTFM). I also pointed out that it would be
GREAT
if PostgreSQL could successfully rollback DDL statements sanely (and thus
diverge from ORACLE). I guess I don't expect that to happen successfully
until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index names and their filesystem
counterparts and to be able to "undo" filesystem operations. That, it seems
to
me, will be a major undertaking and not going to happen any time soon...

I'll stop swinging at windmills now...

Mike Mascari

From bouncefilter Fri Nov 26 16:54:35 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA99066;
Fri, 26 Nov 1999 16:54:26 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from lorc.wgcr.org (dial-22.r11.ncbrvr.infoave.net [207.144.78.86])
by www.wgcr.org (8.8.7/8.8.5) with SMTP id QAA00486;
Fri, 26 Nov 1999 16:54:18 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: Little to None
To: "Mike Mascari" <mascarm@mascari.com>, "Tom Lane" <tgl@sss.pgh.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Fri, 26 Nov 1999 16:51:55 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: "Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgresql.org>,
"PostgreSQL Developers List" <hackers@postgresql.org>
References: <199911262030.PAA02358@corvette.mascari.com>
In-Reply-To: <199911262030.PAA02358@corvette.mascari.com>
MIME-Version: 1.0
Message-Id: <99112616564608.00541@lorc.wgcr.org>
Content-Transfer-Encoding: 8bit

On Fri, 26 Nov 1999, Mike Mascari wrote:

The DCOM remark was just a joke ;-). My remark concerning ORACLE was in
response to Andreas' comment that implicit COMMITs of DDL statements was
absurd. I wanted to simply point out that, since ORACLE has 70% market
share,

I did not see the response to Andreas, nor did I see Andreas' assertion that it
was absurd. My apologies.

counterparts and to be able to "undo" filesystem operations. That, it seems
to
me, will be a major undertaking and not going to happen any time soon...

Yes, that is true. As long as the storage manager relies on the filesystem for
table names, this will be a problem, unless filesystem deletions are delayed
until COMMIT, and filesystem creates are undone at a ROLLBACK.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Fri Nov 26 18:13:36 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id SAA08773
for pgsql-general@postgresql.org; Fri, 26 Nov 1999 18:13:00 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
Message-ID: <383F13FA.61B0A5CF@acrcorp.removethis.com>
From: Matthew Leo <matt@acrcorp.removethis.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
X-Newsgroups: comp.databases.postgresql.questions
Subject: Re: PostgreSQL
References: <7vn13b$bov2@imsp212.netvigator.com>
<381f33af.499056575@news.earthlink.net>
<7voii8$eap5@imsp212.netvigator.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 31
Date: Fri, 26 Nov 1999 18:12:58 -0500
X-Complaints-To: abuse@mediaone.net
X-Trace: wbnws01.ne.mediaone.net 943657978 24.218.54.77 (Fri,
26 Nov 1999 18:12:58 EST)
Organization: Road Runner
To: pgsql-questions@postgresql.org

I'm figuring this stuff out for myself rightnow. Here's what I've got
so far.

Visit this location to obtain the win32 ODBC driver:
http://www.insightdist.com/psqlodbc.

If you've created your database, make sure you edit the file pg_hba.conf
in your default database directory to include a line allowing
connections from your windows machines over IP (assuming you have a
network 192.168.0.*), for example:

host all 192.168.0.0 255.255.255.0 trust

to give completely unfettered access to everything, ignoring passwords.
Obviously, this is probably more permissive than you really want to be!
It's a start for config testing.

Assuming this works, be a little less trusing, change the line to:
host all 192.168.0.0 255.255.255.0 password pg_pwd

This requires a password and looks into the file pg_pwd in your database
directory for the password. You can run the command "pg_passwd pg_pwd"
to set passwords in this file.

That's as far as I've got. Other methods include kerberos, crypt (no
plaintext password transmitted -- a good idea), and ident (the ident
protocol -- don't know about this one). If anyone has any knowledge
about integrating with NT domains that would be great.

-Matt

From bouncefilter Fri Nov 26 20:02:37 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA19830
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 20:02:01 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:64030 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sDmq04925>; Sat, 27 Nov 1999 02:01:54 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11rWJz-0000CO-00; Sat, 27 Nov 1999 02:06:39 +0100
Date: Sat, 27 Nov 1999 02:06:39 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: "Jason C. Leach" <jcl@mail.ocis.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] can I do this.
In-Reply-To: <383CFFE0.2BB3C261@mail.ocis.net>
Message-ID: <Pine.LNX.4.20.9911261435470.344-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-11-25, Jason C. Leach mentioned:

I'm wondering if I can set a trigger or stored procedure that will run a
perl script?

Your best bet will probably be a wrapper function in C that will call the
Perl program via system(), for example.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Fri Nov 26 20:02:45 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA19853
for <pgsql-general@postgresql.org>;
Fri, 26 Nov 1999 20:02:31 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:64199 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sDmqJ4924>; Sat, 27 Nov 1999 02:02:13 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11rWKD-0000DD-00; Sat, 27 Nov 1999 02:06:53 +0100
Date: Sat, 27 Nov 1999 02:06:53 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] about speed
In-Reply-To: <001501bf3740$fb989a20$0100a8c0@sled.rpa.ryazan.su>
Message-ID: <Pine.LNX.4.20.9911261437450.344-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-11-25, Vovk G. Grigoriy mentioned:

Can any tell my, what will fastly - "SELECT ..." statement or function
doing "SELECT..."?

I am not sure, but it would seem that a function doing SELECT will do just
that: call SELECT. The only difference you would have is the function call
overhead. I'm not sure though to what extent the SQL in the function is
preparsed, but in general I never have seen this mentioned as a
performance-tuning measure.

I do query whith storage procedure in MS SQL, and what about postgresql?

We have user-defined functions, which cover some areas of stored
procedures, but not others. For example, functions can not return a set of
tuples. There are "stored procedure" threads all the time on these mailing
lists -- you are encouraged to look through them for the detailed answers.
Also, some of those things are being worked on for 7.0.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Fri Nov 26 20:02:37 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA19854
for <pgsql-general@hub.org>; Fri, 26 Nov 1999 20:02:31 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:64246 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sDmqO4930>; Sat, 27 Nov 1999 02:02:18 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11rWKN-0000Do-00; Sat, 27 Nov 1999 02:07:03 +0100
Date: Sat, 27 Nov 1999 02:07:03 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: "J. Roeleveld" <j.roeleveld@softhome.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] rule's and trigger's
In-Reply-To: <00c001bf374e$47f0bf80$8402a8c0@sentec.demon.nl>
Message-ID: <Pine.LNX.4.20.9911261447210.344-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-11-25, J. Roeleveld mentioned:

I was wondering if anyone knows what's being executed first,
a Rule on a view, or a trigger set to 'before <something>' on a view?

Eg. what's executed first? The RULE, or the TRIGGER?

The rules are done first. The reason is that the rules actually modify the
query before it gets to execution. In case of a view, a trigger would then
act on the query to the base table. Thus a trigger on a view might not
make too much sense.

See also the relevant chapters (39 & 41) in the Programmer's Guide.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Sat Nov 27 03:30:08 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA73441
for <pgsql-general@postgresql.org>;
Sat, 27 Nov 1999 03:29:35 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id DAA05787;
Sat, 27 Nov 1999 03:27:04 -0500
Sender: mascarm@mascari.com
Message-ID: <383F4FDE.71567C65@mascari.com>
Date: Fri, 26 Nov 1999 22:28:30 -0500
From: Mike Mascari <mascarm@mascari.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian Haney <brian@cybernaut.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] update view
References: <000401bf38af$c04bab40$8101a8c0@specter.fresno.cybernaut.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Brian Haney wrote:

I'm trying to update a table through a view and have read up on what
constitutes an 'updatable' view. I created a simple test case and cannot
get it to update the table through the view. In the transcript below,
notice that when I update the view, I get 'UPDATE 0' with no error message
or other complaints. What am I missing? Does PostgreSQL not support
updating through views?

It does, but you must supply the RULE for what should happen in the event of
an INSERT, UPDATE, or DELETE. See Chapter 35 in the Programmer's Guide - The
Postgres Rule System, the section entitled "Rules on INSERT, UPDATE and
DELETE".

Hope that helps,

Mike

From bouncefilter Sat Nov 27 03:19:08 1999
Received: from secure.cybernaut.com (secure.cybernaut.com [207.33.154.240])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA72580
for <pgsql-general@hub.org>; Sat, 27 Nov 1999 03:18:22 -0500 (EST)
(envelope-from brian@cybernaut.com)
Received: from specter (gatekeeper.fresno.cybernaut.com [24.30.110.76])
by secure.cybernaut.com (8.9.1a/8.9.1) with SMTP id AAA23262
for <pgsql-general@hub.org>; Sat, 27 Nov 1999 00:18:14 -0800
X-Authentication-Warning: secure.cybernaut.com: Host
gatekeeper.fresno.cybernaut.com [24.30.110.76] claimed to be
specter
From: "Brian Haney" <brian@cybernaut.com>
To: <pgsql-general@hub.org>
Subject: update view
Date: Sat, 27 Nov 1999 00:16:48 -0800
Message-ID: <000401bf38af$c04bab40$8101a8c0@specter.fresno.cybernaut.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

I'm trying to update a table through a view and have read up on what
constitutes an 'updatable' view. I created a simple test case and cannot
get it to update the table through the view. In the transcript below,
notice that when I update the view, I get 'UPDATE 0' with no error message
or other complaints. What am I missing? Does PostgreSQL not support
updating through views?

-- Brian Haney
brian@cybernaut.com

============================ BEGIN SAMPLE ========================

$ psql -f /tmp/viewtest test2
create table peanuts (
name text,
age int4,
height int4,
weight int4);
CREATE
insert into peanuts values ('Charlie Brown', 50, 24, 75);
INSERT 21228 1
insert into peanuts values ('Snoopy', 21, 18, 25);
INSERT 21229 1
insert into peanuts values ('Lucy van Pelt', 50, 27, 65);
INSERT 21230 1
insert into peanuts values ('Linus van Pelt', 50, 24, 75);
INSERT 21231 1
select * from peanuts;
name |age|height|weight
--------------+---+------+------
Charlie Brown | 50| 24| 75
Snoopy | 21| 18| 25
Lucy van Pelt | 50| 27| 65
Linus van Pelt| 50| 24| 75
(4 rows)

create view dogs as select * from peanuts where name = 'Snoopy';
CREATE
select * from dogs;
name |age|height|weight
------+---+------+------
Snoopy| 21| 18| 25
(1 row)

update dogs set age = 145;
UPDATE 0
select * from dogs;
name |age|height|weight
------+---+------+------
Snoopy| 21| 18| 25
(1 row)

EOF
$

From bouncefilter Sat Nov 27 12:34:15 1999
Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA24893
for <pgsql-general@hub.org>; Sat, 27 Nov 1999 12:33:45 -0500 (EST)
(envelope-from rison@biochemistry.ucl.ac.uk)
Received: from biochem.ucl.ac.uk (actually host bsmori1.biochem.ucl.ac.uk)
by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP;
Sat, 27 Nov 1999 17:33:29 +0000
Received: from bsmlx17.biochem.ucl.ac.uk (bsmlx17 [128.40.46.142]) by
biochem.ucl.ac.uk (8.9.2/8.9.1)
with ESMTP id RAA20086; Sat, 27 Nov 1999 17:33:40 GMT
Received: from localhost (rison@localhost)
by bsmlx17.biochem.ucl.ac.uk (8.9.3/8.6.6) with ESMTP id RAA19803;
Sat, 27 Nov 1999 17:40:25 GMT
X-Authentication-Warning: bsmlx17.biochem.ucl.ac.uk: rison owned process doing
-bs
Date: Sat, 27 Nov 1999 17:40:25 +0000 (GMT)
From: Stuart Rison <rison@biochemistry.ucl.ac.uk>
X-Sender: rison@bsmlx17
To: Peter Eisentraut <peter_e@gmx.net>
cc: "Jason C. Leach" <jcl@mail.ocis.net>, pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] can I do this.
In-Reply-To: <Pine.LNX.4.20.9911261435470.344-100000@localhost.localdomain>
Message-ID: <Pine.LNX.4.10.9911271738190.19797-100000@bsmlx17>
MIME-Version: 1.0
Content-Type: text/plain; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id MAA24913

Yes, but wasn't there talk -a little while back- of actually implementing
Perl functions directly (i.e. not via a C wrapper).

I remember there was a fair bit of support for doing so but I haven't
heard any more!

Anybody out there doing it? I'd really love it! I'd help but I only
"program" Perl... hence the request ;)

Cheers,

On Sat, 27 Nov 1999, Peter Eisentraut wrote:

On 1999-11-25, Jason C. Leach mentioned:

I'm wondering if I can set a trigger or stored procedure that will run a
perl script?

Your best bet will probably be a wrapper function in C that will call the
Perl program via system(), for example.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

************

From bouncefilter Sat Nov 27 17:38:18 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA78220
for <pgsql-general@hub.org>; Sat, 27 Nov 1999 17:37:19 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-67.ocis.net [209.52.173.245])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id OAA21104
for <pgsql-general@hub.org>; Sat, 27 Nov 1999 14:37:17 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <38405C66.48BAF530@mail.ocis.net>
Date: Sat, 27 Nov 1999 14:34:14 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: Mail to DB.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I've read that a few of you are putting email into a postgres DB. I'd
be interested in doing something similar. Would any of you care to
share the secret that allows sendmail to deposit the email to a db, or
how you get it from /var/spool/mail/mailbox into the table when new mail
arrives?

Thanks,
Jason

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

Debain!Linux!

From bouncefilter Sat Nov 27 18:45:16 1999
Received: from smtp.mweb.co.za (quantum.mweb.co.za [196.2.16.241])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA88719
for <pgsql-general@postgresql.org>;
Sat, 27 Nov 1999 18:44:35 -0500 (EST)
(envelope-from pleriche@hotmail.com)
Received: from [196.30.173.95] (helo=developer1)
by smtp.mweb.co.za with smtp (Exim 3.02 #2) id 11rrUJ-00042U-00
for pgsql-general@postgreSQL.org; Sun, 28 Nov 1999 01:42:44 +0200
Message-ID: <000801bf3930$fcdfc4c0$0100a8c0@developer1>
Reply-To: "Pierre le Riche" <pleriche@hotmail.com>
From: "Pierre le Riche" <pleriche@hotmail.com>
To: <pgsql-general@postgresql.org>
Subject:
Date: Sun, 28 Nov 1999 01:41:46 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0005_01BF3941.BB3DA4E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01BF3941.BB3DA4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

subscribe
end

------=_NextPart_000_0005_01BF3941.BB3DA4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_000_0005_01BF3941.BB3DA4E0--

From bouncefilter Sun Nov 28 00:34:46 1999
Received: from primetime.jtek.com (primetime.jtek.com [216.230.38.31])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA27482
for <pgsql-general@postgresql.org>;
Sun, 28 Nov 1999 00:34:01 -0500 (EST) (envelope-from jacobs@jtek.com)
Received: from dev.jtek.com (lsajca1-ar3-015-067.biz.dsl.gtei.net [4.3.15.67])
by primetime.jtek.com (8.9.3/8.9.3) with ESMTP id FAA26207
for <pgsql-general@postgresql.org>; Sun, 28 Nov 1999 05:34:00 GMT
Date: Sat, 27 Nov 1999 21:33:27 -0800 (PST)
From: Stan Jacobs <jacobs@jtek.com>
To: pgsql-general@postgresql.org
Subject: INT4 on Linux/2.2.9 (x86)
Message-ID: <Pine.LNX.4.10.9911272126190.1953-100000@dev.jtek.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,

I just installed PostgreSQL 6.5.3 on Linux 2.2.9 (Intel/x86) platform.
Everything went smoothly, but the regression tests failed for int2 and
int4 datatypes. Repeated tests produced the same results. Should I be
concerned that the SERIAL macros default to int4 for all their values?
Are int4 types corrupted or otherwise unavailable on this platform?

Sorry if this is in a FAQ somewhere... If so, I'd greatly appreciate a
pointer to the right direction. *smile*

Thanks,

- Stan -

From bouncefilter Sun Nov 28 06:32:50 1999
Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA66553
for <pgsql-general@postgreSQL.org>;
Sun, 28 Nov 1999 06:32:10 -0500 (EST)
(envelope-from jaco@gospelsjop.com)
Received: from gospelsjop.com ([212.83.89.116]) by relay01.chello.nl
(InterMail v4.01.00 201-232-112) with ESMTP
id <19991128113839.QHAV10258.relay01@gospelsjop.com>
for <pgsql-general@postgreSQL.org>; Sun, 28 Nov 1999 12:38:39 +0100
Sender: jaco
Message-ID: <384113FA.F95CBF2C@gospelsjop.com>
Date: Sun, 28 Nov 1999 12:37:30 +0100
From: Jaco de Groot <jaco@gospelsjop.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i486)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] drop/rename table and transactions
References: <3.0.5.32.19991126090804.008af890@pop.mecomb.po.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Is it possible to achieve your goals by using things like
"delete * from table1 where id!=stuffIwant" instead of dropping it?

Yes, I think I better use delete statements instead of drop statements
knowing PostgreSQL can't always handle drop/rename statements in
transactions correctly.

Jaco de Groot

From bouncefilter Sun Nov 28 06:39:50 1999
Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA67473
for <pgsql-general@postgreSQL.org>;
Sun, 28 Nov 1999 06:39:24 -0500 (EST)
(envelope-from jaco@gospelsjop.com)
Received: from gospelsjop.com ([212.83.89.116]) by relay01.chello.nl
(InterMail v4.01.00 201-232-112) with ESMTP
id <19991128114550.QHIO10258.relay01@gospelsjop.com>
for <pgsql-general@postgreSQL.org>; Sun, 28 Nov 1999 12:45:50 +0100
Sender: jaco
Message-ID: <384115AD.E9C8B29F@gospelsjop.com>
Date: Sun, 28 Nov 1999 12:44:45 +0100
From: Jaco de Groot <jaco@gospelsjop.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i486)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <14945.943599152@sss.pgh.pa.us> <383E0BD9.F00E5C43@mascari.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike Mascari wrote:

From an otherwise EXTREMELY happy user :-) (full smile...), I see 3

scenarios:

(1) Disallow DDL statements in transactions
(2) Send NOTICE's asking for the user to not trigger the bug until the bugs
can be fixed -or-
(3) Have all DDL statements implicity commit any running transactions.

I think 1 is the best solution as long as there are bugs concerning DDL
statements in transactions. It will prevent people from getting in
trouble. I've been in this trouble for months :-(. I'm using Java
Servlets to connect to PostgreSQL and I'm having DDL statements whitin
transactions wich sometimes cause an error. This error is hard to find
and solve if you don't know PostgreSQL has problems with DDL statements
in transactions. And if the error occures it doesn't simply crash 1
transaction or connection but it crashes all connections wich prevents
my website from running correctly until I've manualy fixed the problem
(mostly restarting PostgreSQL). To prevent others from getting in the
same trouble I'd like to propose that the next release of PosgreSQL
will dissalow DDL statements in transactions and notice the user this
is a feature wich is currently in development.

Jaco de Groot

From bouncefilter Sun Nov 28 16:23:34 1999
Received: from dravite.mint.net (dravite.mint.net [216.227.128.32])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA43705
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 16:23:17 -0500 (EST)
(envelope-from bsneed@mint.net)
Received: from mint.net (ddialup-r-71.mint.net [216.227.145.91])
by dravite.mint.net (8.9.3/8.9.3) with ESMTP id QAA13132
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 16:23:05 -0500
Sender: root@dravite.mint.net
Message-ID: <38419CE4.4D2EE243@mint.net>
Date: Sun, 28 Nov 1999 16:21:40 -0500
From: Bill Sneed <bsneed@mint.net>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Quoting/Escaping
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'd like to be able to find a book title that contain C++ in the
title....

select * from books where title ~* 'C++' doesn't work.

I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...

Any hints would be most appreciated....

....Thanks...

....Bill Sneed, Prospect, Maine....

From bouncefilter Sun Nov 28 17:35:35 1999
Received: from rabies.toodarkpark.org (caffeine@rabies.toodarkpark.org
[207.176.94.148]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA80433
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 17:35:19 -0500 (EST)
(envelope-from caffeine@toodarkpark.org)
Received: from localhost (caffeine@localhost)
by rabies.toodarkpark.org (8.8.8/8.8.8/Debian/GNU) with SMTP id
RAA13338; Sun, 28 Nov 1999 17:38:44 -0500
Date: Sun, 28 Nov 1999 22:38:44 +0000 (GMT)
From: Howie <caffeine@toodarkpark.org>
To: "Jason C. Leach" <jcl@mail.ocis.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] Mail to DB.
In-Reply-To: <38405C66.48BAF530@mail.ocis.net>
Message-ID: <Pine.LNX.3.96.991128223348.372i-100000@rabies.toodarkpark.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 27 Nov 1999, Jason C. Leach wrote:

hi,

I've read that a few of you are putting email into a postgres DB. I'd
be interested in doing something similar. Would any of you care to
share the secret that allows sendmail to deposit the email to a db, or
how you get it from /var/spool/mail/mailbox into the table when new mail
arrives?

a friend and i were just talking about this... you could use procmail to
spawn a program that inserts the data into pgsql. youd most likely want
to use LO's for the email body, storing To:, From:, Cc:, and Subject: in a
table ( for queries ).

---
Howie <caffeine@toodarkpark.org> URL: http://www.toodarkpark.org
"Tell a man that there are 400 billion stars and he'll believe you.
Tell him a bench has wet paint and he has to touch it."

From bouncefilter Sun Nov 28 17:19:34 1999
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA78120
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 17:19:23 -0500 (EST)
(envelope-from jrh@is.com.fj)
Received: from john (test2.is.com.fj [202.62.124.234])
by homer.is.com.fj (8.9.3/8.9.3) with SMTP id LAA29649
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 11:19:17 +1300 (FJDST)
Message-ID: <00a201bf39f6$a06d02e0$ea7c3eca@john.is.com.fj>
Reply-To: "John Henderson" <jrh@is.com.fj>
From: "John Henderson" <jrh@is.com.fj>
To: <pgsql-general@hub.org>
Subject: BSDI shared mem
Date: Mon, 29 Nov 1999 11:16:37 +1200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

Hi,
Perhaps this is useful for the FAQ as it was very difficult for me to
discover...

To increase shared mem and semaphores on BSDI
(courtesy of Sin'ichiro Miyatani on bsdi-users list)

In /usr/src/sys/sys/sem.h,

#ifndef SEMMNI
#define SEMMNI 10 /* # of semaphore identifiers */
#endif
#ifndef SEMMNS
#define SEMMNS 60 /* # of semaphores in system */
#endif

So 10 and 60 are default values. To increase # of semaphore, add next
line into kernel configuration file and recompile your kernel.

options "SEMMNI=XX"
options "SEMMNS=YY"

XX and YY are number you need.

And in /usr/src/sys/sys/shm.h:

#define SHMMAXPGS 1024 /* max hardware pages for shared memory */

It seems this value is hard coded and there is no kernel configuration
option.

John Henderson

From bouncefilter Sun Nov 28 23:15:39 1999
Received: from ns1.aprofile.com (h139-142-54-194.ed.fiberone.net
[139.142.54.194]) by hub.org (8.9.3/8.9.3) with SMTP id XAA28480
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 23:14:43 -0500 (EST)
(envelope-from darvin.zuch@autoprofile.com)
Received: (qmail 2742 invoked from network); 29 Nov 1999 04:12:57 -0000
Received: from h139-142-54-195.ed.fiberone.net (HELO zuchdarvinjava)
(139.142.54.195)
by h139-142-54-194.ed.fiberone.net with SMTP; 29 Nov 1999 04:12:57 -0000
From: "Darvin Zuch" <darvin.zuch@autoprofile.com>
To: "'Howie'" <caffeine@toodarkpark.org>,
"'Jason C. Leach'" <jcl@mail.ocis.net>
Cc: "'pgsql-list'" <pgsql-general@hub.org>
Subject: RE: [GENERAL] Mail to DB.
Date: Sun, 28 Nov 1999 21:19:49 -0700
Message-ID: <000501bf3a20$fa3e3ad0$0ddba8c0@zuchdarvinjava.aprofile.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.3.96.991128223348.372i-100000@rabies.toodarkpark.org>

I understand Oracle 8i does something like this (also acting as an FTP
backend).
You might want to scower their site for good ideas

Darvin Zuch

-----Original Message-----
From: owner-pgsql-general@postgreSQL.org
[mailto:owner-pgsql-general@postgreSQL.org]On Behalf Of Howie
Sent: Sunday, November 28, 1999 3:39 PM
To: Jason C. Leach
Cc: pgsql-list
Subject: Re: [GENERAL] Mail to DB.

On Sat, 27 Nov 1999, Jason C. Leach wrote:

hi,

I've read that a few of you are putting email into a postgres DB. I'd
be interested in doing something similar. Would any of you care to
share the secret that allows sendmail to deposit the email to a db, or
how you get it from /var/spool/mail/mailbox into the table when new mail
arrives?

---
Howie <caffeine@toodarkpark.org> URL: http://www.toodarkpark.org
"Tell a man that there are 400 billion stars and he'll believe you.
Tell him a bench has wet paint and he has to touch it."

************

From bouncefilter Sun Nov 28 23:38:39 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA31963
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 23:37:41 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.16.215]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Sun, 28 Nov 1999 22:29:52 -0600
Sender: ed
Message-ID: <3842037C.533C41CA@austin.rr.com>
Date: Sun, 28 Nov 1999 22:39:24 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bill Sneed <bsneed@mint.net>
CC: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Re: [GENERAL] Quoting/Escaping
References: <38419CE4.4D2EE243@mint.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bill Sneed wrote:

I'd like to be able to find a book title that contain C++ in the
title....

select * from books where title ~* 'C++' doesn't work.

I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...

Any hints would be most appreciated....

....Thanks...

....Bill Sneed, Prospect, Maine....

************

I think the 'like' operator may do what you seek.

create table t (w varchar);
insert into t (w) values ('C++');
insert into t (w) values ('C');
select * from t where w like 'C++';
w
---
C++
(1 row)

Cheers.
Ed

From bouncefilter Sun Nov 28 23:15:39 1999
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA28491
for <pgsql-general@hub.org>; Sun, 28 Nov 1999 23:14:54 -0500 (EST)
(envelope-from jrh@is.com.fj)
Received: from john (test2.is.com.fj [202.62.124.234])
by homer.is.com.fj (8.9.3/8.9.3) with SMTP id RAA03434
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 17:14:43 +1300 (FJDST)
Message-ID: <011801bf3a28$4a61f5e0$ea7c3eca@john.is.com.fj>
Reply-To: "John Henderson" <jrh@is.com.fj>
From: "John Henderson" <jrh@is.com.fj>
To: <pgsql-general@hub.org>
Subject: memory
Date: Mon, 29 Nov 1999 17:11:59 +1200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

Hi,
I could really use some help understanding where exactly the limits are in
my use of memory and how postgres uses memory.
I am running PostgreSQL 6.4 on BSDI 3.0 with 64M ram and 262M virtmem.
table sessions is 74M and 371K records

isfiji=> explain select user_name from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=12)
EXPLAIN

This query (above) works without a hitch from psql

isfiji=> explain select * from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=138)
EXPLAIN

The query above can access over 250M of memory according to top but dies
with either a seg fault or the latest, something called
"calloc: Cannot allocate memory"

I have had to set datasize to 256M which seems to be unrealistic. This table
is only 74M, it has a 15M index which the explain does not think is used.
Even if the entire table has to be sucked into mem and then duplicated
elsewhere in mem as a result this only accounts for 148M. Besides, is it
reaonable to require more than 256M of ram to copy a table from disk to
psql?

Having built this mass of data I don't seem to be able to do any useful
queries with it. Actually, just having problems with the query I want which
is
select user_name,sess_time,start, stop
from sessions
where date_part('epoch',start) between '$t1' and '$t2';

By the way, the following query from a PHP script works great, and because
it uses an index, very fast.
select date_trunc('minutes',sum(sess_time)) from
sessions where
user_name='$FORM{username}' and date_part('epoch',start)>'$t1' and
date_part('epoch',start)<'$t2'

The latter query is asking for 1 out of 3000 summaries approx.

Here are the questions...

1) Can someone explain how postgreSQL uses memory so that I can understand
what I should be doing here.
BTW, I am running postgres with -B 884. Can someone also explain how
postgres uses shared mem so that I can have a clue what would be a
reasonable setting.

2) Can any BSDI folk give me any tuning tips. I am especially interested to
hear from those who claim "some might tell you that we run equally well on
FreeBSD" or "BSD is the One True Code", of course all help is gratefully
received.

Thanks,
John Henderson

From bouncefilter Mon Nov 29 00:28:55 1999
Received: from candle.pha.pa.us (s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA39586;
Mon, 29 Nov 1999 00:27:46 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
AAA05829;
Mon, 29 Nov 1999 00:13:59 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911290513.AAA05829@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <199911262030.PAA02358@corvette.mascari.com> from Mike Mascari at
"Nov 26, 1999 03:32:04 pm"
To: Mike Mascari <mascarm@mascari.com>
Date: Mon, 29 Nov 1999 00:13:59 -0500 (EST)
CC: Lamar Owen <lamar.owen@wgcr.org>, Tom Lane <tgl@sss.pgh.pa.us>,
Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

if PostgreSQL could successfully rollback DDL statements sanely (and thus
diverge from ORACLE). I guess I don't expect that to happen successfully
until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index names and their filesystem
counterparts and to be able to "undo" filesystem operations. That, it seems
to
me, will be a major undertaking and not going to happen any time soon...

Ingres has table names that don't match on-disk file names, and it is a
pain to administer because you can't figure out what is going on at the
file system level. Table files have names like AAAHFGE.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 01:04:51 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA45617;
Mon, 29 Nov 1999 01:04:23 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id MAA26679;
Mon, 29 Nov 1999 12:59:23 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <3842163A.6AD7B1DE@krs.ru>
Date: Mon, 29 Nov 1999 12:59:22 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <199911290513.AAA05829@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

if PostgreSQL could successfully rollback DDL statements sanely (and thus
diverge from ORACLE). I guess I don't expect that to happen successfully
until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index names and their filesystem
counterparts and to be able to "undo" filesystem operations. That, it seems
to
me, will be a major undertaking and not going to happen any time soon...

Ingres has table names that don't match on-disk file names, and it is a
pain to administer because you can't figure out what is going on at the
file system level. Table files have names like AAAHFGE.

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Vadim

From bouncefilter Mon Nov 29 01:34:51 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA49940;
Mon, 29 Nov 1999 01:34:25 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
BAA07430;
Mon, 29 Nov 1999 01:09:41 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911290609.BAA07430@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <3842163A.6AD7B1DE@krs.ru> from Vadim Mikheev at "Nov 29,
1999 12:59:22 pm"
To: Vadim Mikheev <vadim@krs.ru>
Date: Mon, 29 Nov 1999 01:09:41 -0500 (EST)
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Wow, that is a major pain. Anyone else think so?

Using oid's instead of names may give us some ability to fix some other
bugs, though.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 01:18:51 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA47626;
Mon, 29 Nov 1999 01:18:20 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from ferrari (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id BAA19002;
Mon, 29 Nov 1999 01:15:07 -0500
Message-Id: <199911290615.BAA19002@corvette.mascari.com>
From: "Mike Mascari" <mascarm@mascari.com>
To: "Vadim Mikheev" <vadim@krs.ru>, "Bruce Momjian" <pgman@candle.pha.pa.us>
Cc: "Lamar Owen" <lamar.owen@wgcr.org>, "Tom Lane" <tgl@sss.pgh.pa.us>,
"Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgreSQL.org>,
"PostgreSQL Developers List" <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Mon, 29 Nov 1999 01:16:45 -0500
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1161
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Vadim Mikheev wrote:
Bruce Momjian wrote:

if PostgreSQL could successfully rollback DDL statements sanely (and

thus

diverge from ORACLE). I guess I don't expect that to happen

successfully

until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index names and their filesystem
counterparts and to be able to "undo" filesystem operations. That, it

seems

to
me, will be a major undertaking and not going to happen any time

soon...

Ingres has table names that don't match on-disk file names, and it is a
pain to administer because you can't figure out what is going on at the
file system level. Table files have names like AAAHFGE.

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Vadim

Will that aid in fixing a problem such as this:

session 1:

CREATE TABLE example1(value int4);
BEGIN;

session 2:

BEGIN;
ALTER TABLE example1 RENAME TO example2;

session 1:

INSERT INTO example1 VALUES (1);
END;
NOTICE: Abort Transaction and not in in-progress state
ERROR: Cannot write block 0 of example1 [test] blind

session 2:

END;
NOTICE: Abort Transaction and not in in-progress state
ERROR: Cannot write block 0 of example1 [test] blind

Just curious,

Mike (implicit commit) Mascari

From bouncefilter Mon Nov 29 01:32:52 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA49736;
Mon, 29 Nov 1999 01:32:25 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id NAA26907;
Mon, 29 Nov 1999 13:29:07 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <38421D32.90A2E2CB@krs.ru>
Date: Mon, 29 Nov 1999 13:29:06 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Mike Mascari <mascarm@mascari.com>
CC: Bruce Momjian <pgman@candle.pha.pa.us>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <199911290615.BAA19002@corvette.mascari.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike Mascari wrote:

Will that aid in fixing a problem such as this:

session 1:

CREATE TABLE example1(value int4);
BEGIN;

session 2:

BEGIN;
ALTER TABLE example1 RENAME TO example2;

session 1:

INSERT INTO example1 VALUES (1);
END;
NOTICE: Abort Transaction and not in in-progress state
ERROR: Cannot write block 0 of example1 [test] blind

session 2:

END;
NOTICE: Abort Transaction and not in in-progress state
ERROR: Cannot write block 0 of example1 [test] blind

Seems that oid file names will fix this...
Currently, each shared buffer description structure has
database/table names for the purposes of "blind" writes
(when backend cache hasn't entry for relation and so
bufmgr can't use cache to get names from oids).
ALTER TABLE ... RENAME renames relation file(s) but doesn't
change relation name inside shbuffers...

Mike (implicit commit) Mascari

-:)))

Vadim

From bouncefilter Mon Nov 29 01:30:51 1999
Received: from mx20.rmci.net (halcyon.rmci.net [205.162.184.63])
by hub.org (8.9.3/8.9.3) with SMTP id BAA49530
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 01:30:36 -0500 (EST)
(envelope-from webweaver@rmci.net)
Received: (qmail 10352 invoked from network); 29 Nov 1999 06:30:33 -0000
Received: from usr-boi-345.rmci.net (HELO chilly-willy) (206.159.113.221)
by halcyon.rmci.net with SMTP; 29 Nov 1999 06:30:33 -0000
Message-Id: <3.0.6.32.19991128233255.007b67d0@rmci.net>
X-Sender: webweaver@rmci.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sun, 28 Nov 1999 23:32:55 -0700
To: "John Henderson" <jrh@is.com.fj>, <pgsql-general@hub.org>
From: Ken Gunderson <webweaver@rmci.net>
Subject: Re: [GENERAL] memory
In-Reply-To: <011801bf3a28$4a61f5e0$ea7c3eca@john.is.com.fj>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 05:11 PM 11/29/99 +1200, John Henderson wrote:

Here are the questions...

1) Can someone explain how postgreSQL uses memory so that I can understand
what I should be doing here.
BTW, I am running postgres with -B 884. Can someone also explain how
postgres uses shared mem so that I can have a clue what would be a
reasonable setting.

2) Can any BSDI folk give me any tuning tips. I am especially interested to
hear from those who claim "some might tell you that we run equally well on
FreeBSD" or "BSD is the One True Code", of course all help is gratefully
received.

Thanks,
John Henderson

The FreeBSD port of postgres stipulates that you must compile kernel with
options SYSVSHM, SYSVSEM, & SYSVMSG. Don't know jack about BSDI or your
kernel config, but this might be something worth investigating.

Ciao--Ken
http://www.y2know.org/safari/

FreeBSD- Viagra for your server ;^)

From bouncefilter Mon Nov 29 01:56:51 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA54114;
Mon, 29 Nov 1999 01:56:07 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id NAA27008;
Mon, 29 Nov 1999 13:52:28 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <384222A9.5DE64B@krs.ru>
Date: Mon, 29 Nov 1999 13:52:25 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <199911290609.BAA07430@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Wow, that is a major pain. Anyone else think so?

Why it's so painful?
We can write utility to construct database dir with table names
symlinked to real table files -:)
Actually, I don't understand
for what would you need to know what is what, (c) -:)

Using oid's instead of names may give us some ability to fix some other
bugs, though.

Yes.

Vadim

From bouncefilter Mon Nov 29 02:34:52 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA58965;
Mon, 29 Nov 1999 02:34:23 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
CAA12955;
Mon, 29 Nov 1999 02:11:57 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911290711.CAA12955@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <384222A9.5DE64B@krs.ru> from Vadim Mikheev at "Nov 29,
1999 01:52:25 pm"
To: Vadim Mikheev <vadim@krs.ru>
Date: Mon, 29 Nov 1999 02:11:57 -0500 (EST)
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Wow, that is a major pain. Anyone else think so?

Why it's so painful?
We can write utility to construct database dir with table names
symlinked to real table files -:)
Actually, I don't understand
for what would you need to know what is what, (c) -:)

With Ingres, you can't just look at a file and know the table name, and
if you need to reload just one file from a tape, it is a royal pain to
know which file to bring back. I have said Ingres make things 100 times
harder for adminstrators by doing this.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 02:37:52 1999
Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA59420;
Mon, 29 Nov 1999 02:37:45 -0500 (EST)
(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id CAA13232;
Mon, 29 Nov 1999 02:33:13 -0500 (EST)
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: Vadim Mikheev <vadim@krs.ru>, Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-reply-to: Your message of Mon, 29 Nov 1999 01:09:41 -0500 (EST)
<199911290609.BAA07430@candle.pha.pa.us>
Date: Mon, 29 Nov 1999 02:33:13 -0500
Message-ID: <13230.943860793@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Bruce Momjian <pgman@candle.pha.pa.us> writes:

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Wow, that is a major pain. Anyone else think so?
Using oid's instead of names may give us some ability to fix some other
bugs, though.

Yes, and yes. I've been trying to nerve myself to propose that, because
it seems the only reasonable way to make rollback of RENAME TABLE and
DROP TABLE work safely. It'll be a pain in the neck for debugging and
admin purposes though.

Can we make some sort of usually-correct-but-not-guaranteed-correct
dump that shows which corresponds to what? Maybe something similar
to the textfile dump of pg_shadow that the postmaster uses for password
authentication? Then at least you'd have some shot at figuring out
which file was what in extremis...

regards, tom lane

From bouncefilter Mon Nov 29 02:59:52 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA63723;
Mon, 29 Nov 1999 02:58:56 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id OAA28203;
Mon, 29 Nov 1999 14:55:17 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <38423163.7EE18BB1@krs.ru>
Date: Mon, 29 Nov 1999 14:55:15 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <199911290711.CAA12955@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

Wow, that is a major pain. Anyone else think so?

Why it's so painful?
We can write utility to construct database dir with table names
symlinked to real table files -:)
Actually, I don't understand
for what would you need to know what is what, (c) -:)

With Ingres, you can't just look at a file and know the table name, and
if you need to reload just one file from a tape, it is a royal pain to
know which file to bring back. I have said Ingres make things 100 times
harder for adminstrators by doing this.

Moving table file to/off database dir separately is not right way for
backup/restore...

On-line/off-line full backup utility will copy _all_ database files to
_somewhere_ (tape etc) as well as on-line transaction logs
and pg_control (to know when was the last checkpoint made).
And to restore things after disk failure administrator will
have to copy _all_ files + logs (+logs made as incremental backup)
+ pg_control back and start postmaster.

Vadim

From bouncefilter Mon Nov 29 03:02:58 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA66043;
Mon, 29 Nov 1999 03:02:14 -0500 (EST) (envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id PAA28224;
Mon, 29 Nov 1999 15:00:45 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <384232AC.C546A8C0@krs.ru>
Date: Mon, 29 Nov 1999 15:00:44 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Bruce Momjian <pgman@candle.pha.pa.us>,
Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <13230.943860793@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.us> writes:

I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
database/table/index name using oid ...

Wow, that is a major pain. Anyone else think so?
Using oid's instead of names may give us some ability to fix some other
bugs, though.

Yes, and yes. I've been trying to nerve myself to propose that, because
it seems the only reasonable way to make rollback of RENAME TABLE and
DROP TABLE work safely. It'll be a pain in the neck for debugging and
admin purposes though.

So, no more nerves needed, Tom, yeh? -:)
It would be nice if someone else, not me, implement this...

Can we make some sort of usually-correct-but-not-guaranteed-correct
dump that shows which corresponds to what? Maybe something similar
to the textfile dump of pg_shadow that the postmaster uses for password
authentication? Then at least you'd have some shot at figuring out
which file was what in extremis...

As it was proposed - utility to create dir with database name
(in addition to dir with database oid where data really live)
and symlinks there: table_name --> ../db_oid/table_oid

Vadim

From bouncefilter Mon Nov 29 03:13:53 1999
Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA69906;
Mon, 29 Nov 1999 03:12:58 -0500 (EST)
(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id DAA13367;
Mon, 29 Nov 1999 03:10:35 -0500 (EST)
To: Vadim Mikheev <vadim@krs.ru>
cc: Bruce Momjian <pgman@candle.pha.pa.us>,
Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-reply-to: Your message of Mon, 29 Nov 1999 15:00:44 +0700
<384232AC.C546A8C0@krs.ru>
Date: Mon, 29 Nov 1999 03:10:34 -0500
Message-ID: <13365.943863034@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Vadim Mikheev <vadim@krs.ru> writes:

So, no more nerves needed, Tom, yeh? -:)
It would be nice if someone else, not me, implement this...

Um, I've got more than enough on my plate already...

Can we make some sort of usually-correct-but-not-guaranteed-correct
dump that shows which corresponds to what? Maybe something similar
to the textfile dump of pg_shadow that the postmaster uses for password
authentication? Then at least you'd have some shot at figuring out
which file was what in extremis...

As it was proposed - utility to create dir with database name
(in addition to dir with database oid where data really live)
and symlinks there: table_name --> ../db_oid/table_oid

I saw your message about that after sending mine. Yes, that'd be
a cool way of displaying the relationship. But the main thing to
remember is that it'd only be correct at steady-state when nothing
is being changed. If we tried to guarantee the mapping was correct
100% of the time, we'd be back to square one. Of course, that
makes the whole thing somewhat less useful for debugging purposes,
since Murphy's Law says that the times you really need to know
what's what are just when the system crashed in the middle of
a table rename ;-)

regards, tom lane

From bouncefilter Mon Nov 29 03:42:54 1999
Received: from its.uq.edu.au (root@brolga.cc.uq.edu.au [130.102.128.5])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA75814
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 03:41:59 -0500 (EST)
(envelope-from ccmcduff@its.uq.edu.au)
Received: from bunyip.cc.uq.edu.au (ccmcduff@bunyip.cc.uq.edu.au
[130.102.2.1])
by its.uq.edu.au (8.8.6/8.8.8) with ESMTP id SAA09766
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 18:41:56 +1000 (EST)
Message-Id: <199911290841.SAA09766@its.uq.edu.au>
X-Mailer: exmh version 2.1.0 09/18/1999
To: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Postgresql's "copy tablefrom STDIN" and DBD-Pg.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 29 Nov 1999 18:41:55 +1000
From: Rodney McDuff <ccmcduff@its.uq.edu.au>

Hi
Is there a way of using postgresql's "copy table from STDIN"
with DBD-Pg.

  +-----------------+------------------------------------------+
  |    _   ^   _    | Dr. Rodney McDuff                        |
  |   |\  /|\  /|   | Network Development, ITS                 |
  |     \  |  /     | The University of Queensland             |
  |      \ | /      | St. Lucia, Brisbane                      |
  |       \|/       | Queensland, Australia. 4072.             |
  |<-------+------->| TELEPHONE: +61 7 3365 8220               |
  |       /|\       | FACSIMILE: +61 7 3365 4477               |
  |      / | \      | EMAIL: mcduff@its.uq.edu.au              |
  |     /  |  \     |                                          |
  |   |/  \|/  \|   |        Ex ignorantia ad sapientiam       |
  |    -   v   -    |            Ex luce ad tenebras           |
  +-----------------+------------------------------------------+

From bouncefilter Mon Nov 29 08:39:57 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA19000
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 08:39:17 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id OAA06092;
Mon, 29 Nov 1999 14:38:22 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11sRve-0004Qj-00; Mon, 29 Nov 1999 14:37:22 +0000
Message-ID: <38428266.10C35257@sferacarta.com>
Date: Mon, 29 Nov 1999 14:40:54 +0100
From: jose soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: Brian Haney <brian@cybernaut.com>
CC: pgsql-general@hub.org
Subject: Re: [GENERAL] update view
References: <000401bf38af$c04bab40$8101a8c0@specter.fresno.cybernaut.com>
Content-Type: multipart/alternative;
boundary="------------D9A35D4C60E2D86C47406C9E"

--------------D9A35D4C60E2D86C47406C9E
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

You must create a rule to make a view updatable as in the following example:

drop table emp;
create table emp (
empno int,
ename char(20),
job char(12),
hiredate date,
sal money,
comm int,
deptno int,
level int,
mgr int
);

insert into emp values (7499,'ALLEN', 'SALESMAN', '20-FEB-81', '$1600', 300,
20,
insert into emp values (7698,'BLAKE', 'MANAGER', '01-MAY-81', '$2850',NULL,
30,
insert into emp values (7900,'JONES', 'CLERK', '03-DEC-81', '$0950',NULL,
30,
insert into emp values (7901,'KING', 'SALESMAN', '03-DEC-81', '$1950',NULL,
30,

drop view vista;
create view vista
as select empno, ename, job
from emp
where job='SALESMAN';

create rule "_UPDvista" as on update to vista
WHERE new.job='SALESMAN'
do instead
update emp set empno=new.empno, ename=new.ename,job=new.job
where empno=OLD.empno;

select * from vista;

update vista set empno=1 WHERE ename='ALLEN';

Jos�

Brian Haney ha scritto:

I'm trying to update a table through a view and have read up on what
constitutes an 'updatable' view. I created a simple test case and cannot
get it to update the table through the view. In the transcript below,
notice that when I update the view, I get 'UPDATE 0' with no error message
or other complaints. What am I missing? Does PostgreSQL not support
updating through views?

-- Brian Haney
brian@cybernaut.com

============================ BEGIN SAMPLE ========================

$ psql -f /tmp/viewtest test2
create table peanuts (
name text,
age int4,
height int4,
weight int4);
CREATE
insert into peanuts values ('Charlie Brown', 50, 24, 75);
INSERT 21228 1
insert into peanuts values ('Snoopy', 21, 18, 25);
INSERT 21229 1
insert into peanuts values ('Lucy van Pelt', 50, 27, 65);
INSERT 21230 1
insert into peanuts values ('Linus van Pelt', 50, 24, 75);
INSERT 21231 1
select * from peanuts;
name |age|height|weight
--------------+---+------+------
Charlie Brown | 50| 24| 75
Snoopy | 21| 18| 25
Lucy van Pelt | 50| 27| 65
Linus van Pelt| 50| 24| 75
(4 rows)

create view dogs as select * from peanuts where name = 'Snoopy';
CREATE
select * from dogs;
name |age|height|weight
------+---+------+------
Snoopy| 21| 18| 25
(1 row)

update dogs set age = 145;
UPDATE 0
select * from dogs;
name |age|height|weight
------+---+------+------
Snoopy| 21| 18| 25
(1 row)

EOF
$

************

--------------D9A35D4C60E2D86C47406C9E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<tt>You must create a rule to make a view updatable as in the following
example:</tt>
<br><tt></tt> <tt></tt>
<p><tt>drop table emp;</tt>
<br><tt>create table emp (</tt>
<br><tt>        empno   
int,</tt>
<br><tt>        ename   char(20),</tt>
<br><tt>        job     
char(12),</tt>
<br><tt>        hiredate date,</tt>
<br><tt>        sal     
money,</tt>
<br><tt>        comm    
int,</tt>
<br><tt>        deptno   int,</tt>
<br><tt>        level   
int,</tt>
<br><tt>        mgr     
int</tt>
<br><tt>);</tt><tt></tt>
<p><tt>insert into emp values (7499,'ALLEN', 'SALESMAN', '20-FEB-81', '$1600',
300, 20,</tt>
<br><tt>insert into emp values (7698,'BLAKE', 'MANAGER',  '01-MAY-81',
'$2850',NULL, 30,</tt>
<br><tt>insert into emp values (7900,'JONES', 'CLERK',   
'03-DEC-81', '$0950',NULL, 30,</tt>
<br><tt>insert into emp values (7901,'KING', 'SALESMAN', '03-DEC-81', '$1950',NULL,
30,</tt><tt></tt>
<p><tt>drop view vista;</tt>
<br><tt>create view vista</tt>
<br><tt>   as select empno, ename, job</tt>
<br><tt>      from emp</tt>
<br><tt>      where job='SALESMAN';</tt>
<br><tt></tt> <tt></tt>
<p><tt>create rule "_UPDvista" as on update to vista</tt>
<br><tt>    WHERE new.job='SALESMAN'</tt>
<br><tt>    do instead</tt>
<br><tt>    update emp set empno=new.empno, ename=new.ename,job=new.job</tt>
<br><tt>    where empno=OLD.empno;</tt><tt></tt>
<p><tt>select * from vista;</tt><tt></tt>
<p><tt>empno|ename              
|job</tt>
<br><tt>-----+--------------------+------------</tt>
<br><tt> 7499|ALLEN              
|SALESMAN</tt>
<br><tt> 7901|KING               
|SALESMAN</tt>
<br><tt>(2 rows)</tt><tt></tt>
<p><tt>update vista set empno=1 WHERE ename='ALLEN';</tt><tt></tt>
<p><tt>select * from vista;</tt>
<br><tt>empno|ename              
|job</tt>
<br><tt>-----+--------------------+------------</tt>
<br><tt> 7901|KING               
|SALESMAN</tt>
<br><tt>    1|ALLEN              
|SALESMAN</tt>
<br><tt>(2 rows)</tt>
<br><tt></tt> <tt></tt>
<p><tt>José</tt>
<br><tt></tt> 
<br><tt></tt> 
<br><tt></tt> <tt></tt>
<p><tt>Brian Haney ha scritto:</tt>
<blockquote TYPE=CITE>I'm trying to update a table through a view and have
read up on what
<br>constitutes an 'updatable' view.  I created a simple test case
and cannot
<br>get it to update the table through the view.  In the transcript
below,
<br>notice that when I update the view, I get 'UPDATE 0' with no error
message
<br>or other complaints.  What am I missing?  Does PostgreSQL
not support
<br>updating through views?
<p>-- Brian Haney
<br>brian@cybernaut.com
<p>============================ BEGIN SAMPLE ========================
<p>$ psql -f /tmp/viewtest test2
<br>create table peanuts (
<br>  name text,
<br>  age int4,
<br>  height int4,
<br>  weight int4);
<br>CREATE
<br>insert into peanuts values ('Charlie Brown', 50, 24, 75);
<br>INSERT 21228 1
<br>insert into peanuts values ('Snoopy', 21, 18, 25);
<br>INSERT 21229 1
<br>insert into peanuts values ('Lucy van Pelt', 50, 27, 65);
<br>INSERT 21230 1
<br>insert into peanuts values ('Linus van Pelt', 50, 24, 75);
<br>INSERT 21231 1
<br>select * from peanuts;
<br>name          |age|height|weight
<br>--------------+---+------+------
<br>Charlie Brown | 50|    24|    75
<br>Snoopy        | 21|   
18|    25
<br>Lucy van Pelt | 50|    27|    65
<br>Linus van Pelt| 50|    24|    75
<br>(4 rows)
<p>create view dogs as select * from peanuts where name = 'Snoopy';
<br>CREATE
<br>select * from dogs;
<br>name  |age|height|weight
<br>------+---+------+------
<br>Snoopy| 21|    18|    25
<br>(1 row)
<p>update dogs set age = 145;
<br>UPDATE 0
<br>select * from dogs;
<br>name  |age|height|weight
<br>------+---+------+------
<br>Snoopy| 21|    18|    25
<br>(1 row)
<p>EOF
<br>$
<p>************</blockquote>
</html>

--------------D9A35D4C60E2D86C47406C9E--

From bouncefilter Mon Nov 29 10:30:00 1999
Received: from shaked.cc.openu.ac.il (shaked.cc.openu.ac.il [147.233.145.65])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA34078
for <pgsql-general@postgreSQL.org>;
Mon, 29 Nov 1999 10:29:12 -0500 (EST)
(envelope-from herouth@oumail.openu.ac.il)
Received: from [147.233.159.109] (herouth@mac-herouth.pc.openu.ac.il
[147.233.159.109])
by shaked.cc.openu.ac.il (8.8.8/8.8.8) with ESMTP id RAA08951;
Mon, 29 Nov 1999 17:29:04 +0200 (IST)
X-Sender: herouth@shaked.cc.openu.ac.il
Message-Id: <l03130301b4684ba9482e@[147.233.159.109]>
In-Reply-To: <38419CE4.4D2EE243@mint.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 29 Nov 1999 17:29:39 +0200
To: Bill Sneed <bsneed@mint.net>
From: Herouth Maoz <herouth@oumail.openu.ac.il>
Subject: Re: [GENERAL] Quoting/Escaping
Cc: pgsql-general@postgreSQL.org

At 23:21 +0200 on 28/11/1999, Bill Sneed wrote:

I'd like to be able to find a book title that contain C++ in the
title....

select * from books where title ~* 'C++' doesn't work.

I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...

Any hints would be most appreciated....

testing=> select * from test1;
tx
------------------------------------------------
I prefer Java to C++ programming.
C++ is the most complicated of all OO langagues.
Java has less inheritance, but it is simpler.
(3 rows)
testing=> select * from test1 where tx ~* 'C\\+\\+';
tx
------------------------------------------------
I prefer Java to C++ programming.
C++ is the most complicated of all OO langagues.
(2 rows)

Rationale: the string is processed in two stages. One, when the query is
read by Postgres. The other, when the regexp engine reads it. It needs to
have backslashes before the pluses when it reaches the second stage. So the
backslashes have to pass intact through the first stage. Thus, they have to
be escaped themselves...

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herouth/personal/

From bouncefilter Mon Nov 29 14:15:03 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA66937;
Mon, 29 Nov 1999 14:14:20 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA29881;
Mon, 29 Nov 1999 14:08:41 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911291908.OAA29881@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <13230.943860793@sss.pgh.pa.us> from Tom Lane at "Nov 29,
1999 02:33:13 am"
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 29 Nov 1999 14:08:41 -0500 (EST)
CC: Vadim Mikheev <vadim@krs.ru>, Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Wow, that is a major pain. Anyone else think so?
Using oid's instead of names may give us some ability to fix some other
bugs, though.

Yes, and yes. I've been trying to nerve myself to propose that, because
it seems the only reasonable way to make rollback of RENAME TABLE and
DROP TABLE work safely. It'll be a pain in the neck for debugging and
admin purposes though.

I look at this and question the value of allowing such fancy things vs.
the ability to look at the directory and know exactly what table is
which file. Maybe we can use file names like 23423_mytable where 24323
is the table oid and mytable is the table name. That way, we can know
the table, and they are unique too to allow RENAME TABLE to work.

This doesn't solve Vadim's problem. His additional work would be to
write a line to the log file for each table create/delete saying I
deleted this table with this oid, and when reading back the log, he has
to record the oid_username combination and use that to translate his log
oids into actual filenames.

In fact, doesn't that information already appear in the WAL log as part
of pg_class changes? Or is the problem that the table changes happen
before the pg_class is committed?

Can we make some sort of usually-correct-but-not-guaranteed-correct
dump that shows which corresponds to what? Maybe something similar
to the textfile dump of pg_shadow that the postmaster uses for password
authentication? Then at least you'd have some shot at figuring out
which file was what in extremis...

That is OK, and a possible workaround if the above idea is not good.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 14:17:03 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA67358;
Mon, 29 Nov 1999 14:16:06 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA29896;
Mon, 29 Nov 1999 14:10:21 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911291910.OAA29896@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <38423163.7EE18BB1@krs.ru> from Vadim Mikheev at "Nov 29,
1999 02:55:15 pm"
To: Vadim Mikheev <vadim@krs.ru>
Date: Mon, 29 Nov 1999 14:10:20 -0500 (EST)
CC: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Moving table file to/off database dir separately is not right way for
backup/restore...

On-line/off-line full backup utility will copy _all_ database files to
_somewhere_ (tape etc) as well as on-line transaction logs
and pg_control (to know when was the last checkpoint made).
And to restore things after disk failure administrator will
have to copy _all_ files + logs (+logs made as incremental backup)
+ pg_control back and start postmaster.

No, I am talking about restoring a single table without doing the entire
database. If you recreate the table empty with the same structure,
shutdown db, mv table restored file to data directory and restart, table
not has old contents.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 14:18:10 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA67499;
Mon, 29 Nov 1999 14:17:26 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA29912;
Mon, 29 Nov 1999 14:12:04 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911291912.OAA29912@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <384232AC.C546A8C0@krs.ru> from Vadim Mikheev at "Nov 29,
1999 03:00:44 pm"
To: Vadim Mikheev <vadim@krs.ru>
Date: Mon, 29 Nov 1999 14:12:04 -0500 (EST)
CC: Tom Lane <tgl@sss.pgh.pa.us>, Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Can we make some sort of usually-correct-but-not-guaranteed-correct
dump that shows which corresponds to what? Maybe something similar
to the textfile dump of pg_shadow that the postmaster uses for password
authentication? Then at least you'd have some shot at figuring out
which file was what in extremis...

As it was proposed - utility to create dir with database name
(in addition to dir with database oid where data really live)
and symlinks there: table_name --> ../db_oid/table_oid

That's interesting, but I am concerned about the extra overhead of
creating two links for every file.

The other issue is if the table is accidentally dropped, how do you use
that utility to know the oid of the table that was removed?

I guess I like the OID_tablename idea.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 14:18:03 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA67514;
Mon, 29 Nov 1999 14:17:46 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA29927;
Mon, 29 Nov 1999 14:13:36 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911291913.OAA29927@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
In-Reply-To: <384232AC.C546A8C0@krs.ru> from Vadim Mikheev at "Nov 29,
1999 03:00:44 pm"
To: Vadim Mikheev <vadim@krs.ru>
Date: Mon, 29 Nov 1999 14:13:36 -0500 (EST)
CC: Tom Lane <tgl@sss.pgh.pa.us>, Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Lincoln Yeoh <lylyeoh@mecomb.com>,
pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

As it was proposed - utility to create dir with database name
(in addition to dir with database oid where data really live)
and symlinks there: table_name --> ../db_oid/table_oid

In fact, let me change what I suggested. Instead of 3434_mytable, I
suggest mytable_3434 so that the tables even appear in alphabetical
order in the directory. The _ may be the wrong character to separate
tablename from oid. Not sure, but we may need to use something that
can't be used in sql like mytable+234.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 14:19:03 1999
Received: from noc.unc.edu.ar (noc.unc.edu.ar [170.210.2.129])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA67647
for <pgsql-general@postgreSQL.org>;
Mon, 29 Nov 1999 14:18:40 -0500 (EST)
(envelope-from montes@noc.unc.edu.ar)
Received: from unc.edu.ar (localhost [127.0.0.1])
by noc.unc.edu.ar (8.9.1b+Sun/8.9.1) with ESMTP id QAA24031
for <pgsql-general@postgreSQL.org>;
Mon, 29 Nov 1999 16:18:59 -0300 (ARG)
Sender: montes@noc.unc.edu.ar
Message-ID: <3842D1A2.74E05CC1@unc.edu.ar>
Date: Mon, 29 Nov 1999 16:18:59 -0300
From: Miguel Montes <montes@noc.unc.edu.ar>
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-general@postgreSQL.org" <pgsql-general@postgreSQL.org>
Subject: Table corruption and other questions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi:
I'm using postgresql 6.5.1 with Linux Mandrake 6.1. I have two cases
of table corruption related to hardware failure. I have a server with
several clients generating nearly 10000 insertions a day. In both cases
one row of the table got corrupted, and caused the backend to crash when
trying to vacuum or execute pg_dump. SELECT * crashed the backend, too,
but we could do SELECTs on specific columns. The only way we could
recover the data was to do SELECT * FROM table WHERE id > n;
where n is the id of the corrupted row and was found by trial and error.

Is there a tool to repair a corrupted table?

Another question:
I'm using rules to log changes in several tables. I need this
because I have several servers in different locations, and I need to
synchronize them off line. The documentation isn't clear about the
relation between rules and permissions. The documentation i read implies
that a rule has the permissions of the user who is triggering its
execution. But it seems that this is not true, because a rule can insert
on a table over which the user has no privileges. This is exactly what i
need, but i'm not sure if this will be maintained in future versions. On
the other side, if a rule uses a function, it losts all its privileges,
and it can not insert in other tables if the user has no rights over
them.
Does anyone know if this is true, or i'm misunderstanding something?

TIA
Miguel Montes

From bouncefilter Mon Nov 29 16:03:04 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA82796
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 16:02:52 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61772 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sEibE10250>; Mon, 29 Nov 1999 22:02:08 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11sY0X-0000HM-00; Mon, 29 Nov 1999 22:06:49 +0100
Date: Mon, 29 Nov 1999 22:06:49 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Bill Sneed <bsneed@mint.net>
cc: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Re: [GENERAL] Quoting/Escaping
In-Reply-To: <38419CE4.4D2EE243@mint.net>
Message-ID: <Pine.LNX.4.20.9911292205430.658-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-11-28, Bill Sneed mentioned:

I'd like to be able to find a book title that contain C++ in the
title....

select * from books where title ~* 'C++' doesn't work.

I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...

select * from books where title ~[*] 'C\\+\\+'

The reason seems to be that the parser *and* the regexp routine do their
thing with unquoting.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Mon Nov 29 17:41:05 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA98842
for <pgsql-hackers@postgreSQL.org>;
Mon, 29 Nov 1999 17:40:36 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
RAA15736;
Mon, 29 Nov 1999 17:35:42 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911292235.RAA15736@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] Update of bitmask type
In-Reply-To: <383E32C9.7533ABF2@albourne.com> from Adriaan Joubert at "Nov 26,
1999 09:12:09 am"
To: Adriaan Joubert <a.joubert@albourne.com>
Date: Mon, 29 Nov 1999 17:35:42 -0500 (EST)
CC: Bruce Momjian <maillist@candle.pha.pa.us>,
Postgresql <pgsql-hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=UNKNOWN-8BIT
Content-Transfer-Encoding: 8bit

Bruce Momjian wrote:

I can integrate the type for you into the include/catalog files if
everyone agrees they want it as a standard type and not an contrib type.

Hi,

Attached are the C-routines that implement a BIT and BIT VARYING type.
I know Bruce said he would integrate them, but he is writing a book at
the moment as well, so if somebody can explain to me how to go about
integrating it, or would like to have a go, go ahead.

Applied. I am�embarrassed to say I had a copy from June still in my
mailbox.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 18:36:06 1999
Received: from datmail03.dat.com ([209.241.199.3])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA09598
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 18:35:36 -0500 (EST)
(envelope-from philip.culberson@dat.com)
Received: by datmail03.dat.com with Internet Mail Service (5.5.2448.0)
id <XF5B46FT>; Mon, 29 Nov 1999 15:34:57 -0800
Message-ID: <A95EFC3B707BD311986C00A0C9E95B6A04B2AE@datmail03.dat.com>
From: "Culberson, Philip" <philip.culberson@dat.com>
To: "'John Henderson'" <jrh@is.com.fj>, pgsql-general@hub.org
Subject: RE: [GENERAL] memory
Date: Mon, 29 Nov 1999 15:34:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

John,

Overrunning shared memory normally causes a different error, but this may be
worth mentioning. I noticed that you have set the number of buffers to 884.
Buffers are 8192 bytes each, so you would need shared memory to be
configured for at least 7,241,728 bytes. I am running on Solaris 2.6 and I
believe the default max size for shared memory is only about 512K. To allow
for 884 buffers, you would need to increase SHMMAX (in /etc/system) and
reboot the system.

Phil Culberson

-----Original Message-----
From: John Henderson [mailto:jrh@is.com.fj]
Sent: Monday, November 29, 1999 4:01 PM
To: pgsql-general@hub.org
Subject: [GENERAL] memory

Thanks to Ken Gunderson for his recommendation to try the FreeBSD config
options SYSVSHM, SYSVSEM AND SESVMSG. I did and they had no effect on
BSD/OS3.0
Here is the question again...
Hi,
I could really use some help understanding where exactly the limits are in
my use of memory and how postgres uses memory.
I am running PostgreSQL 6.4 on BSDI 3.0 with 64M ram and 262M virtmem.
table sessions is 74M and 371K records

isfiji=> explain select user_name from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=12)
EXPLAIN

This query (above) works without a hitch from psql

isfiji=> explain select * from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=138)
EXPLAIN

The query above can access over 250M of memory according to top but dies
with either a seg fault or the latest, something called
"calloc: Cannot allocate memory"

The latter query is asking for 1 out of 3000 summaries approx.

Here are the questions...

Thanks,
John Henderson

************

From bouncefilter Mon Nov 29 18:44:06 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA10618
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 18:43:24 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
SAA17946;
Mon, 29 Nov 1999 18:41:22 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911292341.SAA17946@candle.pha.pa.us>
Subject: Re: [GENERAL] memory
In-Reply-To: <008d01bf3ac5$f4c85040$ea7c3eca@john.is.com.fj> from John
Henderson at "Nov 30, 1999 12:00:46 pm"
To: John Henderson <jrh@is.com.fj>
Date: Mon, 29 Nov 1999 18:41:22 -0500 (EST)
CC: pgsql-general@hub.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

1) Can someone explain how postgreSQL uses memory so that I can understand
what I should be doing here.
BTW, I am running postgres with -B 884. Can someone also explain how
postgres uses shared mem so that I can have a clue what would be a
reasonable setting.

2) Can any BSDI folk give me any tuning tips. I am especially interested to
hear from those who claim "some might tell you that we run equally well on
FreeBSD" or "BSD is the One True Code", of course all help is gratefully
received.

I have run BSDI for years and never saw this problem. Not sure on a
cause, though.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 17:48:05 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA00190
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 17:48:01 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id RAA24593
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 17:42:34 -0600
Date: Mon, 29 Nov 1999 17:42:34 -0600 (CST)
From: <kaiq@realtyideas.com>
To: pgsql-general@hub.org
Subject: Re: [GENERAL] Re: PL/pgsql or C/C++
In-Reply-To: <99112416284908.07130@Gromit>
Message-ID: <Pine.LNX.4.10.9911291738440.19958-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

PL/pgsql ADN PL/tcl is safer -- that is the OFFICIAL reason, tho the real
reason may be comvenience.
As for PL/pgsql and PL/tcl: I asked before, no answer. I guess it is
portablility and existing codes. If you are a hero, use tcl, if not,
use pl/pgsql.

Kai

On Wed, 24 Nov 1999, Ian Phillips wrote:

On Wed, 24 Nov 1999, you wrote:

Date: Tue, 23 Nov 1999 12:19:53 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
Subject: PL/pgsql or C/C++

This is a general question expecting general answers. I've read the
documentation concerning triggers and functions, as well as the
documentation on the different languages you can use for driving these
triggers and functions. Aside from portability and the lack of having
to explicitly compiling a C/C++ library, what advantages does PL/pgsql
have over C/C++ or even PL/tcl?

^chewie

Ease of use is probably the biggest plus. For running a 'quick and dirty'
trigger, it's a lot easier than compiling a C library or (in my case) learning
TCL. I suppose if you already know TCL, there isn't that much point.

--
Ian Phillips
ian@comodo.net

"The Z80 - The Chip of the Seventies! Today!"

************

From bouncefilter Mon Nov 29 18:04:05 1999
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA03900
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 18:03:35 -0500 (EST)
(envelope-from jrh@is.com.fj)
Received: from john (test2.is.com.fj [202.62.124.234])
by homer.is.com.fj (8.9.3/8.9.3) with SMTP id MAA10037
for <pgsql-general@hub.org>; Tue, 30 Nov 1999 12:03:27 +1300 (FJDST)
Message-ID: <008d01bf3ac5$f4c85040$ea7c3eca@john.is.com.fj>
Reply-To: "John Henderson" <jrh@is.com.fj>
From: "John Henderson" <jrh@is.com.fj>
To: <pgsql-general@hub.org>
Subject: memory
Date: Tue, 30 Nov 1999 12:00:46 +1200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

isfiji=> explain select user_name from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=12)
EXPLAIN

This query (above) works without a hitch from psql

isfiji=> explain select * from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=138)
EXPLAIN

The query above can access over 250M of memory according to top but dies
with either a seg fault or the latest, something called
"calloc: Cannot allocate memory"

The latter query is asking for 1 out of 3000 summaries approx.

Here are the questions...

Thanks,
John Henderson

From bouncefilter Mon Nov 29 18:59:06 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA13131
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 18:58:53 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:64132 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sElAc4909>; Tue, 30 Nov 1999 00:58:32 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11salD-0000PF-00; Tue, 30 Nov 1999 01:03:11 +0100
Date: Tue, 30 Nov 1999 01:03:11 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Rodney McDuff <ccmcduff@its.uq.edu.au>
cc: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Re: [GENERAL] Postgresql's "copy tablefrom STDIN" and DBD-Pg.
In-Reply-To: <199911290841.SAA09766@its.uq.edu.au>
Message-ID: <Pine.LNX.4.20.9911292226160.658-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

Since COPY is PostgreSQL specific and DBD/DBI is supposed to be generic, I
don't think there's an easy way and you wouldn't be doing yourselves any
favours anyway.

If you insist on using COPY then you can use our native "Pg" Perl module,
which has functions equivalent to libpq's getline() and putline(), which
are necessary to handle COPY input and output. In the psql source code
(src/bin/psql/*.c) there are two functions called handleCopy{In|Out} that
handle this correctly, but I suspect in Perl it might be a lot easier
since you don't have to worry about memory allocation.

Good luck.

-Peter

On 1999-11-29, Rodney McDuff mentioned:

Hi
Is there a way of using postgresql's "copy table from STDIN"
with DBD-Pg.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Mon Nov 29 19:35:08 1999
Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA19541;
Mon, 29 Nov 1999 19:34:16 -0500 (EST) (envelope-from Inoue@tpf.co.jp)
Received: from cadzone ([126.0.1.40] (may be forged))
by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP
id JAA05979; Tue, 30 Nov 1999 09:29:19 +0900
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Vadim Mikheev" <vadim@krs.ru>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>,
"Lamar Owen" <lamar.owen@wgcr.org>,
"Lincoln Yeoh" <lylyeoh@mecomb.com>, <pgsql-general@postgreSQL.org>,
"PostgreSQL Developers List" <hackers@postgreSQL.org>
Subject: RE: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Tue, 30 Nov 1999 09:34:03 +0900
Message-ID: <000201bf3aca$9a3a9ac0$2801007e@cadzone.tpf.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <199911291912.OAA29912@candle.pha.pa.us>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal

Hi all,

I propose here that we stop the release of lock before end of transaction.
I have been suffering from the early release of lock.

Comments ?

If we don't allow DDL command inside transaction block,we won't need
the release before end of transaction.
If we allow DDL command inside transaction block,it may be a problem.
But are there any other principles which could guarantee consistency ?

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp

From bouncefilter Mon Nov 29 19:38:07 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA20145
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 19:37:40 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
TAA18785;
Mon, 29 Nov 1999 19:37:27 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911300037.TAA18785@candle.pha.pa.us>
Subject: Re: [GENERAL] memory
In-Reply-To: <00a301bf3acf$995fd8e0$ea7c3eca@john.is.com.fj> from John
Henderson at "Nov 30, 1999 01:09:45 pm"
To: John Henderson <jrh@is.com.fj>
Date: Mon, 29 Nov 1999 19:37:27 -0500 (EST)
CC: pgsql-general@hub.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

[Charset iso-8859-1 unsupported, filtering to ASCII...]

Thanks Philip and Bruce,
Re shared mem, I have increased the BSDI kernel conf from 1024 to 2048
shared mem pages. This allowed me to increase -B from 448 to 896 (not 884 my
error). These are the high values I can reach without postgres failing to
boot. This suggests my memory pages are around 3K - impossible but
interesting.

Pages are 4k.

I will try to increase sharedmem in the kernel after this msg. What does
postgres use shared mem for? How can I determine how much shared mem is
appropriate for the jobs I want to do?

BSDI has very small shared memory defaults.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Mon Nov 29 19:13:06 1999
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA15604
for <pgsql-general@hub.org>; Mon, 29 Nov 1999 19:12:31 -0500 (EST)
(envelope-from jrh@is.com.fj)
Received: from john (test2.is.com.fj [202.62.124.234])
by homer.is.com.fj (8.9.3/8.9.3) with SMTP id NAA18176
for <pgsql-general@hub.org>; Tue, 30 Nov 1999 13:12:28 +1300 (FJDST)
Message-ID: <00a301bf3acf$995fd8e0$ea7c3eca@john.is.com.fj>
Reply-To: "John Henderson" <jrh@is.com.fj>
From: "John Henderson" <jrh@is.com.fj>
To: <pgsql-general@hub.org>
Subject: memory
Date: Tue, 30 Nov 1999 13:09:45 +1200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

Thanks Philip and Bruce,
Re shared mem, I have increased the BSDI kernel conf from 1024 to 2048
shared mem pages. This allowed me to increase -B from 448 to 896 (not 884 my
error). These are the high values I can reach without postgres failing to
boot. This suggests my memory pages are around 3K - impossible but
interesting.

I will try to increase sharedmem in the kernel after this msg. What does
postgres use shared mem for? How can I determine how much shared mem is
appropriate for the jobs I want to do?

Just for interest sake, the query
isfiji=> select user_name,sess_time,start, stop into temp0
isfiji-> from sessions where user_name >= 'z' and date_part('epoch',start)
isfiji-> between '941371199' and '943959600';
SELECT

Works OK. It takes a little longer than a query that just asks to match a
username (user_name='axis') but that is to be expected.

However,
isfiji=> explain select * from sessions where user_name >= '';
NOTICE: QUERY PLAN:
Index Scan using sessions_user_name_idx on sessions (cost=9838.32
size=123907 w
idth=138)
EXPLAIN
isfiji=> select * from sessions where user_name >= '';
calloc: Cannot allocate memory

This last query chugs along for a long time consuming more and more memory
until it finally runs out somewhere areound 256M which is where my datasize
is set.

Question: Am I wrong to expect postgreSQL to be able to do this query given
the resources at my disposal. To recap, I have 262M virt ram, 64M ram, the
table is ~74M with ~300K rows and I want to select * from table where
condition which should yield about half of the records.

TIA,
John

From bouncefilter Mon Nov 29 23:34:10 1999
Received: from host67-160.student.udel.edu (host67-160.student.udel.edu
[128.175.67.160]) by hub.org (8.9.3/8.9.3) with SMTP id XAA77598
for <pgsql-general@postgresql.org>;
Mon, 29 Nov 1999 23:33:39 -0500 (EST)
(envelope-from hovinen@webinbox.com)
Received: (qmail 30677 invoked from network); 30 Nov 1999 04:33:41 -0000
Received: from localhost (127.0.0.1)
by localhost with SMTP; 30 Nov 1999 04:33:41 -0000
Date: Mon, 29 Nov 1999 23:33:41 -0500 (EST)
From: Bradford Hovinen <hovinen@webinbox.com>
X-Sender: hovinen@host67-160.student.udel.edu
To: pgsql-general@postgresql.org
Subject: SQL error in PostgreSQL 6.5.3
Message-ID:
<Pine.LNX.4.04.9911292326120.30671-100000@host67-160.student.udel.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am trying to enter the following query from a Perl script:

insert into messages (subject, cc_addr, priority, owner_id, date_sent,
reply_to_addr, to_addr, date_stored, body, from_addr, id) values ('Re:
Unplugging pessimism', '', '3', '1048578', 'Thu, 07 Oct 1999 08:04:46
-0700', '', 'Peter Herz <peter@websocietyinc.com>', 'now', 'Thanks Peter
-- and thanks for passing that on to Slashdot. Glad you liked
it, it\'s a very rich topic.

Janelle

----------

From: Peter Herz <peter@websocietyinc.com>
To: janelle@salon.com
Subject: Unplugging pessimism
Date: Thu, Oct 7, 1999, 2:38 AM

Janelle,

Wonderful article! I especially enjoyed your inference towards the end.

- Peter Herz

', '"Janelle Brown" <janelle@mail.salonmagazine.com>', '1048628')

When I run it from the Perl script, it results in the error `parameter
unknown'. However, when I paste it in an xterm and invoke it in the
command line client, it works perfectly. Any ideas what might be causing
that?

I'm running PostgreSQL 6.5.3 with DBI 1.06 and DBD::Pg 0.93 on Perl
5.00503 all on Red Hat Linux 6.0. Thanks in advance for your help.

-Bradford Hovinen

"Prudence is a rich, ugly old maid courted by Incapacity."

- William Blake, "Proverbs of Hell," 1793

From bouncefilter Mon Nov 29 23:50:11 1999
Received: from host67-160.student.udel.edu (host67-160.student.udel.edu
[128.175.67.160]) by hub.org (8.9.3/8.9.3) with SMTP id XAA79712
for <pgsql-general@postgresql.org>;
Mon, 29 Nov 1999 23:49:14 -0500 (EST)
(envelope-from hovinen@webinbox.com)
Received: (qmail 30842 invoked from network); 30 Nov 1999 04:49:16 -0000
Received: from localhost (127.0.0.1)
by localhost with SMTP; 30 Nov 1999 04:49:16 -0000
Date: Mon, 29 Nov 1999 23:49:16 -0500 (EST)
From: Bradford Hovinen <hovinen@webinbox.com>
X-Sender: hovinen@host67-160.student.udel.edu
To: pgsql-general@postgreSQL.org
Subject: SQL error in PostgreSQL 6.5.3
Message-ID:
<Pine.LNX.4.04.9911292349010.30840-100000@host67-160.student.udel.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am trying to enter the following query from a Perl script:

Janelle

----------

From: Peter Herz <peter@websocietyinc.com>
To: janelle@salon.com
Subject: Unplugging pessimism
Date: Thu, Oct 7, 1999, 2:38 AM

Janelle,

Wonderful article! I especially enjoyed your inference towards the end.

- Peter Herz

', '"Janelle Brown" <janelle@mail.salonmagazine.com>', '1048628')

I'm running PostgreSQL 6.5.3 with DBI 1.06 and DBD::Pg 0.93 on Perl
5.00503 all on Red Hat Linux 6.0. Thanks in advance for your help.

-Bradford Hovinen

"Prudence is a rich, ugly old maid courted by Incapacity."

- William Blake, "Proverbs of Hell," 1793

From bouncefilter Tue Nov 30 01:23:11 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA93219
for <pgsql-hackers@postgreSQL.org>;
Tue, 30 Nov 1999 01:23:10 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id IAA29035; Tue, 30 Nov 1999 08:27:09 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
IAA02511; Tue, 30 Nov 1999 08:23:05 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <38436D49.16D5580F@albourne.com>
Date: Tue, 30 Nov 1999 08:23:05 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Postgresql <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] Update of bitmask type
References: <199911292235.RAA15736@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

Bruce Momjian wrote:

I can integrate the type for you into the include/catalog files if
everyone agrees they want it as a standard type and not an contrib type.

Hi,

Attached are the C-routines that implement a BIT and BIT VARYING type.
I know Bruce said he would integrate them, but he is writing a book at
the moment as well, so if somebody can explain to me how to go about
integrating it, or would like to have a go, go ahead.

Applied. I am embarrassed to say I had a copy from June still in my
mailbox.

Don't be: they've been ready for a while, but I had to recheck them.
When BIT and BIT VARYING are properly integrated, do I need to do
something about regression tests?

Adriaan

From bouncefilter Tue Nov 30 01:31:12 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA94288
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 01:30:50 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id IAA29061; Tue, 30 Nov 1999 08:34:49 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
IAA02516; Tue, 30 Nov 1999 08:30:42 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <38436F12.93D74DC7@albourne.com>
Date: Tue, 30 Nov 1999 08:30:42 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Miguel Montes <montes@noc.unc.edu.ar>
CC: "pgsql-general@postgreSQL.org" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Table corruption and other questions
References: <3842D1A2.74E05CC1@unc.edu.ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Miguel Montes wrote:

I'm using postgresql 6.5.1 with Linux Mandrake 6.1. I have two cases
of table corruption related to hardware failure.

If the table itself is really messed up it can be tough to fix.
Sometimes it is possible to do a pg_dump of the table and reload --
otherwise it is a restore from the back-ups.

However, if you have indexes on the table, try dropping them all and
re-building them. I have never actually seen a corrupted table, but
index corruption with Postgres does occur. Also check for inidexes that
you may not have knowingly created, such as *_pkey or *_key ffor
primary_key or unique fields.

Hope this helps and good luck,

Adriaan

From bouncefilter Tue Nov 30 02:06:13 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA98207
for <pgsql-hackers@postgreSQL.org>;
Tue, 30 Nov 1999 02:05:44 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
BAA11308;
Tue, 30 Nov 1999 01:33:48 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911300633.BAA11308@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [GENERAL] Update of bitmask type
In-Reply-To: <38436D49.16D5580F@albourne.com> from Adriaan Joubert at "Nov 30,
1999 08:23:05 am"
To: Adriaan Joubert <a.joubert@albourne.com>
Date: Tue, 30 Nov 1999 01:33:48 -0500 (EST)
CC: Postgresql <pgsql-hackers@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Applied. I am embarrassed to say I had a copy from June still in my
mailbox.

Don't be: they've been ready for a while, but I had to recheck them.
When BIT and BIT VARYING are properly integrated, do I need to do
something about regression tests?

Yes, we will need them to be added to the regression tests. We can use
your test/ directory as a source for that.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 30 03:34:13 1999
Received: from smtp.bmi.net (IDENT:root@smtp.bmi.net [204.57.191.31])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA12847
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 03:33:43 -0500 (EST) (envelope-from jscott@bmi.net)
Received: from titan350 (dme-19.bmi.net [206.63.146.19])
by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with SMTP id AAA16024
for <pgsql-general@postgreSQL.org>; Tue, 30 Nov 1999 00:33:35 -0800
Message-Id: <199911300833.AAA16024@smtp.bmi.net>
X-Sender: jscott@mail.bmi.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Tue, 30 Nov 1999 00:32:53 -0800
To: pgsql-general@postgreSQL.org
From: Jesse Scott <jscott@bmi.net>
Subject: Sorting a table...
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hello all, I'm new to this list so forgive me if this question get's asked
a lot. (I did search the archives...)

I have a table of users where I store some basic info along with all my
authentication stuff. I wrote a web interface in PHP3 for viewing and
modifying this table, my PHP page just goes through the table sequentially
from row 0 till the end displaying a good portion of the info on each line.
Then, using radio buttons you select the user and the desired action,
click a button and then do your editing. Once the user has completed the
editing, I perform an UPDATE on that row with the new values, but now that
row is moved to the end of the table, making the page that lists the users
list them out of order (one of the fields is a sequential ID number). Is
there anyway to do a "sort by" or something similar? Or do I need to set
the ID number to be some sort of index type?

Any help would be appreciated.

TIA!

-Jesse

From bouncefilter Tue Nov 30 09:09:53 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA71856
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 09:08:44 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11snwz-0003CM-00
for pgsql-general@postgresql.org; Tue, 30 Nov 1999 14:08:13 +0000
Date: Tue, 30 Nov 1999 14:08:13 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: pgsql-general@postgresql.org
Subject: Executing external scripts
Message-ID: <Pine.BSO.4.10.9911301402590.6506-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

I've been doing some reading through the documentation and the archives of
this list but have not got very far yet.

I want to be able to create a trigger that when fired will execute an
external script. I may require arguments to be passed to the script from
the trigger.

I can't find a definate yes/no as to whether this can actually be done or
not in Postgresql 6.5.* - does anybody know?

Looking over the functions section, I might be able to do what I need to
do using one of the languages. However, I don't know C, and it does not
apply to what I'm doing anyway. I need to use Perl, but this means writing
a procedural language handler, which has to be done in C, which I don't
really know..... :(

Has anybody written, or knows of the existence of, a PL for Perl for
Postgresql?

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Tue Nov 30 10:01:48 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id KAA79626
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 10:00:30 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Vessla.DoCS.UU.SE (e99re41@Vessla.DoCS.UU.SE [130.238.9.188])
by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP id QAA27242;
Tue, 30 Nov 1999 16:00:25 +0100
Received: from localhost (e99re41@localhost) by Vessla.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id QAA13064;
Tue, 30 Nov 1999 16:00:23 +0100
X-Authentication-Warning: Vessla.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Tue, 30 Nov 1999 16:00:23 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Mark Jewiss <Mark.Jewiss@knowledge.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Executing external scripts
In-Reply-To: <Pine.BSO.4.10.9911301402590.6506-100000@office.knowledge.com>
Message-ID: <Pine.GSO.4.02A.9911301558270.12975-100000@Vessla.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 30 Nov 1999, Mark Jewiss wrote:

I want to be able to create a trigger that when fired will execute an
external script. I may require arguments to be passed to the script from
the trigger.

I can't find a definate yes/no as to whether this can actually be done or
not in Postgresql 6.5.* - does anybody know?

The definite answer to this is no, not straightforwardly. You will have to
write a C wrapper function.

While this sure sounds like a neat feature to have, I think there are too
many potential headaches.

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Nov 30 10:04:18 1999
Received: from crystalsugar.com ([207.0.65.31])
by hub.org (8.9.3/8.9.3) with SMTP id KAA80092
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 10:03:37 -0500 (EST)
(envelope-from danderso@crystalsugar.com)
Received: from JCEDO-Message_Server by crystalsugar.com
with Novell_GroupWise; Tue, 30 Nov 1999 09:01:14 -0600
Message-Id: <s843925a.014@crystalsugar.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.2.1
Date: Tue, 30 Nov 1999 09:00:55 -0600
From: "Dale Anderson" <danderso@crystalsugar.com>
To: <pgsql-general@postgreSQL.org>
Subject: PGSQL C Interface
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-7
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id KAC80130

When compiling the test C program for Postgres, I get the following errors. Can anyone help me with what the error might be. I have included th error message when compiling, and the source code ofr the tes.

Thanks in advance,
Dale.

$ gcc -I/usr/include/pgsql dba.c -o dba
/tmp/cca257351.o: In function `exit_nicely':
/tmp/cca257351.o(.text+0x8): undefined reference to `PQfinish'
/tmp/cca257351.o: In function `main':
/tmp/cca257351.o(.text+0x62): undefined reference to `PQsetdbLogin'
/tmp/cca257351.o(.text+0x73): undefined reference to `PQstatus'
/tmp/cca257351.o(.text+0x9c): undefined reference to `PQerrorMessage'
/tmp/cca257351.o(.text+0xce): undefined reference to `PQexec'
/tmp/cca257351.o(.text+0xe5): undefined reference to `PQresultStatus'
/tmp/cca257351.o(.text+0x10f): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x127): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x138): undefined reference to `PQexec'
/tmp/cca257351.o(.text+0x14f): undefined reference to `PQresultStatus'
/tmp/cca257351.o(.text+0x177): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x18f): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x1a0): undefined reference to `PQexec'
/tmp/cca257351.o(.text+0x1b7): undefined reference to `PQresultStatus'
/tmp/cca257351.o(.text+0x1df): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x1f7): undefined reference to `PQnfields'
/tmp/cca257351.o(.text+0x21d): undefined reference to `PQfname'
/tmp/cca257351.o(.text+0x255): undefined reference to `PQntuples'
/tmp/cca257351.o(.text+0x289): undefined reference to `PQgetvalue'
/tmp/cca257351.o(.text+0x2c1): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x2d2): undefined reference to `PQexec'
/tmp/cca257351.o(.text+0x2e3): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x2f4): undefined reference to `PQexec'
/tmp/cca257351.o(.text+0x305): undefined reference to `PQclear'
/tmp/cca257351.o(.text+0x311): undefined reference to `PQfinish'

�---------------[ CODE ]------------------------------------------------------------

/*
* testlibpq.c Test the C version of Libpq, the Postgres frontend
* library.
*
*
*/

#include <stdio.h>
#include "/usr/include/pgsql/postgres.h"
#include "/usr/include/pgsql/libpq-fe.h"
#include "/usr/include/pgsql/libpq/pqcomm.h"

void exit_nicely(PGconn *conn)
{
PQfinish(conn);
exit(1);
}

main()
{
char *pghost,
*pgport,
*pgoptions,
*pgtty;
char *dbName;
int nFields;
int i,
j;

/* FILE *debug; */

PGconn *conn;
PGresult *res;

/*
* begin, by setting the parameters for a backend connection if the
* parameters are null, then the system will try to use reasonable
* defaults by looking up environment variables or, failing that,
* using hardwired constants
*/
pghost = NULL; /* host name of the backend server */
pgport = NULL; /* port of the backend server */
pgoptions = NULL; /* special options to start up the backend
* server */
pgtty = NULL; /* debugging tty for the backend server */
dbName = "ff";

/* make a connection to the database */
conn = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName);

/*
* check to see that the backend connection was successfully made
*/
if (PQstatus(conn) == CONNECTION_BAD)
{
fprintf(stderr, "Connection to database '%s' failed.\n", dbName);
fprintf(stderr, "%s", PQerrorMessage(conn));
exit_nicely(conn);
}

/* debug = fopen("/tmp/trace.out","w"); */
/* PQtrace(conn, debug); */

/* start a transaction block */
res = PQexec(conn, "BEGIN");
if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
{
fprintf(stderr, "BEGIN command failed\n");
PQclear(res);
exit_nicely(conn);
}

/*
* should PQclear PGresult whenever it is no longer needed to avoid
* memory leaks
*/
PQclear(res);

/*
* fetch instances from the pg_database, the system catalog of
* databases
*/
res = PQexec(conn, "DECLARE mycursor CURSOR FOR select * from pg_database");
if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
{
fprintf(stderr, "DECLARE CURSOR command failed\n");
PQclear(res);
exit_nicely(conn);
}
PQclear(res);
res = PQexec(conn, "FETCH ALL in mycursor");
if (!res || PQresultStatus(res) != PGRES_TUPLES_OK)
{
fprintf(stderr, "FETCH ALL command didn't return tuples properly\n");
PQclear(res);
exit_nicely(conn);
}

/* first, print out the attribute names */
nFields = PQnfields(res);
for (i = 0; i < nFields; i++)
printf("%-15s", PQfname(res, i));
printf("\n\n");

/* next, print out the instances */
for (i = 0; i < PQntuples(res); i++)
{
for (j = 0; j < nFields; j++)
printf("%-15s", PQgetvalue(res, i, j));
printf("\n");
}
PQclear(res);

/* close the cursor */
res = PQexec(conn, "CLOSE mycursor");
PQclear(res);

/* commit the transaction */
res = PQexec(conn, "COMMIT");
PQclear(res);

/* close the connection to the database and cleanup */
PQfinish(conn);

/* fclose(debug); */
}

From bouncefilter Tue Nov 30 10:46:18 1999
Received: from ara.zf.jcu.cz (zakkr@ara.zf.jcu.cz [160.217.161.4])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA87279
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 10:45:59 -0500 (EST) (envelope-from zakkr@zf.jcu.cz)
Received: from localhost (zakkr@localhost)
by ara.zf.jcu.cz (8.9.3/8.9.3/Debian/GNU) with SMTP id QAA30401;
Tue, 30 Nov 1999 16:32:44 +0100
Date: Tue, 30 Nov 1999 16:32:43 +0100 (CET)
From: Karel Zak - Zakkr <zakkr@zf.jcu.cz>
To: Dale Anderson <danderso@crystalsugar.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] PGSQL C Interface
In-Reply-To: <s843925a.014@crystalsugar.com>
Message-ID: <Pine.LNX.3.96.991130163050.26151F-100000@ara.zf.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 30 Nov 1999, Dale Anderson wrote:

When compiling the test C program for Postgres, I get the following errors. Can anyone help me with what the error might be. I have included th error message when compiling, and the source code ofr the tes.

Thanks in advance,
Dale.

$ gcc -I/usr/include/pgsql dba.c -o dba

gcc -I/usr/include/pgsql dba.c -o dba -lpq
^^^^
The gcc need libs for compilation.

Karel

From bouncefilter Tue Nov 30 09:49:17 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA77248
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 09:48:19 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id JAA07405;
Tue, 30 Nov 1999 09:42:48 -0600
Date: Tue, 30 Nov 1999 09:42:47 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Mark Jewiss <Mark.Jewiss@knowledge.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Executing external scripts
In-Reply-To: <Pine.BSO.4.10.9911301402590.6506-100000@office.knowledge.com>
Message-ID: <Pine.LNX.4.10.9911300936330.7013-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

you did not study the archive hard enough ;-) somebody answered your
question days ago:
no PL for perl. you can use system() (in C) to
hack perl into c. in short, you need to learn c, just a little bit
(ask a c guy for help). -- or has somebody already done this before,
could you send the example code to the listing? thanks!

Kai

On Tue, 30 Nov 1999, Mark Jewiss wrote:

Hello,

I've been doing some reading through the documentation and the archives of
this list but have not got very far yet.

I want to be able to create a trigger that when fired will execute an
external script. I may require arguments to be passed to the script from
the trigger.

I can't find a definate yes/no as to whether this can actually be done or
not in Postgresql 6.5.* - does anybody know?

Looking over the functions section, I might be able to do what I need to
do using one of the languages. However, I don't know C, and it does not
apply to what I'm doing anyway. I need to use Perl, but this means writing
a procedural language handler, which has to be done in C, which I don't
really know..... :(

Has anybody written, or knows of the existence of, a PL for Perl for
Postgresql?

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

************

From bouncefilter Tue Nov 30 12:05:44 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA02522
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 12:05:39 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 30 Nov 1999 11:05:37 -0600
Sender: ed
Message-ID: <384403EA.5D3784A9@austin.rr.com>
Date: Tue, 30 Nov 1999 11:05:46 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jesse Scott <jscott@bmi.net>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Sorting a table...
References: <199911300833.AAA16024@smtp.bmi.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think you're looking for the 'ORDER BY' clause to use in your SELECT, e.g.,

SELECT * FROM person ORDER BY id

More examples, options, and explanation can be found at

http://www.postgresql.org/docs/postgres/sql-select.htm

Cheers.
Ed Loehr

Jesse Scott wrote:

... Once the user has completed the
editing, I perform an UPDATE on that row with the new values, but now that
row is moved to the end of the table, making the page that lists the users
list them out of order (one of the fields is a sequential ID number). Is
there anyway to do a "sort by" or something similar? Or do I need to set
the ID number to be some sort of index type?

From bouncefilter Tue Nov 30 12:15:44 1999
Received: from primetime.jtek.com (primetime.jtek.com [216.230.38.31])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA04296
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 12:15:31 -0500 (EST) (envelope-from jacobs@jtek.com)
Received: from crease.jtek.com (jacobs@node5.jacobs.dslspeed.ienet.com
[209.250.105.53])
by primetime.jtek.com (8.9.3/8.9.3) with ESMTP id RAA09504
for <pgsql-general@postgreSQL.org>; Tue, 30 Nov 1999 17:15:29 GMT
Date: Tue, 30 Nov 1999 09:15:34 -0800 (PST)
From: Stan Jacobs <jacobs@jtek.com>
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Sorting a table...
In-Reply-To: <199911300833.AAA16024@smtp.bmi.net>
Message-ID: <Pine.LNX.4.05.9911300912230.18406-100000@crease.jtek.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello all, I'm new to this list so forgive me if this question get's asked
a lot. (I did search the archives...)

A standard SQL reference might help a lot, since this is more in the
domain of SQL syntax than PostgreSQL help.

list them out of order (one of the fields is a sequential ID number). Is
there anyway to do a "sort by" or something similar? Or do I need to set
the ID number to be some sort of index type?

Just add the 'ORDER BY' tag to the end of your query....

e.g. 'SELECT * FROM users ORDER BY seq_id_number'

... and it will return the results sorted by seq_id_number. (Of course,
replace this variable with whatever your sequential id number field is
actually called.)

HTH,

- Stan -

From bouncefilter Tue Nov 30 14:12:46 1999
Received: from host67-160.student.udel.edu (host67-160.student.udel.edu
[128.175.67.160]) by hub.org (8.9.3/8.9.3) with SMTP id OAA22128
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 14:12:19 -0500 (EST)
(envelope-from hovinen@webinbox.com)
Received: (qmail 711 invoked from network); 30 Nov 1999 19:12:20 -0000
Received: from localhost (127.0.0.1)
by localhost with SMTP; 30 Nov 1999 19:12:20 -0000
Date: Tue, 30 Nov 1999 14:12:20 -0500 (EST)
From: Bradford Hovinen <hovinen@webinbox.com>
X-Sender: hovinen@host67-160.student.udel.edu
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] SQL error in PostgreSQL 6.5.3
In-Reply-To:
<Pine.LNX.4.04.9911292349010.30840-100000@host67-160.student.udel.edu>
Message-ID:
<Pine.LNX.4.04.9911301411220.709-100000@host67-160.student.udel.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Never mind. I figured out the problem: a bug in the DBD driver that was
installed on my computer. It's fixed and working now.

-Bradford Hovinen

"Prudence is a rich, ugly old maid courted by Incapacity."

- William Blake, "Proverbs of Hell," 1793

From bouncefilter Tue Nov 30 14:20:46 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA23267
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 14:20:28 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 30 Nov 1999 13:12:37 -0600
Sender: ed
Message-ID: <38442393.951B4F1@austin.rr.com>
Date: Tue, 30 Nov 1999 13:20:51 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: "FATAL 1: my bits moved right off the end of the world!"
References: <Pine.LNX.4.05.9911300912230.18406-100000@crease.jtek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have run into this error message a few times now in various circumstances
(using pgsql v6.5.2 on Linux 2.2.5-15smp):

"FATAL 1: my bits moved right off the end of the world!"

Does anyone have a clue as to what scenarios cause this? (It apparently comes
from line 506 of .../src/backend/access/nbtree/nbtpage.c)

I've had the luxury of being early in development and being able to rebuild my
DB to remove the symptom, but that will soon change.

Thanks in advance,
Ed Loehr

From bouncefilter Tue Nov 30 14:37:46 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id OAA25956
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 14:37:28 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Vessla.DoCS.UU.SE (e99re41@Vessla.DoCS.UU.SE [130.238.9.188])
by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP id UAA14362;
Tue, 30 Nov 1999 20:37:25 +0100
Received: from localhost (e99re41@localhost) by Vessla.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id UAA13887;
Tue, 30 Nov 1999 20:37:24 +0100
X-Authentication-Warning: Vessla.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Tue, 30 Nov 1999 20:37:23 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Ed Loehr <ELOEHR@austin.rr.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of the
world!"
In-Reply-To: <38442393.951B4F1@austin.rr.com>
Message-ID: <Pine.GSO.4.02A.9911302036140.13278-100000@Vessla.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

This is getting to be our favourite error message...

It is caused by a corrupted B-Tree index. Drop and recreate that one.

On Tue, 30 Nov 1999, Ed Loehr wrote:

I have run into this error message a few times now in various circumstances
(using pgsql v6.5.2 on Linux 2.2.5-15smp):

"FATAL 1: my bits moved right off the end of the world!"

Does anyone have a clue as to what scenarios cause this? (It apparently comes
from line 506 of .../src/backend/access/nbtree/nbtpage.c)

I've had the luxury of being early in development and being able to rebuild my
DB to remove the symptom, but that will soon change.

Thanks in advance,
Ed Loehr

************

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Nov 30 14:58:46 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA29995
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 14:58:39 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA18607;
Tue, 30 Nov 1999 14:58:27 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911301958.OAA18607@candle.pha.pa.us>
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of the
world!"
In-Reply-To: <38442393.951B4F1@austin.rr.com> from Ed Loehr at "Nov 30, 1999
01:20:51 pm"
To: Ed Loehr <ELOEHR@austin.rr.com>
Date: Tue, 30 Nov 1999 14:58:27 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have run into this error message a few times now in various circumstances
(using pgsql v6.5.2 on Linux 2.2.5-15smp):

"FATAL 1: my bits moved right off the end of the world!"

Does anyone have a clue as to what scenarios cause this? (It apparently comes
from line 506 of .../src/backend/access/nbtree/nbtpage.c)

I've had the luxury of being early in development and being able to rebuild my
DB to remove the symptom, but that will soon change.

Drop index and recreate. 7.0 will say that specifically.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 30 17:35:48 1999
Received: from crystalsugar.com ([207.0.65.31])
by hub.org (8.9.3/8.9.3) with SMTP id RAA48352
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 17:35:26 -0500 (EST)
(envelope-from danderso@crystalsugar.com)
Received: from JCEDO-Message_Server by crystalsugar.com
with Novell_GroupWise; Tue, 30 Nov 1999 16:34:48 -0600
Message-Id: <s843fca8.078@crystalsugar.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.2.1
Date: Tue, 30 Nov 1999 16:34:34 -0600
From: "Dale Anderson" <danderso@crystalsugar.com>
To: <pgsql-general@postgreSQL.org>
Subject: Date & Time
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id RAA48365

How would I insert the current date & time into a record during an insert, IE such as the Oracle SYSDATE function??

( insert into test values (123, SYSDATE, 'Name');

Thanks,
Dale.

From bouncefilter Tue Nov 30 17:48:48 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA49637
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 17:48:14 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11sw4D-000LECC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Tue, 30 Nov 1999 16:48:13 -0600 (CST)
Date: Tue, 30 Nov 1999 16:48:13 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: Dale Anderson <danderso@crystalsugar.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
Message-ID: <19991130164813.A9625@wallace.ece.rice.edu>
References: <s843fca8.078@crystalsugar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <s843fca8.078@crystalsugar.com>;
from Dale Anderson on Tue, Nov 30, 1999 at 04:34:34PM -0600

Dale -
How about this?

Ross

test=> create table test (t_id int, start datetime, what text);
CREATE
test=> insert into test values (123, now(), 'Name');
INSERT 684299 1
test=> select * from test;
t_id|start |what
----+----------------------------+----
123|Tue Nov 30 16:46:07 1999 CST|Name
(1 row)

test=>

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Tue, Nov 30, 1999 at 04:34:34PM -0600, Dale Anderson wrote:

How would I insert the current date & time into a record during an insert, IE such as the Oracle SYSDATE function??

( insert into test values (123, SYSDATE, 'Name');

Thanks,
Dale.

************

From bouncefilter Tue Nov 30 19:01:49 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA59159
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 19:01:36 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
SAA25326;
Tue, 30 Nov 1999 18:58:25 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199911302358.SAA25326@candle.pha.pa.us>
Subject: Re: [GENERAL] Date & Time
In-Reply-To:
<Pine.LNX.4.10.9911301800240.17752-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Nov 30, 1999 06:04:30 pm"
To: kaiq@realtyideas.com
Date: Tue, 30 Nov 1999 18:58:25 -0500 (EST)
CC: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

"now" performs better in this case:
insert into test values (123, 'now','Name');

now() is needed for "default" in create table, because
"now" won't work right (a bug/feature ?).

Why does 'now' preform better than now()?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 30 18:09:48 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA52717
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 18:09:45 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id SAA17774;
Tue, 30 Nov 1999 18:04:30 -0600
Date: Tue, 30 Nov 1999 18:04:30 -0600 (CST)
From: <kaiq@realtyideas.com>
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
cc: Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <19991130164813.A9625@wallace.ece.rice.edu>
Message-ID: <Pine.LNX.4.10.9911301800240.17752-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

"now" performs better in this case:
insert into test values (123, 'now','Name');

now() is needed for "default" in create table, because
"now" won't work right (a bug/feature ?).

see archive in this list

On Tue, 30 Nov 1999, Ross J. Reedstrom wrote:

Dale -
How about this?

Ross

test=> create table test (t_id int, start datetime, what text);
CREATE
test=> insert into test values (123, now(), 'Name');
INSERT 684299 1
test=> select * from test;
t_id|start |what
----+----------------------------+----
123|Tue Nov 30 16:46:07 1999 CST|Name
(1 row)

test=> insert into test values (456, now(), 'Other');
INSERT 684300 1
test=> select * from test;
t_id|start |what
----+----------------------------+----
123|Tue Nov 30 16:46:07 1999 CST|Name
456|Tue Nov 30 16:46:15 1999 CST|Other
(2 rows)

test=>

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Tue, Nov 30, 1999 at 04:34:34PM -0600, Dale Anderson wrote:

How would I insert the current date & time into a record during an insert, IE such as the Oracle SYSDATE function??

( insert into test values (123, SYSDATE, 'Name');

Thanks,
Dale.

************

************

From bouncefilter Tue Nov 30 19:06:49 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA59719
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 19:06:08 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 30 Nov 1999 18:06:21 -0600
Sender: ed
Message-ID: <38446682.4746C051@austin.rr.com>
Date: Tue, 30 Nov 1999 18:06:27 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
References: <Pine.GSO.4.02A.9911302036140.13278-100000@Vessla.DoCS.UU.SE>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Eisentraut wrote:

This is getting to be our favourite error message...

It is caused by a corrupted B-Tree index. Drop and recreate that one.

Thanks. Unfortunately, the lack of context to the error message makes it difficult
to identify which index is "that one." The message was last showing up during the
process of dropping/recreating a series of triggers and functions via "psql -f"
without any table inserts/updates.

Cheers.
Ed Loehr

On Tue, 30 Nov 1999, Ed Loehr wrote:

I have run into this error message a few times now in various circumstances
(using pgsql v6.5.2 on Linux 2.2.5-15smp):

"FATAL 1: my bits moved right off the end of the world!"

Does anyone have a clue as to what scenarios cause this? (It apparently comes
from line 506 of .../src/backend/access/nbtree/nbtpage.c)

I've had the luxury of being early in development and being able to rebuild my
DB to remove the symptom, but that will soon change.

Thanks in advance,
Ed Loehr

************

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

************

From bouncefilter Tue Nov 30 19:09:49 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA60022
for <pgsql-general@postgresql.org>;
Tue, 30 Nov 1999 19:09:46 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 30 Nov 1999 18:10:00 -0600
Sender: ed
Message-ID: <38446761.D2D62AAF@austin.rr.com>
Date: Tue, 30 Nov 1999 18:10:09 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: kaiq@realtyideas.com
CC: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
References: <Pine.LNX.4.10.9911301800240.17752-100000@picasso.realtyideas.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

Cheers.
Ed Loehr

kaiq@realtyideas.com wrote:

"now" performs better in this case:
insert into test values (123, 'now','Name');

now() is needed for "default" in create table, because
"now" won't work right (a bug/feature ?).

see archive in this list

On Tue, 30 Nov 1999, Ross J. Reedstrom wrote:

Dale -
How about this?

Ross

test=> create table test (t_id int, start datetime, what text);
CREATE
test=> insert into test values (123, now(), 'Name');
INSERT 684299 1
test=> select * from test;
t_id|start |what
----+----------------------------+----
123|Tue Nov 30 16:46:07 1999 CST|Name
(1 row)

test=> insert into test values (456, now(), 'Other');
INSERT 684300 1
test=> select * from test;
t_id|start |what
----+----------------------------+----
123|Tue Nov 30 16:46:07 1999 CST|Name
456|Tue Nov 30 16:46:15 1999 CST|Other
(2 rows)

test=>

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Tue, Nov 30, 1999 at 04:34:34PM -0600, Dale Anderson wrote:

How would I insert the current date & time into a record during an insert, IE such as the Oracle SYSDATE function??

( insert into test values (123, SYSDATE, 'Name');

Thanks,
Dale.

************

************

************

From bouncefilter Tue Nov 30 19:30:49 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA63325
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 19:29:47 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
TAA26972;
Tue, 30 Nov 1999 19:27:47 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912010027.TAA26972@candle.pha.pa.us>
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
In-Reply-To: <38446682.4746C051@austin.rr.com> from Ed Loehr at "Nov 30, 1999
06:06:27 pm"
To: Ed Loehr <ELOEHR@austin.rr.com>
Date: Tue, 30 Nov 1999 19:27:46 -0500 (EST)
CC: Peter Eisentraut <peter_e@gmx.net>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Peter Eisentraut wrote:

This is getting to be our favourite error message...

It is caused by a corrupted B-Tree index. Drop and recreate that one.

Thanks. Unfortunately, the lack of context to the error message makes it difficult
to identify which index is "that one." The message was last showing up during the
process of dropping/recreating a series of triggers and functions via "psql -f"
without any table inserts/updates.

I have fixed 7.0 so it will show the index name.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Nov 30 21:36:51 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA77273
for <pgsql-general@postgreSQL.org>;
Tue, 30 Nov 1999 21:36:02 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id KAA01594
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 10:36:01 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma001590; Wed, 1 Dec 99 10:35:33 +0800
Message-Id: <3.0.5.32.19991201103612.0088bdd0@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Wed, 01 Dec 1999 10:36:12 +0800
To: pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Documentation of nitty gritty stuff.
In-Reply-To: <Pine.BSO.4.10.9911301402590.6506-100000@office.knowledge.c
om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

Where should I look in the documentation for how to "quote" data for Postgres?
e.g.
Quoting quotes..
select * from t where x='It''s hard to find'

Quoting Likes- trying to find backslashes-
select * from t where x like '%\\%' ?

Also more information on limits of data/types would be good - serial,
character types. Can characters store 8 bit data safely. If not, can we
kludge it with numeric..

How to get datetime to show the famed 1 microsecond resolution- "order by"
doesn't seem to work.

There's quite a bit of good info in the current Postgres docs, but it seems
to gloss over some nitty gritty details.

Cheerio,

Link.

From bouncefilter Wed Dec 1 04:53:00 1999
Received: from tinago.msuiit.edu.ph (tinago.msuiit.edu.ph [165.220.48.4])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA32673;
Wed, 1 Dec 1999 04:51:47 -0500 (EST)
(envelope-from manny@tinago.msuiit.edu.ph)
Received: from localhost (manny@localhost)
by tinago.msuiit.edu.ph (8.8.7/8.8.7) with ESMTP id RAA07492;
Wed, 1 Dec 1999 17:53:53 +0800
Date: Wed, 1 Dec 1999 17:53:52 +0800 (JST)
From: Manuel Cabido <manny@tinago.msuiit.edu.ph>
To: pgsql-general@hub.org
cc: pgsql-general-digest@hub.org
Subject: Re: pgsql-general-digest V1 #550
In-Reply-To: <199912010402.XAA87578@hub.org>
Message-ID: <Pine.LNX.4.04.9912011750230.7164-100000@tinago.msuiit.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sir:

I working on an application that needs to access the postgresql
database using a web page. Java was suggested to me as a very good
platform. Can anyone give me some ideas where i can obtain some components
like the database components available to delphi or visual basic which i
can use in my web page using java?

Manny C. Cabido
====================================
e-mail:manny@tinago.msuiit.edu.ph
manny@sun.msuiit.edu.ph
=====================================

From bouncefilter Wed Dec 1 04:55:00 1999
Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA32845
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 04:54:39 -0500 (EST)
(envelope-from Inoue@tpf.co.jp)
Received: from cadzone ([126.0.1.40] (may be forged))
by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP
id SAA00039; Wed, 01 Dec 1999 18:52:56 +0900
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Vadim Mikheev" <vadim@krs.ru>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "PostgreSQL Developers List" <hackers@postgreSQL.org>
Subject: RE: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: Wed, 1 Dec 1999 18:57:42 +0900
Message-ID: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <000201bf3aca$9a3a9ac0$2801007e@cadzone.tpf.co.jp>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal

I propose here that we stop the release of lock before end of transaction.
I have been suffering from the early release of lock.

Comments ?

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp

From bouncefilter Wed Dec 1 05:01:00 1999
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA34022
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 05:00:17 -0500 (EST)
(envelope-from vadim@krs.ru)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id QAA15535;
Wed, 1 Dec 1999 16:59:59 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <3844F19E.2A14BF1C@krs.ru>
Date: Wed, 01 Dec 1999 16:59:58 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Hiroshi Inoue <Inoue@tpf.co.jp>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hiroshi Inoue wrote:

I propose here that we stop the release of lock before end of transaction.
I have been suffering from the early release of lock.

Comments ?

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

Vadim

From bouncefilter Wed Dec 1 05:13:09 1999
Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA36956
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 05:12:59 -0500 (EST)
(envelope-from Inoue@tpf.co.jp)
Received: from tpf.co.jp ([126.0.1.56] (may be forged))
by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP
id TAA00054; Wed, 01 Dec 1999 19:11:21 +0900
Message-ID: <3844F44D.4D003E93@tpf.co.jp>
Date: Wed, 01 Dec 1999 19:11:25 +0900
From: Hiroshi Inoue <Inoue@tpf.co.jp>
X-Mailer: Mozilla 4.51 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: Vadim Mikheev <vadim@krs.ru>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
<3844F19E.2A14BF1C@krs.ru>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Vadim Mikheev wrote:

Hiroshi Inoue wrote:

I propose here that we stop the release of lock before end of transaction.
I have been suffering from the early release of lock.

Comments ?

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

I think UnlockRelation() is unnecessary

Oracle doesn't have

Vadim

From bouncefilter Wed Dec 1 10:04:33 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA09008
for <hackers@postgresql.org>; Wed, 1 Dec 1999 10:03:57 -0500 (EST)
(envelope-from vadim@krs.ru)
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by trends.net (8.8.8/8.8.8) with ESMTP id FAA16445
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 05:35:18 -0500 (EST)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id RAA15872;
Wed, 1 Dec 1999 17:28:36 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <3844F854.3DF03CFF@krs.ru>
Date: Wed, 01 Dec 1999 17:28:36 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Hiroshi Inoue <Inoue@tpf.co.jp>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
<3844F19E.2A14BF1C@krs.ru> <3844F44D.4D003E93@tpf.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hiroshi Inoue wrote:

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

I think UnlockRelation() is unnecessary

Oracle doesn't have

And we havn't UNLOCK TABLE _command_ as well -:)
But func call is internal thing and I don't know
Oracle internals.
If this call is unnecessary - get rid of it at all...

Vadim

From bouncefilter Wed Dec 1 10:04:49 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA09272
for <hackers@postgresql.org>; Wed, 1 Dec 1999 10:04:01 -0500 (EST)
(envelope-from Inoue@tpf.co.jp)
Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34])
by trends.net (8.8.8/8.8.8) with ESMTP id FAA16544
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 05:38:57 -0500 (EST)
Received: from tpf.co.jp ([126.0.1.56] (may be forged))
by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP
id TAA00068; Wed, 01 Dec 1999 19:37:14 +0900
Message-ID: <3844FA5E.EAFD86CF@tpf.co.jp>
Date: Wed, 01 Dec 1999 19:37:18 +0900
From: Hiroshi Inoue <Inoue@tpf.co.jp>
X-Mailer: Mozilla 4.51 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: Vadim Mikheev <vadim@krs.ru>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
<3844F19E.2A14BF1C@krs.ru>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Oops sorry,I sent a draft by mistake.

Vadim Mikheev wrote:

Hiroshi Inoue wrote:

I propose here that we stop the release of lock before end of transaction.
I have been suffering from the early release of lock.

Comments ?

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

I was surprized that few people really want DDL commands inside transactions.
Are there any reasons to releasing lock before end of transaction except
that long term lock for system tuples is not preferable ?

I think that UnlockRelation() is unnecessary fundamentally.
Mine is the simplest way to achieve this.
If there's no problem,I am glad to remove UnlockRelation() calls.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp

From bouncefilter Wed Dec 1 10:03:26 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA06504
for <hackers@postgresql.org>; Wed, 1 Dec 1999 10:03:11 -0500 (EST)
(envelope-from vadim@krs.ru)
Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37])
by trends.net (8.8.8/8.8.8) with ESMTP id FAA17119
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 05:56:30 -0500 (EST)
Received: from krs.ru (dune.krs.ru [195.161.16.38])
by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id RAA15998;
Wed, 1 Dec 1999 17:49:49 +0700 (KRS)
Sender: root@sunpine.krs.ru
Message-ID: <3844FD4B.6086683B@krs.ru>
Date: Wed, 01 Dec 1999 17:49:47 +0700
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
X-Accept-Language: ru, en
MIME-Version: 1.0
To: Hiroshi Inoue <Inoue@tpf.co.jp>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
<3844F19E.2A14BF1C@krs.ru> <3844FA5E.EAFD86CF@tpf.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hiroshi Inoue wrote:

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

I was surprized that few people really want DDL commands inside transactions.
Are there any reasons to releasing lock before end of transaction except
that long term lock for system tuples is not preferable ?

I think that UnlockRelation() is unnecessary fundamentally.
Mine is the simplest way to achieve this.
If there's no problem,I am glad to remove UnlockRelation() calls.

There are! I finally found where I used UnlockRelation() -
in execUtils.c:ExecCloseIndices(). Please read comments in
ExecOpenIndices() where LockRelation() is called...

Vadim

From bouncefilter Wed Dec 1 10:02:58 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA01357
for <hackers@postgresql.org>; Wed, 1 Dec 1999 10:01:35 -0500 (EST)
(envelope-from Inoue@tpf.co.jp)
Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34])
by trends.net (8.8.8/8.8.8) with ESMTP id HAA20001
for <hackers@postgreSQL.org>; Wed, 1 Dec 1999 07:26:11 -0500 (EST)
Received: from tpf.co.jp (ppm235.noc.fukui.nsk.ne.jp [210.161.188.110])
by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP
id VAA00091; Wed, 01 Dec 1999 21:24:24 +0900
Message-ID: <3845137D.8ABC6BDD@tpf.co.jp>
Date: Wed, 01 Dec 1999 21:24:29 +0900
From: Hiroshi Inoue <Inoue@tpf.co.jp>
X-Mailer: Mozilla 4.51 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: Vadim Mikheev <vadim@krs.ru>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers List <hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
References: <001001bf3be2$821dc520$2801007e@cadzone.tpf.co.jp>
<3844F19E.2A14BF1C@krs.ru> <3844FA5E.EAFD86CF@tpf.co.jp>
<3844FD4B.6086683B@krs.ru>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Vadim Mikheev wrote:

Hiroshi Inoue wrote:

If there's no objection,I would change UnlockRelation() to not release
the specified lock except AccessShareLock.

Why don't remove this call from improper places?
I would try to find all calls and understand why
they made...

I was surprized that few people really want DDL commands inside transactions.
Are there any reasons to releasing lock before end of transaction except
that long term lock for system tuples is not preferable ?

I think that UnlockRelation() is unnecessary fundamentally.
Mine is the simplest way to achieve this.
If there's no problem,I am glad to remove UnlockRelation() calls.

There are! I finally found where I used UnlockRelation() -
in execUtils.c:ExecCloseIndices(). Please read comments in
ExecOpenIndices() where LockRelation() is called...

I see it now.

Hmm,index itself doesn't have its time qualification and is out of
transaction control(at least now).

OK,I would examine it one by one.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp

From bouncefilter Wed Dec 1 09:42:58 1999
Received: from mail01.t-net.net.ve ([200.35.64.6])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA01823
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 09:42:36 -0500 (EST)
(envelope-from directo@telcel.net.ve)
Received: from 192.168.1.254.nmg.com ([206.49.128.87])
by mail01.t-net.net.ve (Post.Office MTA v3.5.3 release 223
ID# 557-52511U100000L100000S0V35) with SMTP id ve
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 10:41:42 -0400
Message-ID: <000001bf3c05$d9244880$578031ce@192.168.1.254.nmg.com>
Reply-To: "FM&NB" <directo@telcel.net.ve>
From: "FM&NB" <directo@telcel.net.ve>
To: <pgsql-general@postgreSQL.org>
Subject:
Date: Wed, 1 Dec 1999 09:47:07 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

subscribe
end

From bouncefilter Wed Dec 1 09:43:07 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA01846
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 09:42:51 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by trends.net (8.8.8/8.8.8) with ESMTP id JAA24670
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 09:12:56 -0500 (EST)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11tAUY-00006e-00
for pgsql-general@postgresql.org; Wed, 1 Dec 1999 14:12:22 +0000
Date: Wed, 1 Dec 1999 14:12:22 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: pgsql-general@postgreSQL.org
Subject: pg_passwd queries
Message-ID: <Pine.BSO.4.10.9912011407310.7277-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

I've looked over the list archives before, and didn't see anything about
this then....can't check now as I'm having problems getting on to the web
server :(

I'm using the pg_passwd script to create password files that are
referenced via the pg_hba.conf file. Each user has a different file
containing only their own password.

I've noticed that pg_passwd will encrypt any password given to it in lower
case only. Is this intentional, or a bug? To clarify, if a password is
entered and confirmed that has upper case characters in it, the password
that is encrypted contains lower case characters only.

Secondly, I want to build the password files as part of a script I have
written. I'm using the standard encrypt program on OpenBSD, but this does
not work - I get a user authentication error message each time I try to
log in. What method of encryption does the pg_passwd script use? I need to
be able to encrypt using DES or blowfish for this to work.

If anyone has any ideas or solutions that they have found please let me
know.

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Wed Dec 1 09:36:58 1999
Received: from mail.webbridges.it (root@wbridges.cust.fnc.net [195.191.8.246])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA00944
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 09:36:52 -0500 (EST)
(envelope-from massimo@webbridges.it)
Received: from webbridges.it (skvat.hq.webbridges.it [192.168.0.24])
by mail.webbridges.it (8.8.8/8.8.8) with ESMTP id QAA09974
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 16:26:58 +0100
Message-ID: <38452F96.60C01EC6@webbridges.it>
Date: Wed, 01 Dec 1999 15:24:22 +0100
From: Massimo Pichini <massimo@webbridges.it>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Is the postgres libpq library thread safe ?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

I guess that the postgres it-self is not designated as a multi-threaded
server. I was wondering if the library is instead thread safe (i.e.: if
it can be safely called from multi-threaded applications).

Thanks in advance
Massimo

From bouncefilter Wed Dec 1 10:39:46 1999
Received: from camino.pa.tibcofinance.com ([216.101.119.58])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA72392
for <pgsql-general@hub.org>; Wed, 1 Dec 1999 10:38:45 -0500 (EST)
(envelope-from maarten.boekhold@tibcofinance.com)
Received: from tekbspa.tibcofinance.com (tekbspa.tibcofinance.com
[160.101.12.31])
by camino.pa.tibcofinance.com (8.9.3/8.9.3) with SMTP id HAA01076;
Wed, 1 Dec 1999 07:32:23 -0800 (PST)
Received: from tibcofinance.com ([160.101.149.34]) by tekbspa.tibcofinance.com
(4.1/SMI-4.1) id AA21445; Wed, 1 Dec 99 07:34:38 PST
Message-Id: <38453795.BB81DA89@tibcofinance.com>
Date: Wed, 01 Dec 1999 15:58:29 +0100
From: Maarten Boekhold <maarten.boekhold@tibcofinance.com>
Organization: TIBCO Finance Technology Inc.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
Mime-Version: 1.0
To: John Henderson <jrh@is.com.fj>
Cc: pgsql-general@hub.org
Subject: Re: [GENERAL] memory
References: <008d01bf3ac5$f4c85040$ea7c3eca@john.is.com.fj>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

isfiji=> explain select * from sessions;
NOTICE: QUERY PLAN:
Seq Scan on sessions (cost=21330.73 size=371719 width=138)
EXPLAIN

The query above can access over 250M of memory according to top but dies
with either a seg fault or the latest, something called
"calloc: Cannot allocate memory"

I'm not sure, but my guess is: the BE needs to allocate data for over 74
megs (your table data), probably more due to formatting and page alignment
losses. Then it's sending it over either a TCP/IP connection or a UNIX
domain socket, probably another 74 megs to be allocated somewhere in
memory(?) and finally it gets to psql which needs to get yet another 74
megs.

Does this make any sense to the experts?

Maarten

Maarten Boekhold, maarten.boekhold@tibcofinance.com
TIBCO Finance Technology Inc.
"Sevilla" Building
Entrada 308
1096 ED Amsterdam, The Netherlands
tel: +31 20 6601000 (direct: +31 20 6601066)
fax: +31 20 6601005
http://www.tibcofinance.com

From bouncefilter Wed Dec 1 10:00:25 1999
Received: from mail.webbridges.it (root@wbridges.cust.fnc.net [195.191.8.246])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA08613
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 09:56:16 -0500 (EST)
(envelope-from massimo@webbridges.it)
Received: from webbridges.it (skvat.hq.webbridges.it [192.168.0.24])
by mail.webbridges.it (8.8.8/8.8.8) with ESMTP id RAA11392
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 17:01:25 +0100
Message-ID: <384537A9.F2FFBE62@webbridges.it>
Date: Wed, 01 Dec 1999 15:58:49 +0100
From: Massimo Pichini <massimo@webbridges.it>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: postgres libpq library
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

Thanks in advance
Massimo

From bouncefilter Wed Dec 1 09:38:58 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA01073
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 09:38:25 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id JAA28718;
Wed, 1 Dec 1999 09:33:04 -0600
Date: Wed, 1 Dec 1999 09:33:04 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199911302358.SAA25326@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912010922160.28473-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

now is a constant, while now() is a function. so, to me,
it should be always now unless you really need now().
what's more, in my impression, now() is not in any official
doc, it is like a rescue for now. however, in this case,
seems there is not much difference.-- oops

as for current_timestamp: I bet it is cos the sql92 thing.
now and now() is not sql92 standard. but not sure if now
or now() are the underlying thing, not sure even whether now
and now() are from the same code. Anybody ideas?

On Tue, 30 Nov 1999, Bruce Momjian wrote:

"now" performs better in this case:
insert into test values (123, 'now','Name');

now() is needed for "default" in create table, because
"now" won't work right (a bug/feature ?).

Why does 'now' preform better than now()?
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************

From bouncefilter Wed Dec 1 10:40:44 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA75219
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 10:39:48 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 1 Dec 1999 09:35:14 -0600
Sender: ed
Message-ID: <38454038.9B953DFC@austin.rr.com>
Date: Wed, 01 Dec 1999 09:35:21 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Peter Eisentraut <peter_e@gmx.net>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
References: <199912010027.TAA26972@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

Peter Eisentraut wrote:

This is getting to be our favourite error message...

It is caused by a corrupted B-Tree index. Drop and recreate that one.

Thanks. Unfortunately, the lack of context to the error message makes it difficult
to identify which index is "that one." The message was last showing up during the
process of dropping/recreating a series of triggers and functions via "psql -f"
without any table inserts/updates.

I have fixed 7.0 so it will show the index name.

It sounds like this B-tree index corruption happens often enough to gain fame. I am
curious as to what the full impact of this is on a production database. Would I be
correct in assuming are consequences are (1) an unusable index, resulting in (2)
inaccessible data, resulting in (3) an unusable database until the index is dropped and
recreated?

If the least drastic corrective solution is to drop and recreate the index, that leaves
me wondering:
1) Does anyone know what is causing the corrupted B-tree?
2) How difficult would it be to automate the process of index rebuilding at the
point the corruption is detected? How could that be done otherwise in an automated
fashion?
3) What are other people doing to deal with this?

Cheers.
Ed

From bouncefilter Wed Dec 1 10:45:42 1999
Received: from adidbsrv.edn.echostar.com ([205.172.146.91])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA89196
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 10:44:51 -0500 (EST)
(envelope-from Soundar.Pandurangan@exchange1.echostar.com)
Received: from exchange1.echostar.com (IDENT:psrajan@localhost [127.0.0.1])
by adidbsrv.edn.echostar.com (8.9.3/8.9.3) with ESMTP id KAA02549
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 10:49:41 -0500
Sender: psrajan@adidbsrv.edn.echostar.com
Message-ID: <38454395.BFE53A07@exchange1.echostar.com>
Date: Wed, 01 Dec 1999 10:49:41 -0500
From: Soundar <Soundar.Pandurangan@exchange1.echostar.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: JDBC 2.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

Does 6.5.3 support JDBC2.0 API?

From bouncefilter Wed Dec 1 11:05:49 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA18617
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 11:05:12 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.230]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 1 Dec 1999 09:54:39 -0600
Sender: ed
Message-ID: <384544C6.FA315ECD@austin.rr.com>
Date: Wed, 01 Dec 1999 09:54:46 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>,
Peter Eisentraut <peter_e@gmx.net>,
pgsql-general@postgresql.org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
References: <199912010027.TAA26972@candle.pha.pa.us>
<38454038.9B953DFC@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Answering part of my own questions, it appears the latest thinking on this problem (in
http://www.deja.com/getdoc.xp?AN=542994084) is that it stems from indexed columns greater
than half a page (~4K), and/or a previous insert having been interrupted by elog(ERROR) or
a backend crash. The latter explanation seems more plausible, as I do not have any
columns approaching 512 bytes, much less 4K. Glad to hear it may be coming from an error
rather than normal usage, though it'd be nice to optionally have corrupted indices
automatically rebuilt.

Cheers.
Ed

Ed Loehr wrote:

Bruce Momjian wrote:

Peter Eisentraut wrote:

This is getting to be our favourite error message...

It is caused by a corrupted B-Tree index. Drop and recreate that one.

Thanks. Unfortunately, the lack of context to the error message makes it difficult
to identify which index is "that one." The message was last showing up during the
process of dropping/recreating a series of triggers and functions via "psql -f"
without any table inserts/updates.

I have fixed 7.0 so it will show the index name.

It sounds like this B-tree index corruption happens often enough to gain fame. I am
curious as to what the full impact of this is on a production database. Would I be
correct in assuming are consequences are (1) an unusable index, resulting in (2)
inaccessible data, resulting in (3) an unusable database until the index is dropped and
recreated?

If the least drastic corrective solution is to drop and recreate the index, that leaves
me wondering:
1) Does anyone know what is causing the corrupted B-tree?
2) How difficult would it be to automate the process of index rebuilding at the
point the corruption is detected? How could that be done otherwise in an automated
fashion?
3) What are other people doing to deal with this?

Cheers.
Ed

From bouncefilter Wed Dec 1 11:01:49 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1] (may be
forged)) by hub.org (8.9.3/8.9.3) with ESMTP id LAA15376
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 11:00:57 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id RAA21763;
Wed, 1 Dec 1999 17:00:26 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11tD2E-0004SQ-00; Wed, 1 Dec 1999 16:55:18 +0000
Message-ID: <384545C0.AC6246D6@sferacarta.com>
Date: Wed, 01 Dec 1999 16:58:56 +0100
From: jose soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: Ed Loehr <ELOEHR@austin.rr.com>
CC: kaiq@realtyideas.com, "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
References: <Pine.LNX.4.10.9911301800240.17752-100000@picasso.realtyideas.com>
<38446761.D2D62AAF@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

Jose'

From bouncefilter Wed Dec 1 10:19:21 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA36647
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 10:18:42 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id KAA29807
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 10:13:36 -0600
Date: Wed, 1 Dec 1999 10:13:36 -0600 (CST)
From: <kaiq@realtyideas.com>
To: PostreSQL <pgsql-general@postgreSQL.org>
Subject: book's pdf link
In-Reply-To: <3.0.5.32.19991124114437.008eb660@pop.mecomb.po.my>
Message-ID: <Pine.LNX.4.10.9912011009090.29271-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I can not get THE book's pdf link. Not sure whether it
is my side's irregular firewall issue. If in that case,
can it be a http link? I guess I question/request is:
seems the ftp link is broken? if not, can it be a http one?

thanks

Kai

From bouncefilter Wed Dec 1 13:49:51 1999
Received: from desh.cse.iitd.ernet.in (IDENT:root@mailer.cse.iitd.ac.in
[202.141.68.3]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA88601
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 13:49:33 -0500 (EST)
(envelope-from csa98016@cse.iitd.ernet.in)
Received: from cse.iitd.ernet.in (csa98016@vibhas.cse.iitd.ernet.in
[10.20.14.28])
by desh.cse.iitd.ernet.in (8.8.7/8.8.7) with ESMTP id AAA24317
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 00:21:35 +0530
Received: from localhost (csa98016@localhost)
by cse.iitd.ernet.in (8.8.7/8.8.7) with ESMTP id AAA03481
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 00:21:35 +0530
Date: Thu, 2 Dec 1999 00:21:34 +0530 (IST)
From: Satyajeet Seth <csa98016@cse.iitd.ernet.in>
To: pgsql-general@postgresql.org
Subject: Except operation
Message-ID: <Pine.LNX.4.10.9912020021060.3476-100000@vibhas.cse.iitd.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:

tracedb=> \d webdata
Table    = webdata
+----------------------------------+----------------------------------+-------+
|              Field               |              Type                |
Length|
+----------------------------------+----------------------------------+-------+
| tid                              | int4                             |
4 |
| itemid                           | int4                             |
4 |
| ordering                         | int4                             |
4 |
+----------------------------------+----------------------------------+-------+

tracedb=> \d webdata1
Table    = webdata1
+----------------------------------+----------------------------------+-------+
|              Field               |              Type                |
Length|
+----------------------------------+----------------------------------+-------+
| tid                              | int4                             |
4 |
| itemid                           | int4                             |
4 |
| ordering                         | int4                             |
4 |
+----------------------------------+----------------------------------+-------+
tracedb=> select count(*) from webdata;
count
-----
91155
(1 row)

tracedb=> select count(*) from webdata1;
count
-----
9550
(1 row)

Regards
Satya

From bouncefilter Wed Dec 1 15:02:52 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA97408
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 15:02:06 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA04319;
Wed, 1 Dec 1999 14:50:25 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912011950.OAA04319@candle.pha.pa.us>
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <384545C0.AC6246D6@sferacarta.com> from jose soares at "Dec 1,
1999 04:58:56 pm"
To: jose soares <jose@sferacarta.com>
Date: Wed, 1 Dec 1999 14:50:25 -0500 (EST)
CC: Ed Loehr <ELOEHR@austin.rr.com>, kaiq@realtyideas.com,
"Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

I am changing my book to use CURRENT_TIMESTAMP rather than now().

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Wed Dec 1 15:09:53 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA98214
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 15:09:37 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from ocis.ocis.net (IDENT:http@ocis.ocis.net [209.52.173.1])
by ocis.ocis.net (8.9.3/8.9.3) with SMTP id MAA20920
for pgsql-general@postgresql.org; Wed, 1 Dec 1999 12:09:36 -0800
Date: Wed, 1 Dec 1999 12:09:36 -0800
From: Jason Leach <jcl@mail.ocis.net>
Message-Id: <199912012009.MAA20920@ocis.ocis.net>
Subject: The Ghost.
To: undisclosed-recipients:;

hi,

Does anyone know of a thechnical brief on Pg I can look up and read? For example how it spawns a new process, uses mem, and what not. Not detailed algorithms, but an overview of how it works; and maybe a why.

If no such animal exists, perhaps, is a few people are interested, we coudl put one together. Maybe even database of such information - but perhaps a tech-faq.

From bouncefilter Wed Dec 1 15:02:52 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA97428
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 15:02:48 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id OAA05821
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 14:57:49 -0600
Date: Wed, 1 Dec 1999 14:57:49 -0600 (CST)
From: <kaiq@realtyideas.com>
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] book's pdf link
In-Reply-To: <199912011803.NAA24225@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912011450400.608-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

yes. good for netscape. I forgot I hate M$ ;-)
I'm going to read it word by word to systemize my sql/pg knowledge.

Another thing: the general and sql mailing lists' search do not work now.
they only return 1,2,3,... empty links, no content.

thanks!

On Wed, 1 Dec 1999, Bruce Momjian wrote:

I can not get THE book's pdf link. Not sure whether it
is my side's irregular firewall issue. If in that case,
can it be a http link? I guess I question/request is:
seems the ftp link is broken? if not, can it be a http one?

I can get it via Netscape without problems. Sorry.
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Wed Dec 1 17:59:54 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA20005
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 17:59:42 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id SAA02479;
Wed, 1 Dec 1999 18:59:17 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 1 Dec 1999 18:59:16 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: kaiq@realtyideas.com
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] book's pdf link
In-Reply-To: <Pine.LNX.4.10.9912011450400.608-100000@picasso.realtyideas.com>
Message-ID: <Pine.BSF.4.21.9912011857490.823-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 1 Dec 1999 kaiq@realtyideas.com wrote:

yes. good for netscape. I forgot I hate M$ ;-)
I'm going to read it word by word to systemize my sql/pg knowledge.

Another thing: the general and sql mailing lists' search do not work now.
they only return 1,2,3,... empty links, no content.

Remind me about this after tomorrow...tomorrow we're doing a major upgrade
to the server...moving the machine and drives into rackmounted cases, and
more disk space, etc, etc...once that is done, I want to play with the
udmsearch software that uses PostgreSQL for a backend and see if that will
do what ht/dig is currently doing now...

thanks!

On Wed, 1 Dec 1999, Bruce Momjian wrote:
I can not get THE book's pdf link. Not sure whether it
is my side's irregular firewall issue. If in that case,
can it be a http link? I guess I question/request is:
seems the ftp link is broken? if not, can it be a http one?

I can get it via Netscape without problems. Sorry.
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 1 18:16:54 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id SAA22478
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 18:16:32 -0500 (EST)
(envelope-from szi@do.khs-ag.de)
Received: (qmail 29887 invoked by uid 500); 1 Dec 1999 23:15:40 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: How can I alter a function?
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Sascha Ziemann <szi@khs-ag.de>
Date: 02 Dec 1999 00:15:40 +0100
Message-ID: <m3g0xmp80z.fsf@intra.do.khs-ag.de>
Lines: 6
X-Mailer: Gnus v5.7/Emacs 20.4

Hi,

How can I change the definition of a function without breaking all
tables, which use the function?

Sascha

From bouncefilter Wed Dec 1 19:19:56 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA29801
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 19:19:41 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
TAA16636;
Wed, 1 Dec 1999 19:18:37 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912020018.TAA16636@candle.pha.pa.us>
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <Pine.LNX.4.10.9912011817550.9191-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Dec 1, 1999 06:21:24 pm"
To: kaiq@realtyideas.com
Date: Wed, 1 Dec 1999 19:18:37 -0500 (EST)
CC: jose soares <jose@sferacarta.com>, Ed Loehr <ELOEHR@austin.rr.com>,
"Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

no, you won't ;-)
further testing indicates that current_stamp like current, instead of
now/now().

Now I am confused. You say there is a difference between them?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Wed Dec 1 18:26:54 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA23781
for <pgsql-general@postgreSQL.org>; Wed, 1 Dec 1999 18:26:53 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id SAA10515;
Wed, 1 Dec 1999 18:21:24 -0600
Date: Wed, 1 Dec 1999 18:21:24 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: jose soares <jose@sferacarta.com>, Ed Loehr <ELOEHR@austin.rr.com>,
"Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199912011950.OAA04319@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912011817550.9191-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

no, you won't ;-)
further testing indicates that current_stamp like current, instead of
now/now().

also, I remembered (I tried to check the archive, but failed) now() should
not be use in where clause, cos it will hurt performance.

Kai

On Wed, 1 Dec 1999, Bruce Momjian wrote:

Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

I am changing my book to use CURRENT_TIMESTAMP rather than now().
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************

From bouncefilter Wed Dec 1 20:02:00 1999
Received: from fordfamilymarketing.com (jforddsl.wvi.com [204.245.255.187])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA35981
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 20:01:06 -0500 (EST)
(envelope-from stolkd@email.com)
Received: from email.com (localhost [127.0.0.1])
by fordfamilymarketing.com (8.9.3/8.9.3) with ESMTP id RAA05466
for <pgsql-general@postgresql.org>; Wed, 1 Dec 1999 17:00:35 -0800
Sender: root@fordfamilymarketing.com
Message-ID: <3845C4B3.8584AAD8@email.com>
Date: Wed, 01 Dec 1999 17:00:35 -0800
From: Daniel Stolk <stolkd@email.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Too large of a tuple corrupts table
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I seem to have a problem here. When I try to insert a tuple that is
larger than 8192 bytes, I get an error message saying that the tuple is
too large. Ok, that's fine. But the problem is that the table seems to
become corrupted. After I do this insert statement I went to psql and
did a select on the table (which doesn't have any tuples in it). So far
so good. But then I inserted a tuple that wasn't too large and when I
did a select on the table, I got an error message about the backend
going down or something like that. However, I then inserted another
tuple (that wasn't too large) into the table and it seemed to go fine
and when I looked at the file size of that table in the database's data
directory, the size went up. So the insert seems to still work but the
select doesn't?!?! What's going on here?

Thanks for any help, Daniel Stolk

From bouncefilter Wed Dec 1 20:40:56 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA40548
for <pgsql-general@hub.org>; Wed, 1 Dec 1999 20:40:14 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id JAA12535;
Thu, 2 Dec 1999 09:40:11 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma012523; Thu, 2 Dec 99 09:39:53 +0800
Message-Id: <3.0.5.32.19991202094032.00879230@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 02 Dec 1999 09:40:32 +0800
To: Manuel Cabido <manny@tinago.msuiit.edu.ph>, pgsql-general@hub.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Re: pgsql-general-digest V1 #550
In-Reply-To: <Pine.LNX.4.04.9912011750230.7164-100000@tinago.msuiit.edu.
ph>
References: <199912010402.XAA87578@hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi Manuel,

If security is an issue then it is a good idea to keep the part of the
application that accesses the database on a secure system. Because a lot of
bad things are possible if the entire application runs on an uncontrolled
client and is given great authority and direct access to the database.

Of course if you are only allowing SELECTs to a few nonsensitive tables
then it's not a problem. However if you are going to expand the application
later and it needs to do INSERTS etc, then maybe some thought has to go
into the architecture.

To be clear, you can still use Java with the 2nd architecture, it can be on
the client and/or the application server.

For java links try http://java.sun.com/
Or do a search for stuff like JDBC at www.google.com

I'm not too fond of Java myself - system programming language with the
"speed" of a scripting language. Plus, every other step you have to pay
significant money, unlike stuff like Perl,Python,Tcl.

Cheerio,

Link

At 05:53 PM 01-12-1999 +0800, Manuel Cabido wrote:

Sir:

I working on an application that needs to access the postgresql
database using a web page. Java was suggested to me as a very good
platform. Can anyone give me some ideas where i can obtain some components
like the database components available to delphi or visual basic which i
can use in my web page using java?

From bouncefilter Thu Dec 2 01:42:59 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA51291
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 01:42:15 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id IAA05886; Thu, 2 Dec 1999 08:46:15 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
IAA24259; Thu, 2 Dec 1999 08:42:10 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <384614C2.5D11E898@albourne.com>
Date: Thu, 02 Dec 1999 08:42:10 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Satyajeet Seth <csa98016@cse.iitd.ernet.in>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Except operation
References: <Pine.LNX.4.10.9912020021060.3476-100000@vibhas.cse.iitd.ernet.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Satyajeet Seth wrote:

Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:

You could try

select * from webdata w
where not exists
(select * from webdata1 w1
where w1.tid=w.tid
...
)

If you have the correct indexes on webdata1 this can be quite fast.

Adriaan

From bouncefilter Thu Dec 2 04:23:01 1999
Received: from ns.prov-liege.be (ns.prov-liege.be [193.190.122.12])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA70354
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 04:22:50 -0500 (EST)
(envelope-from Fabian.Frederick@prov-liege.be)
From: Fabian.Frederick@prov-liege.be
Received: by ns.prov-liege.be; (8.8.8/1.3/10May95) id JAA11228;
Thu, 2 Dec 1999 09:53:07 +0100 (GMT+0100)
Received: by mesepl.epl.prov-liege.be with Internet Mail Service (5.5.1960.3)
id <X599XPZS>; Thu, 2 Dec 1999 09:56:46 +0100
Message-ID: <17AB709C82E5D111ACF20000F805F4532B4160@mesadm.epl.prov-liege.be>
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] DB Statistics
Date: Thu, 2 Dec 1999 09:56:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

Someone could give me some link on Database Engine compare ?

Fabian
http://www.geocities.com/http://www.geocities.com/lonestar_teklords/

From bouncefilter Thu Dec 2 04:15:04 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id EAA69289
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 04:14:48 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Krokodil.DoCS.UU.SE (e99re41@Krokodil.DoCS.UU.SE
[130.238.9.184]) by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP
id KAA06791; Thu, 2 Dec 1999 10:14:46 +0100
Received: from localhost (e99re41@localhost) by Krokodil.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id KAA00907; Thu, 2 Dec 1999 10:14:44 +0100
X-Authentication-Warning: Krokodil.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Thu, 2 Dec 1999 10:14:43 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Massimo Pichini <massimo@webbridges.it>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres libpq library
In-Reply-To: <384537A9.F2FFBE62@webbridges.it>
Message-ID: <Pine.GSO.4.02A.9912021012030.893-100000@Krokodil.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 1 Dec 1999, Massimo Pichini wrote:

I guess that the postgres it-self is not designated as a multi-threaded
server. I was wondering if the library is instead thread safe (i.e.: if
it can be safely called from multi-threaded applications).

That's a definite no.

I'm not even sure if there is a chance of cleaning that up in finite time,
after all many C libraries are not very thread-safe either.

Perhaps this CORBA stuff that has been thrown around lately can help
there, but that's merely in the proposal stage right now.

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Thu Dec 2 06:41:03 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id GAA90262
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 06:40:05 -0500 (EST)
(envelope-from szi@do.khs-ag.de)
Received: (qmail 22781 invoked by uid 500); 2 Dec 1999 11:39:10 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: ALTER FUNCTION
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Sascha Ziemann <szi@khs-ag.de>
Date: 02 Dec 1999 12:39:10 +0100
Message-ID: <m3r9h5y3kx.fsf@intra.do.khs-ag.de>
Lines: 9
X-Mailer: Gnus v5.7/Emacs 20.4

Hi,

are there plans for an ALTER FUNCTION statement for Postgresql? I
think functions are completely unuseable, when it is not possible to
change the definition of a function. A bugfix in a function requires
the export of all data, a redefinition of the function and a complete
reimport. Or is there a simpler way?

Sascha

From bouncefilter Thu Dec 2 07:44:03 1999
Received: from oxmail.ox.ac.uk (oxmail2.ox.ac.uk [163.1.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA97860
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 07:43:27 -0500 (EST)
(envelope-from moray.mcconnachie@computing-services.oxford.ac.uk)
Received: from ermine.ox.ac.uk ([163.1.2.13])
by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1)
id 11tVa1-0003xX-00; Thu, 2 Dec 1999 12:43:25 +0000
Received: from ermine.ox.ac.uk ([163.1.2.13] helo=moraypc ident=root)
by ermine.ox.ac.uk with smtp (Exim 2.12 #1)
id 11tVa0-0004f6-00; Thu, 2 Dec 1999 12:43:25 +0000
Message-ID: <013c01bf3cc2$d25b6430$760e01a3@oucs.ox.ac.uk>
From: "Moray McConnachie" <moray.mcconnachie@computing-services.oxford.ac.uk>
To: <pgsql-general@postgresql.org>
Cc: "Sascha Ziemann" <szi@khs-ag.de>
References: <m3r9h5y3kx.fsf@intra.do.khs-ag.de>
Subject: Re: [GENERAL] ALTER FUNCTION
Date: Thu, 2 Dec 1999 12:43:22 -0000
Organization: Oxford University
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

UPDATE pg_proc SET prosrc='SQL statement' WHERE proname LIKE
'functionname';

seems to work for SQL queries at least. I doubt it's recommended,
though!

Moray

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk
----- Original Message -----
From: Sascha Ziemann <szi@khs-ag.de>
To: <pgsql-general@postgreSQL.org>
Sent: Thursday, December 02, 1999 11:39 AM
Subject: [GENERAL] ALTER FUNCTION

Hi,

are there plans for an ALTER FUNCTION statement for Postgresql? I
think functions are completely unuseable, when it is not possible to
change the definition of a function. A bugfix in a function

requires

the export of all data, a redefinition of the function and a

complete

reimport. Or is there a simpler way?

Sascha

************

From bouncefilter Thu Dec 2 08:04:04 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id IAA00564
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 08:03:08 -0500 (EST)
(envelope-from szi@do.khs-ag.de)
Received: (qmail 29167 invoked by uid 500); 2 Dec 1999 13:02:13 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: CREATE TRIGGER ON UPDATE
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Sascha Ziemann <szi@khs-ag.de>
Date: 02 Dec 1999 14:02:13 +0100
Message-ID: <m3ln7dxzqi.fsf@intra.do.khs-ag.de>
Lines: 66
X-Mailer: Gnus v5.7/Emacs 20.4

Hi,

Isn't it possible to change the data of a row from it's trigger
function?

I would like to have some update statistics in a database. So I
creeated a basetable with a number_of_updates attribute. Then I
created a child tables, that inherits the attributes. In order to
update the attributes I wrote a trigger function for the updates. But
it does not work. Is there something missing or is this not possible?

This shows what I have done:

----------------------------------------------------------------------
users=> CREATE TABLE basetable
users-> (
users-> created datetime DEFAULT 'now',
users-> last_modified datetime DEFAULT 'now',
users-> last_syncronized datetime DEFAULT '-infinity',
users-> number_of_updates int DEFAULT 0
users-> );
CREATE
users=>
users=> CREATE FUNCTION basetable_update() RETURNS opaque AS '
users'> BEGIN
users'> new.last_modified := now();
users'> new.number_of_updates := old.number_of_updates + 1;
users'> RETURN new;
users'> END;
users'> ' LANGUAGE 'plpgsql';
CREATE
users=>
users=> CREATE TABLE toptable
users-> (
users-> somedata1 text,
users-> somedata2 text
users-> )
users-> INHERITS (basetable);
CREATE
users=>
users=> CREATE TRIGGER toptable_update after UPDATE
users-> ON toptable FOR EACH ROW EXECUTE PROCEDURE basetable_update();
CREATE
users=>
users=> insert into toptable (somedata1) values ('jau');
INSERT 341407 1
users=> select somedata1, last_modified, number_of_updates from toptable;
somedata1|last_modified |number_of_updates
---------+----------------------------+-----------------
jau |Thu Dec 02 13:34:32 1999 MET| 0
(1 row)

users=> update toptable set somedata1 = 'jau neu' where somedata1 = 'jau';
UPDATE 1
users=> select somedata1, last_modified, number_of_updates from toptable;
somedata1|last_modified |number_of_updates
---------+----------------------------+-----------------
jau neu |Thu Dec 02 13:34:32 1999 MET| 0
(1 row)
----------------------------------------------------------------------

The number_of_updates attribute does not change, although the
basetable_update function writes it. Can anybody show me the error?

Sascha

From bouncefilter Thu Dec 2 08:09:04 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA01265
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 08:08:15 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id PAA07205; Thu, 2 Dec 1999 15:12:18 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
PAA22933; Thu, 2 Dec 1999 15:08:09 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <38466F38.E10C3889@albourne.com>
Date: Thu, 02 Dec 1999 15:08:08 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Sascha Ziemann <szi@khs-ag.de>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] ALTER FUNCTION
References: <m3r9h5y3kx.fsf@intra.do.khs-ag.de>
<013c01bf3cc2$d25b6430$760e01a3@oucs.ox.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Just drop the function, drop all triggers that use the function,
re-create the function and recreate all triggers. If the function is
called by other PL functions, you need to drop and re-install those as
well. If you keep them all in a big file, every one preceded by drop,
you can just reload the file (with \i into psql) whenever you have
changed something. No need to dump any data.

Adriaan

UPDATE pg_proc SET prosrc='SQL statement' WHERE proname LIKE
'functionname';

seems to work for SQL queries at least. I doubt it's recommended,
though!

are there plans for an ALTER FUNCTION statement for Postgresql? I
think functions are completely unuseable, when it is not possible to
change the definition of a function. A bugfix in a function

requires

the export of all data, a redefinition of the function and a

complete

reimport. Or is there a simpler way?

From bouncefilter Thu Dec 2 08:17:04 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id IAA02485
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 08:16:12 -0500 (EST)
(envelope-from szi@do.khs-ag.de)
Received: (qmail 30027 invoked by uid 500); 2 Dec 1999 13:15:16 -0000
Sender: szi@intra.do.khs-ag.de
To: Adriaan Joubert <a.joubert@albourne.com>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] ALTER FUNCTION
References: <m3r9h5y3kx.fsf@intra.do.khs-ag.de>
<013c01bf3cc2$d25b6430$760e01a3@oucs.ox.ac.uk>
<38466F38.E10C3889@albourne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Sascha Ziemann <szi@khs-ag.de>
Date: 02 Dec 1999 14:15:16 +0100
In-Reply-To: Adriaan Joubert's message of "Thu, 02 Dec 1999 15:08:08 +0200"
Message-ID: <m3iu2hxz4r.fsf@intra.do.khs-ag.de>
Lines: 19
X-Mailer: Gnus v5.7/Emacs 20.4

Adriaan Joubert <a.joubert@albourne.com> writes:

| Just drop the function, drop all triggers that use the function,
| re-create the function and recreate all triggers. If the function is
| called by other PL functions, you need to drop and re-install those as
| well. If you keep them all in a big file, every one preceded by drop,
| you can just reload the file (with \i into psql) whenever you have
| changed something. No need to dump any data.

When I use the function in a CHECK constrain of a table, I have to
destroy the table. Or is it possible to refresh the reference to the
function by an ALTER TABLE statement?

By the way: when I drop a table that is used by another table via
INHERITS, I get the warning, that the table is used and that I can not
drop it. Why are functions handled different? I is really a problem,
when there are broken tables in a database and nobody knows it.

Sascha

From bouncefilter Thu Dec 2 08:55:04 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id IAA27341
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 08:54:31 -0500 (EST)
(envelope-from szi@do.khs-ag.de)
Received: (qmail 31 invoked by uid 500); 2 Dec 1999 13:53:35 -0000
Sender: szi@intra.do.khs-ag.de
To: Holger Klawitter <holger@klawitter.de>
Subject: Re: [GENERAL] ALTER FUNCTION
Cc: pgsql-general@postgreSQL.org
References: <m3r9h5y3kx.fsf@intra.do.khs-ag.de>
<38466D5D.3AC92234@klawitter.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Sascha Ziemann <szi@khs-ag.de>
Date: 02 Dec 1999 14:53:35 +0100
In-Reply-To: Holger Klawitter's message of "Thu, 02 Dec 1999 14:00:13 +0100"
Message-ID: <m3bt89xxcw.fsf@intra.do.khs-ag.de>
Lines: 77
X-Mailer: Gnus v5.7/Emacs 20.4

Holger Klawitter <holger@klawitter.de> writes:

I think I didn't have expained the problem well enough:

Take a look at this example:

First I create a function that checks if the argument is 1:

users=> CREATE FUNCTION check_func(int) RETURNS boolean AS '
users'> BEGIN
users'> IF $1 = 1 THEN
users'> RETURN TRUE;
users'> ELSE
users'> RETURN FALSE;
users'> END IF;
users'> END;
users'> ' LANGUAGE 'plpgsql';
CREATE

Then I create a table that uses the function as an CHECK constrain:

users=> CREATE TABLE data_table
users-> (
users-> data int CHECK (check_func(data))
users-> );
CREATE

Now I can insert data into the table:

users=> INSERT INTO data_table (data) VALUES (1);
INSERT 341478 1

Later I find out that my check constrain was wrong and I drop the
function and create the new one:

users=> DROP FUNCTION check_func(int);
DROP
users=> CREATE FUNCTION check_func(int) RETURNS boolean AS '
users'> BEGIN
users'> IF $1 = 2 THEN
users'> RETURN TRUE;
users'> ELSE
users'> RETURN FALSE;
users'> END IF;
users'> END;
users'> ' LANGUAGE 'plpgsql';
CREATE

Now I insert the new data and find out that the data_table is broken:

users=> INSERT INTO data_table VALUES (1);
ERROR: init_fcache: Cache lookup failed for procedure 341467

Locking does not help here.

bis sp�ter...
Sascha

From bouncefilter Thu Dec 2 09:12:04 1999
Received: from guinness.urw.org (root@guinness.urw.org [209.32.194.52])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA42343
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 09:11:41 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from wookimus.net (chewie@wookimus.net [209.32.194.62])
by guinness.urw.org (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id IAA25399
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 08:11:29 -0600
Date: Thu, 2 Dec 1999 08:11:29 -0600 (CST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@guinness.urw.org
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] postgres libpq library
In-Reply-To: <Pine.GSO.4.02A.9912021012030.893-100000@Krokodil.DoCS.UU.SE>
Message-ID: <Pine.LNX.4.10.9912020808110.25390-100000@guinness.urw.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 2 Dec 1999, Peter Eisentraut wrote:

I guess that the postgres it-self is not designated as a multi-threaded
server. I was wondering if the library is instead thread safe (i.e.:
if it can be safely called from multi-threaded applications).

That's a definite no.

I'm not even sure if there is a chance of cleaning that up in finite
time, after all many C libraries are not very thread-safe either.

Perhaps this CORBA stuff that has been thrown around lately can help
there, but that's merely in the proposal stage right now.

You know. I, for one, have a little bit of free time I could donate to
contributing to the Postgresql project. I know C and would not mind
learning how to implement POSIX threading. Like any project, it needs
to start somewhere with someone. I suppose I should join the [HACKERS]
list, then, huh? ;-)

^chewie <chewie@wookimus.net>

From bouncefilter Thu Dec 2 10:59:06 1999
Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA51477
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 10:58:48 -0500 (EST)
(envelope-from moray.mcconnachie@computing-services.oxford.ac.uk)
Received: from ermine.ox.ac.uk ([163.1.2.13])
by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1)
id 11tXxd-0005ls-00; Thu, 2 Dec 1999 15:15:57 +0000
Received: from ermine.ox.ac.uk ([163.1.2.13] helo=moraypc ident=root)
by ermine.ox.ac.uk with smtp (Exim 2.12 #1)
id 11tXxd-0004m7-00; Thu, 2 Dec 1999 15:15:57 +0000
Message-ID: <000c01bf3cd8$2159a9b0$760e01a3@oucs.ox.ac.uk>
From: "Moray McConnachie" <moray.mcconnachie@computing-services.oxford.ac.uk>
To: <pgsql-general@postgresql.org>
Cc: <ELOEHR@austin.rr.com>
References: <199912010027.TAA26972@candle.pha.pa.us>
<38454038.9B953DFC@austin.rr.com>
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
Date: Thu, 2 Dec 1999 15:15:55 -0000
Organization: Oxford University
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0009_01BF3CD8.21059640"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01BF3CD8.21059640
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

With all this talk of rebuilding indices, the following script does it
for me:

#!/bin/sh
pg_dump -s databasename > filename
perl -pi -e 'unless (/CREATE.*INDEX/) {s/.*//;chomp;}' filename
perl -pi.create -e 's/CREATE.*?INDEX(.*?\s)ON.*/DROP INDEX$1\;/i;'
filename
mv filename filename.drop
psql -d databasename -c '\i filename.drop'
psql -d databasename -c '\i filename.create'

Of course there are bound to be a million ways of scripting this
without perl, but using awk or similar.

You could cron this up - I don't know if regular rebuilding
of indices helps minimise corruption?

Yours,
Moray

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk

------=_NextPart_000_0009_01BF3CD8.21059640
Content-Type: text/plain;
name="Re [GENERAL] FATAL 1 my bits moved right off the end of
theworld!.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Re [GENERAL] FATAL 1 my bits moved right off the end of
theworld!.txt"

With all this talk of rebuilding indices, the following script does it
for me:

#!/bin/sh
pg_dump -s databasename > filename
perl -pi -e 'unless (/CREATE.*INDEX/) {s/.*//;chomp;};$old=3D$_;'
filename
perl -pi.create -e 's/CREATE.*?INDEX(.*?\s)ON.*/DROP INDEX$1\;/i;'
filename
mv filename filename.drop
psql -d databasename -c '\i filename.drop'
psql -d databasename -c '\i filename.create'

Of course there are bound to be a million ways of scripting this
without perl, but using awk or similar.
You could cron this up, of course - I don't know if regular rebuilding
of indices helps minimise corruption?
Yours,
Moray

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk

------=_NextPart_000_0009_01BF3CD8.21059640--

From bouncefilter Thu Dec 2 11:21:07 1999
Received: from picasso.realtyideas.com (IDENT:root@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA55951
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 11:20:28 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id JAA20009;
Thu, 2 Dec 1999 09:50:25 -0600
Date: Thu, 2 Dec 1999 09:50:25 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199912011950.OAA04319@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912020943400.19647-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Here is the test. I did not put it in mail because pine did not like
cut/paste. now I find a way to do it. It looks good!
the conclusion: current_timestamp is "current" -- it should be,
the looks closer than now/now() :-)

###############################################################
test3=> drop table account;

DROP
test3=> CREATE TABLE account (

test3-> act char(1) default 'Y',

test3-> createdfunc DATETIME DEFAULT now(),

test3-> createdcons DATETIME DEFAULT 'now',

test3-> created2cons DATETIME DEFAULT 'current_timestamp',

test3-> createdcurr DATETIME DEFAULT 'current'

test3-> );

CREATE
test3=>

test3=>

test3=> insert into account values('y');

INSERT 283346 1
test3=> insert into account values('1');
INSERT 283347 1
test3=> insert into account (createdcons) values(now());

INSERT 283348 1
test3=> insert into account (createdcons) values(now);

ERROR: Attribute now not found
test3=> insert into account (createdcons) values('now');

INSERT 283349 1
test3=> insert into account (createdcons) values(current);

ERROR: Attribute current not found
test3=> insert into account (createdcons) values('current');

INSERT 283350 1
test3=> insert into account (createdcons) values(current_timestamp);

INSERT 283351 1
test3=> insert into account (createdcons) values('current_timestamp');

INSERT 283352 1
test3=>
test3=> insert into account (createdcons) values(current_timestamp());

ERROR: parser: parse error at or near ")"
test3=> insert into account (createdcons) values(current_timestamp(now));

ERROR: parser: parse error at or near "now"
test3=> insert into account (createdcons) values(current_timestamp('now'));

ERROR: parser: parse error at or near "'"
test3=> insert into account (createdcons) values(now(current_timestamp));

ERROR: No such function 'now' with the specified attributes
test3=>

test3=> select * from account;

test3=> select * from account where createdcons = 'now';

test3=> select * from account where createdcons = now();

test3=> select * from account where createdcons = 'current_timestamp';

test3=> select * from account where createdcons = current_timestamp();

ERROR: parser: parse error at or near ")"
test3=> select * from account where createdcons = current_timestamp('now');

ERROR: parser: parse error at or near "'"
test3=> select * from account where createdcons = 'current_timestamp('now')';

ERROR: parser: parse error at or near "now"

##############################################################
On Wed, 1 Dec 1999, Bruce Momjian wrote:

Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

I am changing my book to use CURRENT_TIMESTAMP rather than now().
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************

From bouncefilter Thu Dec 2 11:49:06 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA60948
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 11:49:05 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11tZPG-0004tn-00
for pgsql-general@postgresql.org; Thu, 2 Dec 1999 16:48:34 +0000
Date: Thu, 2 Dec 1999 16:48:34 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: pgsql-general@postgresql.org
Subject: Upper/lower case passwords
Message-ID: <Pine.BSO.4.10.9912021645430.23604-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

I've come across this in the past day or so, is anyone else aware of the
issue?

(I've looked over the list archives, the feature list and todo list, with
no joy).

When creating a user with a password, the password is always converted to
it's lower case equivalent - no upper case characters are allowed. Enter a
password with upper case characters in it, and if you try to connect with
that it will fail - you need to use all lower case.

I'm going to look at the source code to try and resolve this, but before I
do, has anyone found the problem and solved it yet?

I'm using Postgresql 6.5.0 on OpenBSD 6.5

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Thu Dec 2 11:14:08 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA54570
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 11:13:21 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id LAA21882;
Thu, 2 Dec 1999 11:07:23 -0600
Date: Thu, 2 Dec 1999 11:07:23 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Adriaan Joubert <a.joubert@albourne.com>
cc: Satyajeet Seth <csa98016@cse.iitd.ernet.in>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Except operation
In-Reply-To: <384614C2.5D11E898@albourne.com>
Message-ID: <Pine.LNX.4.10.9912021103300.21346-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

how about I'm a sql92 lover? :-)

the idea is to use index. but the engine only use index when it sees
"where". so, how about add "where w.tid = w.tid" to the first (or
both) select on the two sides of the except?

not tested. if work, please let us know, thanks.

Kai
On Thu, 2 Dec 1999, Adriaan Joubert wrote:

Satyajeet Seth wrote:

Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:

You could try

select * from webdata w
where not exists
(select * from webdata1 w1
where w1.tid=w.tid
...
)

If you have the correct indexes on webdata1 this can be quite fast.

Adriaan

************

From bouncefilter Thu Dec 2 12:57:07 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA70638
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 12:55:54 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA01049;
Thu, 2 Dec 1999 12:44:27 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912021744.MAA01049@candle.pha.pa.us>
Subject: Re: [GENERAL] Upper/lower case passwords
In-Reply-To: <Pine.BSO.4.10.9912021645430.23604-100000@office.knowledge.com>
from Mark Jewiss at "Dec 2, 1999 04:48:34 pm"
To: Mark Jewiss <Mark.Jewiss@knowledge.com>
Date: Thu, 2 Dec 1999 12:44:27 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hello,

I've come across this in the past day or so, is anyone else aware of the
issue?

(I've looked over the list archives, the feature list and todo list, with
no joy).

When creating a user with a password, the password is always converted to
it's lower case equivalent - no upper case characters are allowed. Enter a
password with upper case characters in it, and if you try to connect with
that it will fail - you need to use all lower case.

I'm going to look at the source code to try and resolve this, but before I
do, has anyone found the problem and solved it yet?

Put double-quotes around the password when you create it.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 13:00:07 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA70877
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 12:59:00 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA01084;
Thu, 2 Dec 1999 12:46:02 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912021746.MAA01084@candle.pha.pa.us>
Subject: Re: [GENERAL] book's pdf link/archive/documentation
In-Reply-To:
<Pine.LNX.4.10.9912021151300.23060-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Dec 2, 1999 12:02:48 pm"
To: kaiq@realtyideas.com
Date: Thu, 2 Dec 1999 12:46:02 -0500 (EST)
CC: The Hermit Hacker <scrappy@hub.org>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Also, is the documentation still updating routinely? how often? is the
documentation also has "releases" (I hope), do you sent notice to
the listing when you update the documentation? thanks.

If you mean the book, it is updated every day.
-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 12:08:07 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA63882
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 12:07:39 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id MAA23229;
Thu, 2 Dec 1999 12:02:48 -0600
Date: Thu, 2 Dec 1999 12:02:48 -0600 (CST)
From: <kaiq@realtyideas.com>
To: The Hermit Hacker <scrappy@hub.org>
cc: pgsql-general@postgreSQL.org
Subject: book's pdf link/archive/documentation
In-Reply-To: <Pine.BSF.4.21.9912011857490.823-100000@thelab.hub.org>
Message-ID: <Pine.LNX.4.10.9912021151300.23060-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

it works now -- exactly as you predicted/promised. thanks.
sounds you are going to make big changes, will it affect the everyday
perform of those mail listings?

another thing: is there a way to download a (or a few) big text files
of those listing archives, so that I can simply use vi to do the search
locally?

Also, is the documentation still updating routinely? how often? is the
documentation also has "releases" (I hope), do you sent notice to
the listing when you update the documentation? thanks.

On Wed, 1 Dec 1999, The Hermit Hacker wrote:

On Wed, 1 Dec 1999 kaiq@realtyideas.com wrote:

yes. good for netscape. I forgot I hate M$ ;-)
I'm going to read it word by word to systemize my sql/pg knowledge.

Another thing: the general and sql mailing lists' search do not work now.
they only return 1,2,3,... empty links, no content.

Remind me about this after tomorrow...tomorrow we're doing a major upgrade
to the server...moving the machine and drives into rackmounted cases, and
more disk space, etc, etc...once that is done, I want to play with the
udmsearch software that uses PostgreSQL for a backend and see if that will
do what ht/dig is currently doing now...
thanks!

On Wed, 1 Dec 1999, Bruce Momjian wrote:
I can not get THE book's pdf link. Not sure whether it
is my side's irregular firewall issue. If in that case,
can it be a http link? I guess I question/request is:
seems the ftp link is broken? if not, can it be a http one?

I can get it via Netscape without problems. Sorry.
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

************

From bouncefilter Thu Dec 2 13:26:08 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA76027
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 13:26:04 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA08359;
Thu, 2 Dec 1999 13:25:25 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912021825.NAA08359@candle.pha.pa.us>
Subject: Re: [GENERAL] book's pdf link/archive/documentation
In-Reply-To:
<Pine.LNX.4.10.9912021312550.23334-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Dec 2, 1999 01:17:38 pm"
To: kaiq@realtyideas.com
Date: Thu, 2 Dec 1999 13:25:25 -0500 (EST)
CC: The Hermit Hacker <scrappy@hub.org>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I mean the documentation proper :-) I want to know any new info added.
as for the book, I also hope (I know I ask too much tho) I can have
a "what's new" or a "diff" thing, so that if I read it now, I do not
need to read it over and over again. any solutions for that. Otherwise,
people tend to wait until it gets stable.

Documention is updated mostly before each release.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 13:27:07 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA76150
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 13:26:54 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.28.74.220]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Thu, 2 Dec 1999 12:18:53 -0600
Sender: ed
Message-ID: <3846BA0F.16F8F28@austin.rr.com>
Date: Thu, 02 Dec 1999 12:27:27 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Moray McConnachie <moray.mcconnachie@computing-services.oxford.ac.uk>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
References: <199912010027.TAA26972@candle.pha.pa.us>
<38454038.9B953DFC@austin.rr.com>
<000c01bf3cd8$2159a9b0$760e01a3@oucs.ox.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks. As your example demonstrates, automating a rebuild of indices via cron/perl/DBI is pretty straighforward. Unfortunately, reliability and
usability concerns in my application strongly suggest that the corrupted index really needs to be identified and rebuilt in real-time to allow the
original failed queries to be automatically retried to success, albeit a bit slower. Taking the system off-line to rebuild the corrupted index is *very*
undesirable. If I could get a true error indication in real-time from DBI/DBD::Pg that this was the problem, I think I could rebuild the index on the
fly. Not sure enough PG error information and/or codes are being returned to sufficiently identify the problem, though.

Cheers.
Ed

Moray McConnachie wrote:

With all this talk of rebuilding indices, the following script does it
for me:

#!/bin/sh
pg_dump -s databasename > filename
perl -pi -e 'unless (/CREATE.*INDEX/) {s/.*//;chomp;}' filename
perl -pi.create -e 's/CREATE.*?INDEX(.*?\s)ON.*/DROP INDEX$1\;/i;'
filename
mv filename filename.drop
psql -d databasename -c '\i filename.drop'
psql -d databasename -c '\i filename.create'

Of course there are bound to be a million ways of scripting this
without perl, but using awk or similar.

You could cron this up - I don't know if regular rebuilding
of indices helps minimise corruption?

Yours,
Moray

----------------------------------------------------------------------
----------------
Moray.McConnachie@computing-services.oxford.ac.uk

----------------------------------------------------------------------
Name: Re [GENERAL] FATAL 1 my bits moved right off the end of theworld!.txt
Re [GENERAL] FATAL 1 my bits moved right off the end of theworld!.txt Type: Plain Text (text/plain)
Encoding: quoted-printable

From bouncefilter Thu Dec 2 14:17:08 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA85280
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 14:16:22 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.28.74.220]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Thu, 2 Dec 1999 13:16:09 -0600
Sender: ed
Message-ID: <3846C590.29422D0A@austin.rr.com>
Date: Thu, 02 Dec 1999 13:16:32 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: kaiq@realtyideas.com
CC: Bruce Momjian <pgman@candle.pha.pa.us>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
References: <Pine.LNX.4.10.9912020943400.19647-100000@picasso.realtyideas.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

kaiq@realtyideas.com wrote:

Here is the test. I did not put it in mail because pine did not like
cut/paste. now I find a way to do it. It looks good!
the conclusion: current_timestamp is "current" -- it should be,
the looks closer than now/now() :-)

I don't think that's quite true, at least on v6.5.2.

Single quotes make a big difference, both on the declaration
in CREATE and on the input params to INSERT. Here's
an example...

CREATE TABLE mytable (
id SERIAL,
note VARCHAR,
dt1 DATETIME DEFAULT CURRENT_TIMESTAMP,
dt2 DATETIME DEFAULT 'CURRENT_TIMESTAMP'
);

INSERT INTO mytable (note) VALUES
('True default datetime values');
INSERT INTO mytable (note,dt1) VALUES
('dt1 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt1) VALUES
('dt1 input as current_timestamp',current_timestamp);
INSERT INTO mytable (note,dt2) VALUES
('dt2 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt2) VALUES
('dt2 input as current_timestamp',current_timestamp);

SELECT * FROM mytable;

The results:

And with 'current' and 'now' as column types...

DROP SEQUENCE mytable_id_seq;
DROP TABLE mytable;
CREATE TABLE mytable (
id SERIAL,
note VARCHAR,
dt3 DATETIME DEFAULT 'current',
dt4 DATETIME DEFAULT 'now'
);

INSERT INTO mytable (note) VALUES
('True default datetime values');
INSERT INTO mytable (note,dt3) VALUES
('dt3 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt3) VALUES
('dt3 input as current_timestamp',current_timestamp);
INSERT INTO mytable (note,dt4) VALUES
('dt4 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt4) VALUES
('dt4 input as current_timestamp',current_timestamp);

SELECT * FROM mytable;

Results:

Cheers.
Ed Loehr

###############################################################
test3=> drop table account;

DROP
test3=> CREATE TABLE account (

test3-> act char(1) default 'Y',

test3-> createdfunc DATETIME DEFAULT now(),

test3-> createdcons DATETIME DEFAULT 'now',

test3-> created2cons DATETIME DEFAULT 'current_timestamp',

test3-> createdcurr DATETIME DEFAULT 'current'

test3-> );

CREATE
test3=>

test3=>

test3=> insert into account values('y');

INSERT 283346 1
test3=> insert into account values('1');
INSERT 283347 1
test3=> insert into account (createdcons) values(now());

INSERT 283348 1
test3=> insert into account (createdcons) values(now);

ERROR: Attribute now not found
test3=> insert into account (createdcons) values('now');

INSERT 283349 1
test3=> insert into account (createdcons) values(current);

ERROR: Attribute current not found
test3=> insert into account (createdcons) values('current');

INSERT 283350 1
test3=> insert into account (createdcons) values(current_timestamp);

INSERT 283351 1
test3=> insert into account (createdcons) values('current_timestamp');

INSERT 283352 1
test3=>
test3=> insert into account (createdcons) values(current_timestamp());

ERROR: parser: parse error at or near ")"
test3=> insert into account (createdcons) values(current_timestamp(now));

ERROR: parser: parse error at or near "now"
test3=> insert into account (createdcons) values(current_timestamp('now'));

ERROR: parser: parse error at or near "'"
test3=> insert into account (createdcons) values(now(current_timestamp));

ERROR: No such function 'now' with the specified attributes
test3=>

test3=> select * from account;

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:33 1999 CST|current |current
1 |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:33 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(7 rows)

test3=> select * from account where createdcons = 'now';

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = now();

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = 'current';
act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = 'current_timestamp';

act|createdfunc |createdcons|created2cons|createdcurr
---+----------------------------+-----------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(2 rows)

test3=> select * from account where createdcons = current_timestamp();

ERROR: parser: parse error at or near ")"
test3=> select * from account where createdcons = current_timestamp('now');

ERROR: parser: parse error at or near "'"
test3=> select * from account where createdcons = 'current_timestamp('now')';

ERROR: parser: parse error at or near "now"

##############################################################
On Wed, 1 Dec 1999, Bruce Momjian wrote:
Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

I am changing my book to use CURRENT_TIMESTAMP rather than now().
--
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************
************

From bouncefilter Thu Dec 2 13:24:07 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA75444
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 13:23:52 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id NAA24419;
Thu, 2 Dec 1999 13:17:38 -0600
Date: Thu, 2 Dec 1999 13:17:38 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: The Hermit Hacker <scrappy@hub.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] book's pdf link/archive/documentation
In-Reply-To: <199912021746.MAA01084@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912021312550.23334-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I mean the documentation proper :-) I want to know any new info added.
as for the book, I also hope (I know I ask too much tho) I can have
a "what's new" or a "diff" thing, so that if I read it now, I do not
need to read it over and over again. any solutions for that. Otherwise,
people tend to wait until it gets stable.

kai

On Thu, 2 Dec 1999, Bruce Momjian wrote:

Also, is the documentation still updating routinely? how often? is the
documentation also has "releases" (I hope), do you sent notice to
the listing when you update the documentation? thanks.
If you mean the book, it is updated every day.
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 14:05:08 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA83121
for <pgsql-general@postgresql.org>; Thu, 2 Dec 1999 14:04:23 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id NAA25885;
Thu, 2 Dec 1999 13:57:44 -0600
Date: Thu, 2 Dec 1999 13:57:44 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199912021827.NAA08460@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912021352190.25587-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I rechecked the results I sent before, it is not clear, becuase I
run it as a batch. I need a sleep :-) but I do not if there is
a sleep in sql or psql command. so, I use the vaccum! (this is
a development machine!). I re-run it, it looks good now!

anybody know any sleep-like thing for sql ?
##############################################################
test3=> drop table account;

DROP
test3=> CREATE TABLE account (

test3-> act char(1) default 'Y',

test3-> createdfunc DATETIME DEFAULT now(),

test3-> createdcons DATETIME DEFAULT 'now',

test3-> created2cons DATETIME DEFAULT 'current_timestamp',

test3-> createdcurr DATETIME DEFAULT 'current'

test3-> );

CREATE
test3=>

test3=>

test3=> insert into account values('y');

INSERT 283378 1
test3=> vacuum;
VACUUM
test3=> insert into account values('1');

INSERT 283379 1
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values(now());

INSERT 283380 1
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values(now);

ERROR: Attribute now not found
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values('now');

INSERT 283381 1
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values(current);
ERROR: Attribute current not found
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values('current');

INSERT 283382 1
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values(current_timestamp);

INSERT 283383 1
test3=> vacuum;

VACUUM
test3=> insert into account (createdcons) values('current_timestamp');

INSERT 283384 1
test3=> insert into account (createdcons) values(current_timestamp());

ERROR: parser: parse error at or near ")"
test3=> insert into account (createdcons) values(current_timestamp(now));

ERROR: parser: parse error at or near "now"
test3=> insert into account (createdcons) values(current_timestamp('now'));
ERROR: parser: parse error at or near "'"
test3=> insert into account (createdcons) values(now(current_timestamp));

ERROR: No such function 'now' with the specified attributes
test3=> select * from account;

test3=> select * from account where createdcons = 'now';

test3=> select * from account where createdcons = 'current';

test3=> select * from account where createdcons = 'current_timestamp';

test3=> select * from account where createdcons = current_timestamp();

ERROR: parser: parse error at or near ")"
test3=> select * from account where createdcons = current_timestamp('now');
ERROR: parser: parse error at or near "'"
test3=> select * from account where createdcons = 'current_timestamp('now')';

ERROR: parser: parse error at or near "now"
test3=> select * from account where createdcons = 'current_timestamp()';

test3=> select * from account where createdcons = 'current_timestamp(now())';

test3=>

#############################################################
On Thu, 2 Dec 1999, Bruce Momjian wrote:

Can you resend the results you had. I can't see the difference.
no. "CURRENT_TIMESTAMP" is the same as "current", which
is very very different from "now", which, in turn, also
delicately different from "now()" .

"current" is not very usefule. If you put "current" in db,
it remains there, until when you retrieve the dada, i.e.,
it is the "retrieve time". while "now" is our fmailiar
"modified time".

conclusion: you were right in you book! keep using "now()".
(except in where-clause, you should use "now" instead)
-- until the now-'feature' is fixed, after that, we can use
"now" everywhere).

remaining questions: 1) is the behavior of "now" in create
table a bug or feature?
2) is "CURRENT_TIMESTAMP" = "current" a bug or not? --
need a real sql92 lover here. anybody idea?

Kai

On Thu, 2 Dec 1999, Bruce Momjian wrote:
Here is the test. I did not put it in mail because pine did not like
cut/paste. now I find a way to do it. It looks good!
the conclusion: current_timestamp is "current" -- it should be,
the looks closer than now/now() :-)

So CURRENT_TIMESTAMP is the same as now(), right?
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 15:05:09 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA92921
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 15:04:20 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id PAA29118;
Thu, 2 Dec 1999 15:00:45 -0500
Message-ID: <3846D069.79EF1543@mascari.com>
Date: Thu, 02 Dec 1999 15:02:49 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: kaiq@realtyideas.com
CC: Adriaan Joubert <a.joubert@albourne.com>,
Satyajeet Seth <csa98016@cse.iitd.ernet.in>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Except operation
References: <Pine.LNX.4.10.9912021103300.21346-100000@picasso.realtyideas.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

kaiq@realtyideas.com wrote:

how about I'm a sql92 lover? :-)

the idea is to use index. but the engine only use index when it sees
"where". so, how about add "where w.tid = w.tid" to the first (or
both) select on the two sides of the except?

not tested. if work, please let us know, thanks.

Kai

That's not the problem. The problem is that the INTERSECT/EXCEPT code
uses the query rewriter to automatically rewrite the query to something
like:

SELECT * FROM webdata w
WHERE (<webdata.fieldlist>) NOT IN (
SELECT * FROM webdata1);

and 'IN' clauses in PostgreSQL can't use indices. The result is always a
sequential scan on the IN values. INTERSECT/EXCEPT should have been
written to rewrite the query using correlated subqueries and the EXISTS
test, as Adriaan suggests below. In fact, one of the possible solutions
for the un-usability of IN clauses is to have PostgreSQL rewrite those as
EXISTS....but no one's done that yet.

Mike

On Thu, 2 Dec 1999, Adriaan Joubert wrote:

Satyajeet Seth wrote:

Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:

You could try

select * from webdata w
where not exists
(select * from webdata1 w1
where w1.tid=w.tid
...
)

If you have the correct indexes on webdata1 this can be quite fast.

Adriaan

From bouncefilter Thu Dec 2 15:30:09 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA09434
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 15:29:03 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
PAA19946;
Thu, 2 Dec 1999 15:23:58 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912022023.PAA19946@candle.pha.pa.us>
Subject: Re: [GENERAL] Date & Time
In-Reply-To:
<Pine.LNX.4.10.9912021444270.26323-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Dec 2, 1999 03:08:53 pm"
To: kaiq@realtyideas.com
Date: Thu, 2 Dec 1999 15:23:58 -0500 (EST)
CC: Ed Loehr <ELOEHR@austin.rr.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I agree. my fault. sql92 constant is "global", it should not be in single
quotation mark, while pg's "now" is datetime's constant, it should be in
single quotation mark.

seems we do not need now/now() anymore!!!

seems that the problem/feature is the "current" implementation: it only
compare the beginning of the word. interesting!

Ah, but look at this under current tree:

test=> create table kk (x datetime default current_timestamp);
CREATE
test=> \d kk
Table "kk"
Attribute | Type | Extra
-----------+----------+------------------------------------------
x | datetime | default timestamp(datetime('now'::text))

Internally, it is using 'now'.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 15:18:09 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA07708
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 15:17:37 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id PAA27283;
Thu, 2 Dec 1999 15:08:53 -0600
Date: Thu, 2 Dec 1999 15:08:53 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Ed Loehr <ELOEHR@austin.rr.com>
cc: Bruce Momjian <pgman@candle.pha.pa.us>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <3846C590.29422D0A@austin.rr.com>
Message-ID: <Pine.LNX.4.10.9912021444270.26323-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I agree. my fault. sql92 constant is "global", it should not be in single
quotation mark, while pg's "now" is datetime's constant, it should be in
single quotation mark.

seems we do not need now/now() anymore!!!

seems that the problem/feature is the "current" implementation: it only
compare the beginning of the word. interesting!

On Thu, 2 Dec 1999, Ed Loehr wrote:

kaiq@realtyideas.com wrote:

Here is the test. I did not put it in mail because pine did not like
cut/paste. now I find a way to do it. It looks good!
the conclusion: current_timestamp is "current" -- it should be,
the looks closer than now/now() :-)

I don't think that's quite true, at least on v6.5.2.

Single quotes make a big difference, both on the declaration
in CREATE and on the input params to INSERT. Here's
an example...

CREATE TABLE mytable (
id SERIAL,
note VARCHAR,
dt1 DATETIME DEFAULT CURRENT_TIMESTAMP,
dt2 DATETIME DEFAULT 'CURRENT_TIMESTAMP'
);

INSERT INTO mytable (note) VALUES
('True default datetime values');
INSERT INTO mytable (note,dt1) VALUES
('dt1 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt1) VALUES
('dt1 input as current_timestamp',current_timestamp);
INSERT INTO mytable (note,dt2) VALUES
('dt2 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt2) VALUES
('dt2 input as current_timestamp',current_timestamp);

SELECT * FROM mytable;

The results:

test=> SELECT * FROM mytable;
id|note |dt1 |dt2
--+--------------------------------+----------------------------+----------------------------
1|True default datetime values |Thu Dec 02 13:07:41 1999 CST|current
2|dt1 input as 'current_timestamp'|current |current
3|dt1 input as current_timestamp |Thu Dec 02 13:07:41 1999 CST|current
4|dt2 input as 'current_timestamp'|Thu Dec 02 13:07:41 1999 CST|current
5|dt2 input as current_timestamp |Thu Dec 02 13:07:41 1999 CST|Thu Dec 02 13:07:41 1999 CST
(5 rows)

And with 'current' and 'now' as column types...

DROP SEQUENCE mytable_id_seq;
DROP TABLE mytable;
CREATE TABLE mytable (
id SERIAL,
note VARCHAR,
dt3 DATETIME DEFAULT 'current',
dt4 DATETIME DEFAULT 'now'
);

INSERT INTO mytable (note) VALUES
('True default datetime values');
INSERT INTO mytable (note,dt3) VALUES
('dt3 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt3) VALUES
('dt3 input as current_timestamp',current_timestamp);
INSERT INTO mytable (note,dt4) VALUES
('dt4 input as ''current_timestamp''','current_timestamp');
INSERT INTO mytable (note,dt4) VALUES
('dt4 input as current_timestamp',current_timestamp);

SELECT * FROM mytable;

Results:

test=> SELECT * FROM mytable;
id|note |dt3 |dt4
--+--------------------------------+----------------------------+----------------------------
1|True default datetime values |current |Thu Dec 02 13:10:24 1999 CST
2|dt3 input as 'current_timestamp'|current |Thu Dec 02 13:10:24 1999 CST
3|dt3 input as current_timestamp |Thu Dec 02 13:10:25 1999 CST|Thu Dec 02 13:10:24 1999 CST
4|dt4 input as 'current_timestamp'|current |current
5|dt4 input as current_timestamp |current |Thu Dec 02 13:10:25 1999 CST
(5 rows)

Cheers.
Ed Loehr
###############################################################
test3=> drop table account;

DROP
test3=> CREATE TABLE account (

test3-> act char(1) default 'Y',

test3-> createdfunc DATETIME DEFAULT now(),

test3-> createdcons DATETIME DEFAULT 'now',

test3-> created2cons DATETIME DEFAULT 'current_timestamp',

test3-> createdcurr DATETIME DEFAULT 'current'

test3-> );

CREATE
test3=>

test3=>

test3=> insert into account values('y');

INSERT 283346 1
test3=> insert into account values('1');
INSERT 283347 1
test3=> insert into account (createdcons) values(now());

INSERT 283348 1
test3=> insert into account (createdcons) values(now);

ERROR: Attribute now not found
test3=> insert into account (createdcons) values('now');

INSERT 283349 1
test3=> insert into account (createdcons) values(current);

ERROR: Attribute current not found
test3=> insert into account (createdcons) values('current');

INSERT 283350 1
test3=> insert into account (createdcons) values(current_timestamp);

INSERT 283351 1
test3=> insert into account (createdcons) values('current_timestamp');

INSERT 283352 1
test3=>
test3=> insert into account (createdcons) values(current_timestamp());

ERROR: parser: parse error at or near ")"
test3=> insert into account (createdcons) values(current_timestamp(now));

ERROR: parser: parse error at or near "now"
test3=> insert into account (createdcons) values(current_timestamp('now'));

ERROR: parser: parse error at or near "'"
test3=> insert into account (createdcons) values(now(current_timestamp));

ERROR: No such function 'now' with the specified attributes
test3=>

test3=> select * from account;

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:33 1999 CST|current |current
1 |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:33 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(7 rows)

test3=> select * from account where createdcons = 'now';

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = now();

act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = 'current';
act|createdfunc |createdcons |created2cons|createdcurr
---+----------------------------+----------------------------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|Thu Dec 02 08:41:34 1999 CST|current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(5 rows)

test3=> select * from account where createdcons = 'current_timestamp';

act|createdfunc |createdcons|created2cons|createdcurr
---+----------------------------+-----------+------------+-----------
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
Y |Thu Dec 02 08:41:34 1999 CST|current |current |current
(2 rows)

test3=> select * from account where createdcons = current_timestamp();

ERROR: parser: parse error at or near ")"
test3=> select * from account where createdcons = current_timestamp('now');

ERROR: parser: parse error at or near "'"
test3=> select * from account where createdcons = 'current_timestamp('now')';

ERROR: parser: parse error at or near "now"

##############################################################
On Wed, 1 Dec 1999, Bruce Momjian wrote:
Ed Loehr ha scritto:

Just curious: anyone have any comment on any practical differences between now() and CURRENT_TIMESTAMP, which seems to work
the same?

I think it is the same function, both of them return the current date and time.

now() should be the internal postgreSQL function.
and CURRENT_TIMESTAMP is the exact SQL-92 syntax

I am changing my book to use CURRENT_TIMESTAMP rather than now().
--
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************
************

From bouncefilter Thu Dec 2 16:19:10 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA17568
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 16:18:56 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
QAA21159;
Thu, 2 Dec 1999 16:17:20 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912022117.QAA21159@candle.pha.pa.us>
Subject: Re: [GENERAL] Date & Time
In-Reply-To:
<Pine.LNX.4.10.9912021600530.27385-100000@picasso.realtyideas.com>
from "kaiq@realtyideas.com" at "Dec 2, 1999 04:04:50 pm"
To: kaiq@realtyideas.com
Date: Thu, 2 Dec 1999 16:17:20 -0500 (EST)
CC: Ed Loehr <ELOEHR@austin.rr.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

in ""current" implementation", I mean the implementation of "current". OK,
my fault again. I'm beaten :-) thanks

for 6.5.1 that I'm using, it is: "datetime default now()"

Table "kk"
Attribute | Type | Extra
-----------+----------+------------------------------------------
x | datetime | default timestamp(datetime('now'::text))

Internally, it is using 'now'.

I think it was changed by Tom to fix a problem with default handling for
dates.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 2 16:32:10 1999
Received: from studserv.stud.uni-hannover.de
(root@studserv.stud.uni-hannover.de [130.75.176.2])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA20771
for <pgsql-general@hub.org>; Thu, 2 Dec 1999 16:32:01 -0500 (EST)
(envelope-from awer@stud.uni-hannover.de)
Received: from stud.uni-hannover.de (aw@a115.home.uni-hannover.de
[130.75.232.115])
by studserv.stud.uni-hannover.de (8.9.3/8.9.3/1) with ESMTP id WAA19890
for <pgsql-general@hub.org>; Thu, 2 Dec 1999 22:31:53 +0100 (MET)
Sender: Astrid.Wolf@stud.uni-hannover.de
Message-ID: <3846E516.AAB04A26@stud.uni-hannover.de>
Date: Thu, 02 Dec 1999 22:31:02 +0100
From: Andreas Werner <Andreas.Werner@stud.uni-hannover.de>
Reply-To: aw@kammer.uni-hannover.de
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.7 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: errormsg?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I'm geting messages like this in my postgresgl.log:

NOTICE: SIAssignBackendId: discarding tag 2147476827
FATAL 1: Backend cache invalidation initialization failed

What's the problem and how can I fix it. Where can I get
more informations about this errormsg's?

Thanks

Andreas Werner

mailto: aw@kammer.uni-hannover.de

From bouncefilter Thu Dec 2 16:11:09 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA16146
for <pgsql-general@postgreSQL.org>; Thu, 2 Dec 1999 16:10:16 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id QAA28352;
Thu, 2 Dec 1999 16:04:50 -0600
Date: Thu, 2 Dec 1999 16:04:50 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: Ed Loehr <ELOEHR@austin.rr.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199912022023.PAA19946@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.10.9912021600530.27385-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

in ""current" implementation", I mean the implementation of "current". OK,
my fault again. I'm beaten :-) thanks

for 6.5.1 that I'm using, it is: "datetime default now()"

I agree. my fault. sql92 constant is "global", it should

not be in single

quotation mark, while pg's "now" is datetime's constant, it should be in
single quotation mark.

seems we do not need now/now() anymore!!!

seems that the problem/feature is the "current" implementation: it only
compare the beginning of the word. interesting!

Ah, but look at this under current tree:

test=> create table kk (x datetime default current_timestamp);
CREATE
test=> \d kk
Table "kk"
Attribute | Type | Extra
-----------+----------+------------------------------------------
x | datetime | default timestamp(datetime('now'::text))

Internally, it is using 'now'.
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
************

From bouncefilter Fri Dec 3 08:41:04 1999
Received: from hotmail.com (f157.law3.hotmail.com [209.185.241.157])
by hub.org (8.9.3/8.9.3) with SMTP id IAA21314
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 08:40:29 -0500 (EST)
(envelope-from lv68@hotmail.com)
Received: (qmail 47599 invoked by uid 0); 3 Dec 1999 13:39:52 -0000
Message-ID: <19991203133952.47598.qmail@hotmail.com>
Received: from 192.6.76.68 by www.hotmail.com with HTTP;
Fri, 03 Dec 1999 05:39:51 PST
X-Originating-IP: [192.6.76.68]
From: "vincent leycuras" <lv68@hotmail.com>
To: pgsql-general@postgreSQL.org
Subject: Some MySQL features
Date: Fri, 03 Dec 1999 12:39:51 EGT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Hi!
I'd like to know if pgsql supports the two excellent features that exist in
MySQL:
- the possibility to load the database with ASCII formatted file containing
the data we want to put;
- the index auto incrementation the prevents from having to specify the
value of the primary key each time one adds a row.

I'd also like to know if the java driver for pgsql really works under linux
as I haven't been able to make the MySQL one work and this thing is really
getting on my nerves...

Thanks!
Vincent.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

From bouncefilter Fri Dec 3 07:37:20 1999
Received: from duke.krautzer-lynn.com (duke.krautzer-lynn.com [193.83.186.5])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA75290
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 07:37:09 -0500 (EST)
(envelope-from garcia@krautzer-lynn.com)
Received: from Next (gate.krautzer-lynn.com [193.83.186.6])
by duke.krautzer-lynn.com (8.8.7/8.8.7) with SMTP id NAA28309
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 13:37:07 +0100
Received: by Next with Microsoft Mail
id <01BF3D94.027269D0@Next>; Fri, 3 Dec 1999 13:40:49 +0100
Message-ID: <01BF3D94.027269D0@Next>
From: Julio Garcia <garcia@krautzer-lynn.com>
To: "'pgsql-general@postgresql.org'" <pgsql-general@postgresql.org>
Subject: Paging through records using pgsql and ASP
Date: Fri, 3 Dec 1999 13:47:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id HAA75329

I am trying to port some ASP from MS Access to PostgreSQL and I am having problems with an ASP function the enables me to page through a collection of records viewing only a limited number of records on each page.
Specifically I am able to set the PageSize of the ADODB.RecordSet object but when I try to set the AbsolutePage of this object beyond 1 I get a very informative "unexpected error".
Does anyone knows if PostgreSQL supports this kind of functionality?

Thanks,

Julio Garcia
garcia@krautzer-lynn.com

From bouncefilter Fri Dec 3 07:55:03 1999
Received: from trends.net (clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA01313
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 07:54:24 -0500 (EST)
(envelope-from lodea@vet.com.au)
Received: from rivendell.mel.vet.com.au ([203.103.154.61])
by trends.net (8.8.8/8.8.8) with ESMTP id HAA29585
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 07:54:14 -0500 (EST)
Received: (from lodea@localhost)
by rivendell.mel.vet.com.au (8.9.3/8.9.3) id XAA04009
for pgsql-general@postgresql.org; Fri, 3 Dec 1999 23:53:34 +1100 (EST)
Date: Fri, 3 Dec 1999 23:53:34 +1100
From: "Lachlan O'Dea" <lodea@vet.com.au>
To: pgsql-general@postgresql.org
Subject: All writes make postgresql a slow database?
Message-ID: <19991203235333.A3664@vet.com.au>
Mail-Followup-To: pgsql-general@postgresql.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.1i
X-Operating-System: FreeBSD 3.3-STABLE i386

What I'm about to say may be total garbage, but I'm just telling it how
it happened.

I'm using Postges to log certain customer activities on our web site -
logins, things like that. I vacuum once a night. Now the database has
grown quite large, the main table alone is 180 Mb. It contains lots and
lots of small rows.

I've been finding recently that my postmaster processes have been eating
up more and more CPU, and I've been wondering what to do about it (the
connections to the database are pooled and kept open for long
periods). The other (perhaps strange) thing is, we hardly ever do
queries on this thing. Gathering stats is still on my to-do list.

Anyway, a few minutes ago I ran a single query. After it finished, I
noticed that the CPU usage had dropped dramatically. Like from a load
average of about 5 to about 0.8. Now I'm wondering if the query I ran
was the cause of this. Will postgres slow down if the only operations
being performed are inserts?

It may just be that activity on the site dropped off at the same time a
ran the query, but the number of clients seemed to be pretty normal.

Is there any validity to this idea?

--
Lachlan O'Dea <mailto:lodea@vet.com.au> Computer Associates Pty Ltd
Webmaster Vet - Anti-Virus Software
http://www.vet.com.au/

"It is better to light a candle than to curse the darkness."
- Carl Sagan

From bouncefilter Fri Dec 3 09:04:04 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA25629
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 09:03:09 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-28.dial.eunet.ch
[193.72.192.251])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id PAA11396;
Fri, 3 Dec 1999 15:02:35 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id PAA02136;
Fri, 3 Dec 1999 15:02:48 +0100
Sender: herbie@thinx.ch
Message-ID: <3847CD82.9B84062E@thinx.ch>
Date: Fri, 03 Dec 1999 15:02:42 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: vincent leycuras <lv68@hotmail.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Some MySQL features
References: <19991203133952.47598.qmail@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

vincent leycuras wrote:

I'd like to know if pgsql supports the two excellent features that exist in
MySQL:
- the possibility to load the database with ASCII formatted file containing
the data we want to put;

Sure. This is the copy routine. But it is also easy to load data with
programs (perl DBI/DBD)

- the index auto incrementation the prevents from having to specify the
value of the primary key each time one adds a row.

Sure. You may define a sequence by doing this:

create sequence xxx_id_seq START 1;
create table xxy
(
xxx_Id INTEGER NOT NULL
DEFAULT NEXTVAL('xxx_id_seq'),
...
);

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Herbert Liechti E-Mail: Herbert.Liechti@thinx.ch
ThinX networked business services Stahlrain 10, CH-5200 Brugg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From bouncefilter Fri Dec 3 09:18:04 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA28852
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 09:17:40 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.2/8.9.2) with SMTP id PAA21967;
Fri, 3 Dec 1999 15:16:09 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Fri, 3 Dec 1999 15:16:08 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
To: vincent leycuras <lv68@hotmail.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Some MySQL features
In-Reply-To: <19991203133952.47598.qmail@hotmail.com>
Message-ID: <Pine.BSF.3.96.991203151529.20534E-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 3 Dec 1999, vincent leycuras wrote:

Hi!
I'd like to know if pgsql supports the two excellent features that exist in
MySQL:
- the possibility to load the database with ASCII formatted file containing
the data we want to put;

yes

- the index auto incrementation the prevents from having to specify the
value of the primary key each time one adds a row.

yes

I'd also like to know if the java driver for pgsql really works under linux
as I haven't been able to make the MySQL one work and this thing is really
getting on my nerves...

yes

Thanks!

np
mazek

From bouncefilter Fri Dec 3 11:00:13 1999
Received: from gw.rpa.ryazan.su ([193.125.211.254])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA61986
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 11:00:08 -0500 (EST)
(envelope-from rpa.ryazan.su!sled.rpa.ryazan.su!vovk@gw.rpa.ryazan.su)
Received: from rpa.ryazan.su!sled.rpa.ryazan.su by gw.rpa.ryazan.su with UUCP
id TAA00444; (8.9.3/vak/1.9) Fri, 3 Dec 1999 19:00:40 +0300 (MSK)
Received: from hub.sled.rpa.ryazan.su by rpa.ryazan.su with ESMTP id PAA20653;
(8.8.7/vak/1.9) Fri, 3 Dec 1999 15:53:45 GMT
Received: (from root@localhost)
by hub.sled.rpa.ryazan.su (8.9.3/8.9.3) id RAA31369
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 17:36:05 +0300 (MSK)
Received: from vovk.sled.rpa.ryazan.su(192.168.0.1) by hub.sled.rpa.ryazan.su
via smap (V2.1) id xma031367; Fri, 3 Dec 99 17:35:37 +0300
Message-ID: <000901bf3d9a$bdcd9cd0$0100a8c0@sled.rpa.ryazan.su>
From: "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
To: <pgsql-general@postgresql.org>
Subject: upper, initcap
Date: Fri, 3 Dec 1999 17:28:56 +0300
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

I was configure postgresql with --enable-locale --with-mb=KOI8 and set
LC_COLLATE=koi8-r and LC_CTYPE=koi8-r when starting postmaster.
But, upper() and initcap() do not work.
Can any help me?

From bouncefilter Fri Dec 3 10:53:13 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA59304
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 10:52:44 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1)
id 11tv0e-00074s-00; Fri, 3 Dec 1999 15:52:36 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11tv0U-0001Dl-00; Fri, 3 Dec 1999 15:52:26 +0000
Subject: Re: [GENERAL] Urgent - unable to get postgres up
To: kimi@intercept.co.in (V Krishnaraj)
Date: Fri, 3 Dec 1999 15:52:26 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Cc: pgsql-general@postgresql.org
Reply-To: prlw1@cam.ac.uk
In-Reply-To: <199912031406.HAA06105@intercept-india.com> from "V Krishnaraj"
at Dec 3, 99 07:42:30 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11tv0U-0001Dl-00@quartz.newn.cam.ac.uk>

The error message we get at the unix prompt when starting
postmaster is:

/usr/local/bin/postmaster does not know where to find the database system
data. You must specify the directory that contains the database system
either by specifying the -D invocation option or by setting the PGDATA
environment variable.

No data directory -- can't proceed.

So, where is your data? Is it in the default /usr/local/pgsql/data ? If so,
try

/usr/local/bin/postmaster -D/usr/local/pgsql/data

Did something happen to that directory? eg., disk still there etc?

Cheers,

Patrick

From bouncefilter Fri Dec 3 11:39:14 1999
Received: from fep132.fep.ru (mail@fep132.fep.ru [195.230.89.88])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA74294
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 11:39:05 -0500 (EST)
(envelope-from phd@phd.russ.ru)
Received: from localhost [127.0.0.1] (phd)
by fep132.fep.ru with esmtp (Exim 2.05 #1 (Debian))
id 11tvjJ-0007cy-00; Fri, 3 Dec 1999 19:38:45 +0300
Date: Fri, 3 Dec 1999 16:38:44 +0000 (GMT)
From: Oleg Broytmann <phd@phd.russ.ru>
X-Sender: phd@fep132.fep.ru
Reply-To: phd2@earthling.net
To: "Vovk G. Grigoriy" <vovk@sled.rpa.ryazan.su>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] upper, initcap
In-Reply-To: <000901bf3d9a$bdcd9cd0$0100a8c0@sled.rpa.ryazan.su>
Message-ID: <Pine.LNX.4.21.9912031637010.29302-100000@fep132.fep.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 3 Dec 1999, Vovk G. Grigoriy wrote:

I was configure postgresql with --enable-locale --with-mb=KOI8 and set
LC_COLLATE=koi8-r and LC_CTYPE=koi8-r when starting postmaster.
But, upper() and initcap() do not work.
Can any help me?

All things related to locale and charset converting (at least, all
things that I was aware of) are about sorting (ORDER BY). I have never
looked into other parts of locale-related code.

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.

From bouncefilter Fri Dec 3 12:29:18 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA04923
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 12:28:32 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11twVT-000LEEC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Fri, 3 Dec 1999 11:28:31 -0600 (CST)
Date: Fri, 3 Dec 1999 11:28:31 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Some MySQL features
Message-ID: <19991203112831.A11929@rice.edu>
References: <19991203133952.47598.qmail@hotmail.com>
<3847CD82.9B84062E@thinx.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <3847CD82.9B84062E@thinx.ch>;
from Herbert.Liechti@thinx.ch on Fri, Dec 03, 1999 at 03:02:42PM
+0100

On Fri, Dec 03, 1999 at 03:02:42PM +0100, Herbert Liechti wrote:

vincent leycuras wrote:

I'd like to know if pgsql supports the two excellent features that exist in
MySQL:
- the possibility to load the database with ASCII formatted file containing
the data we want to put;

Sure. This is the copy routine. But it is also easy to load data with
programs (perl DBI/DBD)

COPY has its own little quirks as regards representing NULLs and
such. Check the docs. Works fine for me from the unix command line.
Be careful about delimiters and quoting: if a bulk load fails, the actual
error usually goes flying past, and the ultimate killing error says
something about the command buffer overflowing, or command to long, or
so. Usually a result of quoting getting off by one. Hmm, I just realized
that the work to allow unlimited command buffers is going to change this
failure mode.

- the index auto incrementation the prevents from having to specify the
value of the primary key each time one adds a row.

Sure. You may define a sequence by doing this:

create sequence xxx_id_seq START 1;
create table xxy
(
xxx_Id INTEGER NOT NULL
DEFAULT NEXTVAL('xxx_id_seq'),
...
);

Or even easier:

test=> create table xxy (xxx_id serial);
NOTICE:  CREATE TABLE will create implicit sequence 'xxy_xxx_id_seq' for SERIAL column 'xxy.xxx_id'
NOTICE:  CREATE TABLE/UNIQUE will create implicit index 'xxy_xxx_id_key' for table 'xxy'
CREATE
test=> \d xxy  
Table    = xxy
+----------------------------------+----------------------------------+-------+
|              Field               |              Type                | Length|
+----------------------------------+----------------------------------+-------+
| xxx_id                           | int4 not null default nextval('" |     4 |
+----------------------------------+----------------------------------+-------+
Index:    xxy_xxx_id_key

test=>

As you can see, 'serial' is implemented exaclty that way: it creates a
sequence, and sets the default for the field to nextval, and makes it not null
and unique (with the index).

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

From bouncefilter Fri Dec 3 13:41:18 1999
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA60672
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 13:41:07 -0500 (EST)
(envelope-from keithmur@mindspring.com)
Received: from mindspring.com ([209.138.136.187])
by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id NAA25747
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 13:41:06 -0500 (EST)
Message-ID: <38480F16.71802604@mindspring.com>
Date: Fri, 03 Dec 1999 12:42:30 -0600
From: "Keith G. Murphy" <keithmur@mindspring.com>
Reply-To: keithmur@mindspring.com
Organization: A small shoebox in the middle of the road
X-Mailer: Mozilla 4.6 [en] (Win95; U)
X-Accept-Language: en,en-US,en-GB
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Some MySQL features
References: <19991203133952.47598.qmail@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

vincent leycuras wrote:

Hi!
I'd like to know if pgsql supports the two excellent features that exist in
MySQL:
- the possibility to load the database with ASCII formatted file containing
the data we want to put;
- the index auto incrementation the prevents from having to specify the
value of the primary key each time one adds a row.

This is a question that could be an answer. What do y'all think about
using the OID to get the same functionality (unless he really needs a
sequence of nice small numbers)?

From bouncefilter Fri Dec 3 14:09:19 1999
Received: from gtv.ca (h-207-228-97-106.gen.cadvision.com [207.228.97.106])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA66560
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 14:08:48 -0500 (EST)
(envelope-from aaron@genisys.ca)
Received: from stilborne (24.67.89.147.ab.wave.home.com [24.67.89.147])
by gtv.ca (8.9.3/8.8.7) with SMTP id NAA32469;
Fri, 3 Dec 1999 13:18:36 -0700
From: "Aaron J. Seigo" <aaron@gtv.ca>
To: keithmur@mindspring.com
Subject: Re: [GENERAL] Some MySQL features
Date: Fri, 3 Dec 1999 12:07:27 -0700
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <19991203133952.47598.qmail@hotmail.com>
<38480F16.71802604@mindspring.com>
In-Reply-To: <38480F16.71802604@mindspring.com>
Cc: pgsql-general@postgreSQL.org
MIME-Version: 1.0
Message-Id: <99120312081305.23724@stilborne>
Content-Transfer-Encoding: 8bit

hi..

This is a question that could be an answer. What do y'all think about
using the OID to get the same functionality (unless he really needs a
sequence of nice small numbers)?

OIDs don't survive dump/reloads and sequences already provide this
functionality, surviving dump/reloads

--
Aaron J. Seigo
Sys Admin

From bouncefilter Fri Dec 3 15:50:20 1999
Received: from cuaima.ica.luz.ve (root@cuaima.ica.luz.ve [150.185.194.30])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA93541
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 15:50:08 -0500 (EST)
(envelope-from vegeta@cuaima.ica.luz.ve)
Received: from localhost (vegeta@localhost)
by cuaima.ica.luz.ve (8.8.8/8.8.8) with ESMTP id PAA11548
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 15:42:50 -0400
Date: Fri, 3 Dec 1999 15:42:50 -0400 (VET)
From: Vegeta <vegeta@cuaima.ica.luz.ve>
To: pgsql-general@postgresql.org
Subject: PostgreSQL 6.5.3 on SuSE 6.1
Message-ID: <Pine.LNX.4.05.9912031536280.11532-100000@cuaima.ica.luz.ve>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi list members:
I am currently using PostgreSQL 6.4.2 on SuSE 6.1. This version came with
the SuSE disks. Recently, I downloaded and compiled the source from the
pgsql ftp site, but postgres does not run and says that a file called
libreadline.so is needed to run. This file is not on my computer. Is
there a way to make postgres run without this file on this distribution?.
Are there RPMs for SuSE 6.1?
Any help is appreciated.

Thanks,
Vegeta

From bouncefilter Fri Dec 3 14:28:19 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA79746
for <pgsql-general@postgreSQL.org>; Fri, 3 Dec 1999 14:27:20 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id OAA14996;
Fri, 3 Dec 1999 14:22:26 -0600
Date: Fri, 3 Dec 1999 14:22:26 -0600 (CST)
From: <kaiq@realtyideas.com>
To: "Aaron J. Seigo" <aaron@gtv.ca>
cc: keithmur@mindspring.com, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Some MySQL features
In-Reply-To: <99120312081305.23724@stilborne>
Message-ID: <Pine.LNX.4.10.9912031420310.14529-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

and, generally, those low-level non-sql86/92 things should be treated with
caution.

On Fri, 3 Dec 1999, Aaron J. Seigo wrote:

hi..

This is a question that could be an answer. What do y'all think about
using the OID to get the same functionality (unless he really needs a
sequence of nice small numbers)?

OIDs don't survive dump/reloads and sequences already provide this
functionality, surviving dump/reloads

--
Aaron J. Seigo
Sys Admin

************

From bouncefilter Fri Dec 3 17:30:21 1999
Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA09698
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 17:29:35 -0500 (EST)
(envelope-from jesse@revbox.com)
Received: from revbox.com (revbox.ne.mediaone.net [24.147.17.161])
by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id RAA22975
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 17:29:35 -0500 (EST)
Message-ID: <3848426D.45A0445@revbox.com>
Date: Fri, 03 Dec 1999 17:21:33 -0500
From: Jesse Kipp <jesse@revbox.com>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] All writes make postgresql a slow database?
References: <19991203235333.A3664@vet.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm using Postges to log certain customer activities on our web site -
logins, things like that. I vacuum once a night. Now the database has
grown quite large, the main table alone is 180 Mb. It contains lots and
lots of small rows.

That is a very small database. :)

Anyway, a few minutes ago I ran a single query. After it finished, I
noticed that the CPU usage had dropped dramatically. Like from a load
average of about 5 to about 0.8. Now I'm wondering if the query I ran
was the cause of this. Will postgres slow down if the only operations
being performed are inserts?

What indexes do you have on the table? Having lots of indexes could slow
down inserts, but speed up queries. If you don't have any indexes, a
query against a 180 meg table could take a while, particularly if you
have less then 180 megs of ram.

jesse

From bouncefilter Fri Dec 3 17:40:21 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA10955
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 17:39:58 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.3.127]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Fri, 3 Dec 1999 16:32:00 -0600
Sender: ed
Message-ID: <384846E1.B503C120@austin.rr.com>
Date: Fri, 03 Dec 1999 16:40:33 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: keithmur@mindspring.com
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Some MySQL features
References: <19991203133952.47598.qmail@hotmail.com>
<38480F16.71802604@mindspring.com> <99120312081305.23724@stilborne>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Aaron J. Seigo" wrote:

This is a question that could be an answer. What do y'all think about
using the OID to get the same functionality (unless he really needs a
sequence of nice small numbers)?

OIDs don't survive dump/reloads and sequences already provide this
functionality, surviving dump/reloads

The postgres SERIAL type, which is a sequence, is fairly well-suited to
primary key usage. See PG documentation for details...

Cheers.
Ed Loehr

From bouncefilter Fri Dec 3 09:07:04 1999
Received: from intercept-india.com (intercep@intercept-india.com
[192.41.37.131]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA26339
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 09:06:16 -0500 (EST)
(envelope-from kimi@intercept.co.in)
Received: from vsnl.net.in ([202.9.149.121]) by intercept-india.com (8.8.5) id
HAA06105; Fri, 3 Dec 1999 07:06:00 -0700 (MST)
Message-Id: <199912031406.HAA06105@intercept-india.com>
X-Authentication-Warning: intercept-india.com: Host [202.9.149.121] claimed to
be vsnl.net.in
From: "V Krishnaraj" <kimi@intercept.co.in>
To: pgsql-general@postgresql.org
Date: Fri, 3 Dec 1999 19:42:30 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Urgent - unable to get postgres up
Priority: normal
X-mailer: Pegasus Mail for Win32 (v3.01b)

Dear Community,

Postgres has been suddenly shut off and we are unable to log on:

The error message we get at the unix prompt when starting
postmaster is:

/usr/local/bin/postmaster does not know where to find the da
tabase system data. You must specify the directory that contains
the database s
ystem either by specifying the -D invocation option or by setting
the PGDATA env
ironment variable.

No data directory -- can't proceed.

Please help. A mission critical application is held up.

Thanks in advance.

Kimi

From bouncefilter Fri Dec 3 21:19:23 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA37081
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 21:18:58 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61905 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sG5c/16419>; Sat, 4 Dec 1999 03:18:41 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11u4qz-0000yf-00; Sat, 04 Dec 1999 03:23:17 +0100
Date: Sat, 4 Dec 1999 03:23:17 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: jose soares <jose@sferacarta.com>, Ed Loehr <ELOEHR@austin.rr.com>,
kaiq@realtyideas.com, "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dale Anderson <danderso@crystalsugar.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Date & Time
In-Reply-To: <199912011950.OAA04319@candle.pha.pa.us>
Message-ID: <Pine.LNX.4.20.9912021931480.384-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-01, Bruce Momjian mentioned:

I am changing my book to use CURRENT_TIMESTAMP rather than now().

I recall Thomas muttering some very promising things about the date/time
revolution, including conformance to SQL and ISO formats. Perhaps this
could go along with it. At least move the standard identifiers to more
prominent locations in the docs (than the non-standard ones). Currently,
those are very confusing because there are about three different ways to
go and it pretty much says "use whatever".

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Fri Dec 3 21:20:23 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA37185
for <pgsql-general@postgresql.org>; Fri, 3 Dec 1999 21:19:38 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:62262 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sG5ch36900>; Sat, 4 Dec 1999 03:19:25 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11u4rj-00011D-00; Sat, 04 Dec 1999 03:24:03 +0100
Date: Sat, 4 Dec 1999 03:24:03 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: ^chewie <chewie@wookimus.net>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres libpq library
In-Reply-To: <Pine.LNX.4.10.9912020808110.25390-100000@guinness.urw.org>
Message-ID: <Pine.LNX.4.20.9912021942590.384-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-02, ^chewie mentioned:

server. I was wondering if the library is instead thread safe (i.e.:
if it can be safely called from multi-threaded applications).

That's a definite no.

You know. I, for one, have a little bit of free time I could donate to
contributing to the Postgresql project. I know C and would not mind
learning how to implement POSIX threading. Like any project, it needs
to start somewhere with someone. I suppose I should join the [HACKERS]
list, then, huh? ;-)

Although to my knowledge, there haven't been a lot of complaints regarding
the thread-safeness of libpq, you are sure welcome to try. Note that this
would (probably) not involve any thread programming though.

The main difficulty would seem to center around the fact that all network
transmission is done as strings and you need a bunch of different buffers
to convert those back and forth and a lot of care needs to be exercised
there. I'm personally not sure if it's worth it or even possible using the
current protocols.

If you do want to contribute, however, joining that hackers list and
reading the TODO list would be excellent starts. There is probably a lot
of stuff in libpq that could be taken care of anyway.

-Peter

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Sat Dec 4 15:59:36 1999
Received: from s8-37-26.student.washington.edu
(S8-37-26.student.washington.edu [128.208.37.26])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA84796
for <pgsql-general@postgresql.org>; Sat, 4 Dec 1999 15:58:44 -0500 (EST)
(envelope-from jcwells@u.washington.edu)
Received: from localhost (jcw@localhost)
by s8-37-26.student.washington.edu (8.9.3/8.9.3) with ESMTP id VAA63820
for <pgsql-general@postgresql.org>; Sat, 4 Dec 1999 21:02:22 GMT
(envelope-from jcwells@u.washington.edu)
X-Authentication-Warning: s8-37-26.student.washington.edu: jcw owned process
doing -bs
Date: Sat, 4 Dec 1999 21:02:22 +0000 (GMT)
From: "Jason C. Wells" <jcwells@u.washington.edu>
X-Sender: jcw@s8-37-26.student.washington.edu
Reply-To: "Jason C. Wells" <jcwells@u.washington.edu>
To: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Buggered Sequence
Message-ID:
<Pine.BSF.4.10.9912042058320.63812-100000@s8-37-26.student.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

After I screwed up a pgdump and restore I finally got my data back into
the database. I have one little thing to fix. My sequence should be at
last_value='44'.

I tried to use update set last_value='44' but I wasn't allowed to change
the sequence as jcwells or as the pgsql superuser. How can I fix my
sequence?

Thank You, | http://students.washington.edu/jcwells/
Jason Wells

From bouncefilter Sat Dec 4 16:18:36 1999
Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA87174
for <pgsql-general@postgresql.org>; Sat, 4 Dec 1999 16:17:52 -0500 (EST)
(envelope-from jesse@revbox.com)
Received: from revbox.com (revbox.ne.mediaone.net [24.147.17.161])
by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id QAA09541;
Sat, 4 Dec 1999 16:17:39 -0500 (EST)
Message-ID: <38498310.7AE20E1C@revbox.com>
Date: Sat, 04 Dec 1999 16:09:36 -0500
From: Jesse Kipp <jesse@revbox.com>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Jason C. Wells" <jcwells@u.washington.edu>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Buggered Sequence
References:
<Pine.BSF.4.10.9912042058320.63812-100000@s8-37-26.student.washington.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Can you do:

drop sequence people_id_seq
create sequence people_id_seq start 44

jesse kipp

"Jason C. Wells" wrote:

sequence_name|last_value|increment_by| max_value|min_value|cache_value|is_cycled|is_called
-------------+----------+------------+----------+---------+-----------+---------+---------
people_id_seq| 4| 1|2147483647| 1| 1|f |t
(1 row)

After I screwed up a pgdump and restore I finally got my data back into
the database. I have one little thing to fix. My sequence should be at
last_value='44'.

I tried to use update set last_value='44' but I wasn't allowed to change
the sequence as jcwells or as the pgsql superuser. How can I fix my
sequence?

Thank You, | http://students.washington.edu/jcwells/
Jason Wells

************

From bouncefilter Sat Dec 4 17:09:37 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA92718
for <pgsql-general@postgresql.org>; Sat, 4 Dec 1999 17:08:49 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11uNMG-000LECC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Sat, 4 Dec 1999 16:08:48 -0600 (CST)
Date: Sat, 4 Dec 1999 16:08:48 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: pgsql-general@postgresql.org
Cc: "Jason C. Wells" <jcwells@u.washington.edu>
Subject: Re: [GENERAL] Buggered Sequence
Message-ID: <19991204160848.B19842@rice.edu>
References:
<Pine.BSF.4.10.9912042058320.63812-100000@s8-37-26.student.washington.edu>
<38498310.7AE20E1C@revbox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <38498310.7AE20E1C@revbox.com>;
from jesse@revbox.com on Sat, Dec 04, 1999 at 04:09:36PM -0500

Jason -
Jesse's sugestion should work, but there's a setval() function for
this exact use:

SELECT setval('people_id_seq',44);

I usually use it like this:

SELECT setval('"Experiments_ExptID_seq"',max("ExptID")) from "Experiments";

That automatically sets the sequence value to the current max in the table.

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

From bouncefilter Sat Dec 4 21:32:40 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA19787
for <pgsql-general@postgresql.org>; Sat, 4 Dec 1999 21:32:20 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61554 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sGQuW26631>; Sun, 5 Dec 1999 03:32:02 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11uRXq-00008c-00; Sun, 05 Dec 1999 03:37:02 +0100
Date: Sun, 5 Dec 1999 03:37:02 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Vegeta <vegeta@cuaima.ica.luz.ve>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] PostgreSQL 6.5.3 on SuSE 6.1
In-Reply-To: <Pine.LNX.4.05.9912031536280.11532-100000@cuaima.ica.luz.ve>
Message-ID: <Pine.LNX.4.20.9912050329590.436-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

I don't have SuSE but I'll give it a shot.

First of all, libreadline is only needed by the psql frontend, the
postmaster should still start up. If you don't have libreadline installed
at all then the compilation should have omitted it, so that seems
unlikely. Chances are that running /sbin/ldconfig will solve this problem.

Regarding the second question, there are no RPMs for SuSE, but I
understand that the RPM maintainers are working on RPMs for a variety of
distributions.

-Peter

On 1999-12-03, Vegeta mentioned:

Hi list members:
I am currently using PostgreSQL 6.4.2 on SuSE 6.1. This version came with
the SuSE disks. Recently, I downloaded and compiled the source from the
pgsql ftp site, but postgres does not run and says that a file called
libreadline.so is needed to run. This file is not on my computer. Is
there a way to make postgres run without this file on this distribution?.
Are there RPMs for SuSE 6.1?
Any help is appreciated.

Thanks,
Vegeta

************

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Sun Dec 5 06:25:46 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA79105
for <pgsql-general@postgreSQL.org>; Sun, 5 Dec 1999 06:25:41 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-9.dial.eunet.ch
[193.72.192.232])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id MAA17379;
Sun, 5 Dec 1999 12:25:10 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id MAA00367;
Sun, 5 Dec 1999 12:06:41 +0100
Sender: herbie@thinx.ch
Message-ID: <384A4741.F7F286B8@thinx.ch>
Date: Sun, 05 Dec 1999 12:06:41 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Vegeta <vegeta@cuaima.ica.luz.ve>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] PostgreSQL 6.5.3 on SuSE 6.1
References: <Pine.LNX.4.05.9912031536280.11532-100000@cuaima.ica.luz.ve>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi list members:
I am currently using PostgreSQL 6.4.2 on SuSE 6.1. This version came with
the SuSE disks. Recently, I downloaded and compiled the source from the
pgsql ftp site, but postgres does not run and says that a file called
libreadline.so is needed to run. This file is not on my computer. Is
there a way to make postgres run without this file on this distribution?.
Are there RPMs for SuSE 6.1?
Any help is appreciated.

I setted up postgres 6.5.2 on Suse 6.1 without problems. Here my
configuration options:

./configure --prefix=/home/db/postgres/ --with-template=linux_i386 \
--enable-locale

After compiling postgres you need to edit /etc/ld.so.conf. With the
above configuration I added the following line to ld.so.conf:

/home/db/postgres/lib

Run /sbin/ldconfig after editing ld.so.conf. Of course you have to
set up you environment correctly as described in the INSTALL
doucment of postgres:

PATH=$PATH:/home/db/postgres/bin
MANPATH=$MANPATH:/home/db/postgres/man
PGLIB=/home/db/postgres/lib
PGDATA=/home/db/postgres/data
export PATH MANPATH PGLIB PGDATA

Greetings Herbie

From bouncefilter Sun Dec 5 09:07:48 1999
Received: from dcave.digsys.bg (root@dcave.digsys.bg [192.92.129.5])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA99802
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 09:07:21 -0500 (EST)
(envelope-from daniel@dcave.digsys.bg)
Received: from dcave.digsys.bg (daniel@localhost.digsys.bg [127.0.0.1])
by dcave.digsys.bg (8.9.0/8.9.0) with ESMTP id QAA03457
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 16:06:27 +0200 (EET)
Message-Id: <199912051406.QAA03457@dcave.digsys.bg>
X-Mailer: exmh version 2.0.2 2/24/98
From: Daniel Kalchev <daniel@digsys.bg>
To: pgsql-general@hub.org
Subject: Re: [GENERAL] memory
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 05 Dec 1999 16:06:27 +0200
Sender: daniel@digsys.bg

Bruce Momjian <pgman@candle.pha.pa.us> wrote:

owner-pgsql-general-digest@hub.org said:

1) Can someone explain how postgreSQL uses memory so that I can
understand
what I should be doing here.
BTW, I am running postgres with -B 884. Can someone also explain how
postgres uses shared mem so that I can have a clue what would be a
reasonable setting.

2) Can any BSDI folk give me any tuning tips. I am especially
interested to
hear from those who claim "some might tell you that we run equally
well on
FreeBSD" or "BSD is the One True Code", of course all help is
gratefully
received.

I have run BSDI for years and never saw this problem. Not sure on a
cause, though.

Bruce,

I too run BSD/OS for years and on all BSD/OS versions since 2.1 and Postgres
since 6.0 (earlier postrges releases didn't have much load here) observe the
same problem:

the postgres process never can allocate more than ~74MB of memory! It would
die with (printed on the controlling terminal!?) message:

sbrk: grow failed, return = 12

The postgres log would show

FATAL 1: Memory exhausted in AllocSetAlloc()

I have actually complained seveal time, and saw recently that the alloc
routines have been rewritten, but with the same result! I now think this may
be something BSD/OS related - I never ever see a postgres process allocate
more than 74 MB memory! :-)

The resource limits when postrges is started are:

coredumpsize unlimited
cputime unlimited
datasize 262144 kbytes
filesize unlimited
maxproc 4116
memorylocked 256164 kbytes
memoryuse 256160 kbytes
openfiles 13196
stacksize 262144 kbytes

This is one of the most mysterious things I ever saw on using BSD/OS and
PostgreSQL.... and of course - shared memory and semaphores! :-)

I have my BSD/OS kernel (3.1) configured with these options

options "DFLDSIZ=$64*1024*1024$"
options "MAXDSIZ=$256*1024*1024$"
options "CHILD_MAX=256"
options "OPEN_MAX=256"
options "KMAPENTRIES=4000" # Prevents kmem malloc errors !
options "KMEMSIZE=$32*1024*1024$"
# shared memory setup for Postgres
options "SHMMAXPGS=32768"
options "SHMMNI=400"
options "SHMSEG=204"
# More semaphores for Postgres
options "SEMMNS=600"

sometimes, it logs messages such as

IpcMemoryCreate: shmget failed (Cannot allocate memory) key=5432401,
size=2661376, permission=600

Postgres is started with

postmaster -D/usr/local/pgsql/data -B 256 -i -o "-e -S 8192" >>
/usr/local/pgsql/errlog 2>&1 &

Weird...

Daniel

From bouncefilter Sun Dec 5 10:13:49 1999
Received: from www.geocrawler.com (sourceforge.net [209.81.8.17])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA05923
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 10:13:19 -0500 (EST)
(envelope-from nobody@www.geocrawler.com)
Received: (from nobody@localhost)
by www.geocrawler.com (8.9.3/8.9.3) id HAA13993;
Sun, 5 Dec 1999 07:13:20 -0800
Date: Sun, 5 Dec 1999 07:13:20 -0800
Message-Id: <199912051513.HAA13993@www.geocrawler.com>
To: pgsql-general@hub.org
Subject: PostgreSQL and Java
From: "USSL" <archiver@db.geocrawler.com>
Reply-To: "USSL" <ussl@usa.net>

This message was sent from Geocrawler.com by "USSL" <ussl@usa.net>
Be sure to reply to that address.

Subject: Request for help on PostgreSQL and
JBuilder

Hi members,

Is there someone who can help me in establishing
connectivity between PostgreSQL and JBuilder
using JDBC driver ?

My environment is as follows:

Server: RedHat Linux 6.1

ORDBMS: PostgreSQL

Client OS: Windows 95

IDE: JBuilder

Connectivity: JDBC

Thanks in advance. A quick response will be
highly appreciated.

jayasimha makineni

Geocrawler.com - The Knowledge Archive

From bouncefilter Sun Dec 5 11:54:50 1999
Received: from moe.cadabradesign.com (hat1.cadabradesign.com [216.129.4.2])
by hub.org (8.9.3/8.9.3) with SMTP id LAA32120
for <pgsql-general@postgreSQL.org>; Sun, 5 Dec 1999 11:54:48 -0500 (EST)
(envelope-from dons@cadabradesign.com)
Received: from willie.cadabra.ca by moe.cadabradesign.com (5.x/SMI-SVR4)
id AA11620; Sun, 5 Dec 1999 11:55:50 -0500
Received: from cadabradesign.com (localhost) by willie.cadabra.ca
(4.1/SMI-4.1)
id AA12760; Sun, 5 Dec 99 11:55:49 EST
Sender: dons@cadabradesign.com
Message-Id: <384A9914.3FF57B04@cadabradesign.com>
Date: Sun, 05 Dec 1999 11:55:49 -0500
From: Don Shesnicky <dons@cadabradesign.com>
X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 4.1.4 sun4m)
Mime-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: free form text database?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'd like to build something where I can store a searchable database of
free form text.
Right now I'd like to input usenet articles in a similar fashion to
Dejanews but only with
the groups I am interested in.

There use to be a shareware program called WAIS that would have been
similar to
what I was thinking of but it appears to have died off. Could Postgresql
be adapted
to this?

I've done something similar with a Perl cgi script but it's dead slow
and not very
expandable. What I'm looking for is a database of all words pointing
back to the
articles that contain them.

Don

From bouncefilter Sun Dec 5 13:38:51 1999
Received: from ss452.tel.hr (ss452.tel.hr [205.219.255.21])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA49931
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 13:38:50 -0500 (EST)
(envelope-from izvori@iname.com)
Received: from iname.com (IDENT:slavica@ad6-m1.tel.hr [195.29.229.1])
by ss452.tel.hr (0.0.0/0.0.0) with ESMTP id TAA18001
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 19:38:46 +0100 (MET)
Sender: slavica@ss452.tel.hr
Message-ID: <384AB0C5.93F97204@iname.com>
Date: Sun, 05 Dec 1999 19:36:53 +0100
From: Slavica Stefic <izvori@iname.com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.13-7mdk i686)
MIME-Version: 1.0
To: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: null and =
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

is null = null true or also null ?

more precisely I have this kind of situation in a mission critical
project and I'm,sadly, not an expert in SQL.
But until now I used null values with a specific meaning in my database,
and I didn't knew that
I would come in this situation:

=>create table dummy (a int, b int);
insert into dummy values (1);
insert into dummy values (2);
insert into dummy values (3);

--- this work as expected
=>select * from dummy where a = 1 and a in (select a from dummy where a
!= 3 );
a|b
-+-
1|
(1 row)

--- this one also
=> select a from dummy where a = 1 intersect select a from dummy where a
!= 3 ;
a
-
1
(1 row)

---- !!!!!!!!
=> select a,b from dummy where a = 1 intersect select a,b from dummy
where a != 3 ;
a|b
-+-
(0 rows)

it appears that two null records are not equal if they are both null.
I tried also
select b = b from dummy where b is null;
and I get three empty rows.

First question: is this correct? is this SQL conformant?
2: if I change the sources for the operator to compare nulls as
they where values
will it have too many side effects?

one possibility I have is to create a new type with a custum operator
"=" for each field type I use
in this compond filter query but I'd like to know if there are other
solutions before I start to do
this long coding.

I would appreciate very much and kind of help.
Thanks in advance

Marko Mikulicic

From bouncefilter Sun Dec 5 14:00:51 1999
Received: from outthere.thinx.ch (outthere.thinx.ch [194.158.233.34])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA53033
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 14:00:22 -0500 (EST)
(envelope-from Herbert.Liechti@thinx.ch)
Received: from venus.net.thinx.ch (root@dyna-ol-16.dial.eunet.ch
[193.72.192.239])
by outthere.thinx.ch (8.9.2/8.9.2) with ESMTP id TAA18467
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 19:59:51 +0100 (CET)
Received: from thinx.ch (herbie@tobi.net.thinx.ch [192.168.0.9])
by venus.net.thinx.ch (8.8.8/8.8.8) with ESMTP id UAA01144
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 20:00:00 +0100
Sender: herbie@thinx.ch
Message-ID: <384AB628.FBC93E1D@thinx.ch>
Date: Sun, 05 Dec 1999 19:59:52 +0100
From: Herbert Liechti <Herbert.Liechti@thinx.ch>
Organization: ThinX networked business services
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@hub.org
Subject: Re: [GENERAL] null and =
References: <384AB0C5.93F97204@iname.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Slavica Stefic wrote:

is null = null true or also null?

A null value represents either the absence of data or
an unknown value. A null value is not
the same as a zero or a blank.

Thus two tuples with null values are never the same and can not
be joined.

it appears that two null records are not equal if they are both null.
First question: is this correct? is this SQL conformant?

yes

2: if I change the sources for the operator to compare nulls as
they where values
will it have too many side effects?

Don't do that. You will get a desaster ;-)

Herbie

From bouncefilter Sun Dec 5 14:35:51 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA56753
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 14:34:54 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-192.ocis.net [209.52.174.143])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id LAA30462
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 11:34:52 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <384ABA80.7C23BB04@mail.ocis.net>
Date: Sun, 05 Dec 1999 11:18:24 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: procmail w/ PG.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

I seem to have found a good solution for getting email into a Pg db,
only problem is I'm not good enough with procmail scripts to do it.

I'l like procmail to filter out the To, From, Date, Subject, Body and
complete header of the email. Then either stick it in a DB, or pass
that info to a Perl script to stick in in the DB.

Anyone know of such a script? Or an example I can work with?

Thanks
Jason

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

Debian!Linux!

From bouncefilter Sun Dec 5 14:28:52 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA55922
for <pgsql-ports@postgreSQL.org>; Sun, 5 Dec 1999 14:28:47 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
OAA19470;
Sun, 5 Dec 1999 14:28:19 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912051928.OAA19470@candle.pha.pa.us>
Subject: Re: [GENERAL] memory
In-Reply-To: <199912051406.QAA03457@dcave.digsys.bg> from Daniel Kalchev at
"Dec 5, 1999 04:06:27 pm"
To: Daniel Kalchev <daniel@digsys.bg>
Date: Sun, 5 Dec 1999 14:28:19 -0500 (EST)
CC: PostgreSQL-ports <pgsql-ports@postgreSQL.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have run BSDI for years and never saw this problem. Not sure on a
cause, though.

Bruce,

I too run BSD/OS for years and on all BSD/OS versions since 2.1 and Postgres
since 6.0 (earlier postrges releases didn't have much load here) observe the
same problem:

[Redirected to ports list].

OK, let me suggest something. Just write a program and see how much
memory you can malloc(). THe sbrk call is for heap memory, so see how
many 1mb chunks you can malloc before it fails.

The error sbrk() is not related to shared memory or semaphores. THe
6.5.* code gets all shared memory and semaphores on startup, so if it
starts, it has done all that already.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Sun Dec 5 15:28:52 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA62682
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 15:28:11 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.3.127]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Sun, 5 Dec 1999 14:27:41 -0600
Sender: ed
Message-ID: <384ACACC.BFA8223@austin.rr.com>
Date: Sun, 05 Dec 1999 14:27:56 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Jason C. Leach" <jcl@mail.ocis.net>
CC: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] procmail w/ PG.
References: <384ABA80.7C23BB04@mail.ocis.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Jason C. Leach" wrote:

I'l like procmail to filter out the To, From, Date, Subject, Body and
complete header of the email. Then either stick it in a DB, or pass
that info to a Perl script to stick in in the DB.

Anyone know of such a script? Or an example I can work with?

Caveat emptor, as I haven't done it yet, but there are a few procmail
examples of how to filter and pass email to other programs, perl
included, at

http://www.tamucc.edu/~compserv/lman/other/procexamples/index.html

The relevant examples look something like this one, which sends all mail
with 'Digest' in the subject to a mail reformatting program called
formail (see man formail):

:0
* ^Subject:.*Digest
|formail +1 -d -s procmail

This sounds like a task well-suited to perl regular expressions with
DBI/DBD::Pg. I found it quite worthwhile when setting up procmail to
spend some time carefully reviewing the various procmail filter options
(on the man page) that follow the colon. They allow you to chain
filters together and control the flow and exit point of mail through
your filter chains.

Cheers.
Ed Loehr

From bouncefilter Sun Dec 5 17:00:53 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA79080
for <pgsql-general@postgresql.org>; Sun, 5 Dec 1999 17:00:29 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id QAA04864;
Sun, 5 Dec 1999 16:56:45 -0500
Message-ID: <384AE02E.F5FE985B@mascari.com>
Date: Sun, 05 Dec 1999 16:59:11 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Slavica Stefic <izvori@iname.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] null and =
References: <384AB0C5.93F97204@iname.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Slavica Stefic wrote:

Hello,

is null = null true or also null ?

NULL = NULL is also NULL (or more explicity, UNKNOWN, implemented as NULL).
Since NULL means "unknown/not applicable" we don't know whether two
"unknowns" are, in fact, equal, and that is what the standard says - at
least according to Joe Celko...

more precisely I have this kind of situation in a mission critical
project and I'm,sadly, not an expert in SQL.
But until now I used null values with a specific meaning in my database,
and I didn't knew that
I would come in this situation:

=>create table dummy (a int, b int);
insert into dummy values (1);
insert into dummy values (2);
insert into dummy values (3);
--- this work as expected
=>select * from dummy where a = 1 and a in (select a from dummy where a
!= 3 );
a|b
-+-
1|
(1 row)
--- this one also
=> select a from dummy where a = 1 intersect select a from dummy where a
!= 3 ;
a
-
1
(1 row)
---- !!!!!!!!
=> select a,b from dummy where a = 1 intersect select a,b from dummy
where a != 3 ;
a|b
-+-
(0 rows)

I would avoid using the INTERSECT/EXCEPT code since the query rewriter
rewrites these to IN clauses which cannot use indexes. As soon as the tables
grow beyond more than a couple hundred rows, the statment becomes unusable.
Instead, I would use a correlated subquery with an EXISTS/NOT EXISTS test
against the criteria for which you are searching:

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a)
....

then, if you need a comparison of the entire row in the correlated subquery,
you could use a clause such as

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a AND
t1.b IS NULL and t2.b IS NULL);

Hope that helps,

Mike

From bouncefilter Sun Dec 5 18:06:54 1999
Received: from ss452.tel.hr (ss452.tel.hr [205.219.255.21])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA89165
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 18:06:10 -0500 (EST)
(envelope-from izvori@iname.com)
Received: from iname.com (IDENT:slavica@ad10-m161.tel.hr [195.29.233.161])
by ss452.tel.hr (0.0.0/0.0.0) with ESMTP id AAA08502;
Mon, 6 Dec 1999 00:05:46 +0100 (MET)
Sender: slavica@ss452.tel.hr
Message-ID: <384AEF59.39536D69@iname.com>
Date: Mon, 06 Dec 1999 00:03:53 +0100
From: Slavica Stefic <izvori@iname.com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.13-7mdk i686)
MIME-Version: 1.0
To: Mike Mascari <mascarm@mascari.com>
CC: "pgsql-general@hub.org" <pgsql-general@hub.org>
Subject: Re: [GENERAL] null and =
References: <384AB0C5.93F97204@iname.com> <384AE02E.F5FE985B@mascari.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike Mascari wrote:

I would avoid using the INTERSECT/EXCEPT code since the query rewriter
rewrites these to IN clauses which cannot use indexes. As soon as the tables
grow beyond more than a couple hundred rows, the statment becomes unusable.
Instead, I would use a correlated subquery with an EXISTS/NOT EXISTS test
against the criteria for which you are searching:

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a)
....

then, if you need a comparison of the entire row in the correlated subquery,
you could use a clause such as

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a AND
t1.b IS NULL and t2.b IS NULL);

Hope that helps,

Mike

Yes, thanks.
But there is still a problem. I'm generating queries from user selection and
linking them in a serie.
Using intersect this was very simple (yes, it was slow,but flexible). Using the
form you proposed queries
has to be nested and in every level the table should have an unique name and a
t1.a = t2.a .. tn-1.a = tn.a
has to be generated, which is not a big problem but I have really too much of
this "query building blocks"
and rewrite them to coform the new model will be painful and buggy (many
queries are too long to fit in
a row, and what you don't see well you don't write well :-) ). I hoped that
there was a "plugin" solution
but Murphy was right :-)

Another question: how does the rewriter rewrite the intersect/except query if
it has many fields?
as far as I know the IN clause accepts only subqueries wich return one column
only.
Can I someway (assuming that performance is not a point) force INTERSECT
rewriter to generate code
that confront only the primary key and not all the fields?

Thanks.

Marko Mikulicic

From bouncefilter Sun Dec 5 19:07:55 1999
Received: from s8-37-26.student.washington.edu
(S8-37-26.student.washington.edu [128.208.37.26])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA96468
for <pgsql-general@postgreSQL.org>; Sun, 5 Dec 1999 19:06:57 -0500 (EST)
(envelope-from jcwells@u.washington.edu)
Received: from localhost (jcw@localhost)
by s8-37-26.student.washington.edu (8.9.3/8.9.3) with ESMTP id AAA65361;
Mon, 6 Dec 1999 00:10:46 GMT (envelope-from jcwells@u.washington.edu)
X-Authentication-Warning: s8-37-26.student.washington.edu: jcw owned process
doing -bs
Date: Mon, 6 Dec 1999 00:10:46 +0000 (GMT)
From: "Jason C. Wells" <jcwells@u.washington.edu>
X-Sender: jcw@s8-37-26.student.washington.edu
Reply-To: "Jason C. Wells" <jcwells@u.washington.edu>
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
cc: pgsql-general@postgreSQL.org, "Jason C. Wells" <jcwells@u.washington.edu>
Subject: Re: [GENERAL] Buggered Sequence
In-Reply-To: <19991204160848.B19842@rice.edu>
Message-ID:
<Pine.BSF.4.10.9912060010030.65356-100000@s8-37-26.student.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 4 Dec 1999, Ross J. Reedstrom wrote:

Jason -
Jesse's sugestion should work, but there's a setval() function for
this exact use:

SELECT setval('people_id_seq',44);

I usually use it like this:

SELECT setval('"Experiments_ExptID_seq"',max("ExptID")) from "Experiments";

That automatically sets the sequence value to the current max in the table.

Hmmm. Thanks for the tip. It looks like I will have to dig a little deeper
into postgres.

Thank You, | http://students.washington.edu/jcwells/
Jason Wells

From bouncefilter Sun Dec 5 19:56:55 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA02170;
Sun, 5 Dec 1999 19:56:34 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id UAA42634;
Sun, 5 Dec 1999 20:56:48 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Sun, 5 Dec 1999 20:56:47 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
cc: jeff@pgsql.com, pgsql-hackers@postgresql.org
Subject: Oft Ask: How to contribute to PostgreSQL?
Message-ID: <Pine.BSF.4.21.9912052011040.823-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Due to a recent thread started on pgsql-hackers, I'm posting this to the
lists. Vince is planning on putting in appropriate links for some of
this, and, Bruce, can we maybe put it into the FAQ?

I'm not an English major, so this is more techinese then anything
else...or, a rambling of an un-ordered mind, however you want to classify
it :)

============

There are several ways that people can contribute to the PostgreSQL
project, and, below, I'm going to try and list them...

1. Code. We have a TODO list available at
http://www.postgresql.org/docs/todo.html, which lists enhancements that
have been picked out as needed. Some of them take time to learn the
intricacies of the code, some require no more then time. Contributing
code, altho not the only way to contribute, is always one of the more
valuable ways of improving any Open Source Project.

2. Web Site. http://www.postgresql.org is mirrored on many sites around
the world, as is ftp://ftp.postgresql.org. By increasing the number of
mirrors available around the world, you help reduce the load on any one
site, as well as improve the accessibility to the code. If you have
the resources to provide a mirror, both hardware and bandwidth, this is
another means of contributing to the project. All our mirrors are
required to use rsync, in order to be listed, with details on this
found at http://www.postgresql.org/howtomirror.html

3. Mailing Lists. We use software that allows us to use remote sites for
'mail relaying'. Basically, instead of our central server having to
service *all* remote addresses, it offloads email onto remote servers
to do the distribution. For intance, by dumping all email destined for
a subscribers in France to a server residing in France, the central
server has to send one email mesage "Across the pond", and let the
server in France handle the other servers. If you are interested in
providing a relay point, email scrappy@hub.org (me) for details on how
to get setup for this.

4. Financial. In June of 1999, PostgreSQL, Inc was formed as the
"Commercial Arm" of the PostgreSQL Project. Although it was originally
formed to provide Commercial Support for PostgreSQL, it has expanded to
include Consulting services, PostgreSQL Merchandise (ElephantWear) and,
most recently, Database Hosting services.

As our mission statement (http://www.pgsql.com/mission.html) states,
our purpose (among several) is to provide funding for various project,
whether they be Advertising or Programming. Although not currently
available, but will be when the new site is up, there will be a set of
pages off of http://www.pgsql.com that will provide a cleaner means of
contribute financially towards having features implemented, as well as
showing funds available for various projects. For instance, 25% of the
revenue from Support Contracts will be ear-marked for stuff like
Advertising and a General Pool that we can use to fund projects that we
feel is important from a "commercial deployment" standpoint.

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Dec 6 02:16:00 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id CAA69300
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 02:15:46 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id 646C81F72; Mon, 6 Dec 1999 02:17:06 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id 4FA281F42
for <pgsql-general@postgresql.org>;
Mon, 6 Dec 1999 02:17:06 +0000 (GMT)
Date: Mon, 6 Dec 1999 02:17:06 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: WaitOnLock error on wakeup
Message-ID: <Pine.BSF.4.10.9912060205560.59446-100000@server.b0x.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am getting a WaitOnLock error on wakeup when searching my database
using php on my website. This is clearly a pgsql error message, but I
can't seem to understand why pgsql would lock on me.

My problem query returns batches of 100 found products and I keep
statistics for each product found. Therefore, there is 100 writes to the
db for each query. My code causing the error looks like:
update product_table set stat='$x' where id='$id';

My current OS and software are:
Freebsd 3.3-CURRENT with the following ports:
apache+php+mod_ssl-1.3.9+3.0.12+2.4.2
postgresql-5.4.1

I am running postmaster with the following flags:
postmaster -i -S -o -F

Thanks in advance,
Marc

From bouncefilter Sun Dec 5 21:45:56 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA21024
for <pgsql-general@postgreSQL.org>; Sun, 5 Dec 1999 21:44:57 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id KAA14376;
Mon, 6 Dec 1999 10:44:53 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma014374; Mon, 6 Dec 99 10:44:40 +0800
Message-Id: <3.0.5.32.19991206104518.008a8420@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 06 Dec 1999 10:45:18 +0800
To: Mike Mascari <mascarm@mascari.com>, Slavica Stefic <izvori@iname.com>,
pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] null and =
In-Reply-To: <384AE02E.F5FE985B@mascari.com>
References: <384AB0C5.93F97204@iname.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 04:59 PM 05-12-1999 -0500, Mike Mascari wrote:

Instead, I would use a correlated subquery with an EXISTS/NOT EXISTS test
against the criteria for which you are searching:

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a)
....

I've got two tables, the first table contains "user accounts" and I'd like
to insert rows in the second table if necessary (if the userids don't exist
in the second table).

My query to find out which ids need to be inserted is something like this:
select usr_id,usr_login from users where usr_id not in (select userid from
wm_accounts);

(first table = users, second table = wm_accounts)

Is there a way of doing this efficiently and effectively? I cannot use
rules because I need to insert some extra nondatabase data into the second
table.

I would prefer a query which can work if the second table is null. The
problem with other queries I thought of was they would return null if the
second table is null.

I could in theory modify the program which inserts rows to the first table
and make it insert rows to the second table, however I'd like to keep a
functional and logical separation between the two programs (they aren't
supposed to be doing each others jobs).

Any suggestions?

Thanks,
Link.

From bouncefilter Sun Dec 5 22:18:57 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA31194
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 22:18:40 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-265.ocis.net [209.52.174.99])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id TAA31420
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 19:18:38 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <384B2A57.B779C4B9@mail.ocis.net>
Date: Sun, 05 Dec 1999 19:15:35 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
References: <Pine.BSF.4.21.9912052011040.823-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

Is PG done in C or C++?

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

Debian!Linux!

From bouncefilter Sun Dec 5 22:38:57 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA33795
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 22:38:40 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA43627;
Sun, 5 Dec 1999 23:38:31 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Sun, 5 Dec 1999 23:38:30 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Jason C. Leach" <jcl@mail.ocis.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
In-Reply-To: <384B2A57.B779C4B9@mail.ocis.net>
Message-ID: <Pine.BSF.4.21.9912052338200.823-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 5 Dec 1999, Jason C. Leach wrote:

hi,

Is PG done in C or C++?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Sun Dec 5 22:40:57 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA34254
for <pgsql-general@postgreSQL.org>; Sun, 5 Dec 1999 22:40:48 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id WAA05692;
Sun, 5 Dec 1999 22:36:56 -0500
Message-ID: <384B2FEC.DC613408@mascari.com>
Date: Sun, 05 Dec 1999 22:39:24 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Lincoln Yeoh <lylyeoh@mecomb.com>
CC: lylyeoh@mecomb.com, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] null and =
References: <384AB0C5.93F97204@iname.com>
<3.0.5.32.19991206104518.008a8420@pop.mecomb.po.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lincoln Yeoh wrote:

At 04:59 PM 05-12-1999 -0500, Mike Mascari wrote:

Instead, I would use a correlated subquery with an EXISTS/NOT EXISTS test
against the criteria for which you are searching:

SELECT t1.a, t1.b FROM dummy t1
WHERE EXISTS (SELECT t2.a FROM dummy t2 WHERE t1.a = t2.a)
....

I've got two tables, the first table contains "user accounts" and I'd like
to insert rows in the second table if necessary (if the userids don't exist
in the second table).

My query to find out which ids need to be inserted is something like this:
select usr_id,usr_login from users where usr_id not in (select userid from
wm_accounts);

(first table = users, second table = wm_accounts)

Is there a way of doing this efficiently and effectively? I cannot use
rules because I need to insert some extra nondatabase data into the second
table.

I would just do:

SELECT users.usr_id, users.usr_login FROM users WHERE NOT EXISTS
(SELECT wm_accounts.usr_id FROM wm_accounts WHERE
wm_accounts.usr_id = users.usr_id);

I would prefer a query which can work if the second table is null. The
problem with other queries I thought of was they would return null if the
second table is null.

I'm not sure what you mean here. Do you mean the table doesn't exist, is empty,
or that the usr_id field is NULL?

I could in theory modify the program which inserts rows to the first table
and make it insert rows to the second table, however I'd like to keep a
functional and logical separation between the two programs (they aren't
supposed to be doing each others jobs).

What happens if a record is added to wm_accounts? Do you want a record to also
be created in users as well, or is users a superset with respect to wm_accounts
and usr_id?

Any suggestions?

Thanks,
Link.

From bouncefilter Sun Dec 5 22:47:57 1999
Received: from bigiron.sopac.org.fj (bigiron.sopac.org.fj [202.62.0.150] (may
be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id WAA34994
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 22:47:10 -0500 (EST)
(envelope-from Franck@sopac.org.fj)
Received: by bigiron.sopac.org.fj with Internet Mail Service (5.5.2448.0)
id <Y1SKYJCC>; Mon, 6 Dec 1999 16:45:39 +1300
Message-ID: <F12ECEA0435AD211B5280008C7ACBC857FE740@bigiron.sopac.org.fj>
From: Franck Martin <Franck@sopac.org.fj>
To: pgsql-list <pgsql-general@hub.org>
Subject: RE: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
Date: Mon, 6 Dec 1999 16:45:10 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

Does anybody know about some GIS or GPS software using PostgreSQL outside
GRASS?

Thanks.

Franck Martin
Network and Database Development Officer
SOPAC South Pacific Applied Geoscience Commission
Fiji
E-mail: franck@sopac.org.fj <mailto:franck@sopac.org.fj>
Web site: www.sopac.org.fj <http://www.sopac.org.fj>

From bouncefilter Sun Dec 5 23:03:54 1999
Received: from ocis.ocis.net (IDENT:root@ocis.ocis.net [209.52.173.1])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA37248
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 23:00:18 -0500 (EST)
(envelope-from jcl@mail.ocis.net)
Received: from mail.ocis.net (jcl@dial-1.ocis.net [209.52.173.33])
by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id UAA02600;
Sun, 5 Dec 1999 20:00:15 -0800
Sender: jcl@ocis.ocis.net
Message-ID: <384B3418.5477E545@mail.ocis.net>
Date: Sun, 05 Dec 1999 19:57:12 -0800
From: "Jason C. Leach" <jcl@mail.ocis.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Loehr <ELOEHR@austin.rr.com>
CC: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] procmail w/ PG.
References: <384ABA80.7C23BB04@mail.ocis.net> <384ACACC.BFA8223@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

hi,

That looks promising. Any idea where the mail reformatted 'formail' gets
the input email? From STDIN?

Ed Loehr wrote:

"Jason C. Leach" wrote:

:0

* ^Subject:.*Digest
|formail +1 -d -s procmail

This sounds like a task well-suited to perl regular expressions with
DBI/DBD::Pg. I found it quite worthwhile when setting up procmail to
spend some time carefully reviewing the various procmail filter options

--
.............
......... Jason C. Leach
...... University College of the Cariboo
... jcl@mail.ocis.net.
.. http://www.ocis.net/~jcl
.

Debian!Linux!

From bouncefilter Sun Dec 5 23:21:58 1999
Received: from bigiron.sopac.org.fj (bigiron.sopac.org.fj [202.62.0.150] (may
be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id XAA46386
for <pgsql-general@hub.org>; Sun, 5 Dec 1999 23:21:13 -0500 (EST)
(envelope-from Franck@sopac.org.fj)
Received: by bigiron.sopac.org.fj with Internet Mail Service (5.5.2448.0)
id <Y1SKYJD1>; Mon, 6 Dec 1999 17:19:41 +1300
Message-ID: <F12ECEA0435AD211B5280008C7ACBC857FE741@bigiron.sopac.org.fj>
From: Franck Martin <Franck@sopac.org.fj>
To: pgsql-list <pgsql-general@hub.org>
Subject: GIS and PostgreSQL ?
Date: Mon, 6 Dec 1999 17:19:23 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

Does anybody know some GIS software used with PostgreSQL ?

From bouncefilter Mon Dec 6 01:56:00 1999
Received: from goliath.dart.ro (IDENT:root@goliath.dart.ro [193.231.249.1])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA66681
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 01:55:52 -0500 (EST)
(envelope-from mkaroly@hotpop.com)
Received: from hotpop.com (tc01-dialup060.dart.ro [193.231.249.188])
by goliath.dart.ro (8.9.3/8.9.3) with ESMTP id IAA01478
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 08:56:36 +0200
Message-ID: <384B5E49.FF56A382@hotpop.com>
Date: Mon, 06 Dec 1999 08:57:13 +0200
From: Madarasz Karoly <mkaroly@hotpop.com>
Reply-To: mkaroly@hotpop.com
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: database GUI library for C,C++
References: <19991203133952.47598.qmail@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello!

I try to make a PostgreSQL based GUI aplication.
I find a lot of GUI libraries, but none of them
have 'high level' classes for accessing and displaying
dates from databases in a more convenient mode.
(like TTable, TDBGrid in Delphi)
Is there something like that?

Thanks,
Karesz.

From bouncefilter Mon Dec 6 02:01:00 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA67260
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 02:00:16 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id PAA16832;
Mon, 6 Dec 1999 15:00:04 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma016825; Mon, 6 Dec 99 14:59:36 +0800
Message-Id: <3.0.5.32.19991206150010.008a9450@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 06 Dec 1999 15:00:10 +0800
To: Mike Mascari <mascarm@mascari.com>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] null and =
Cc: pgsql-general@postgreSQL.org
In-Reply-To: <384B2FEC.DC613408@mascari.com>
References: <384AB0C5.93F97204@iname.com>
<3.0.5.32.19991206104518.008a8420@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:39 PM 05-12-1999 -0500, Mike Mascari wrote:

I would just do:

SELECT users.usr_id, users.usr_login FROM users WHERE NOT EXISTS
(SELECT wm_accounts.usr_id FROM wm_accounts WHERE
wm_accounts.usr_id = users.usr_id);

OK, my current query is
select usr_id,usr_login from users where usr_id not in (select userid from
wm_accounts);

Your query on small test tables (after vacuum analyze):
Seq Scan on users (cost=1.83 rows=25 width=16)

SubPlan
-> Seq Scan on wm_accounts (cost=1.33 rows=2 width=4)

My query:
Seq Scan on users (cost=1.83 rows=25 width=16)

SubPlan
-> Seq Scan on wm_accounts (cost=1.33 rows=10 width=4)

What does rows mean? But it looks like your query is better :). Don't fully
understand why tho. Would it work if wm_accounts is empty?

I would prefer a query which can work if the second table is null. The
problem with other queries I thought of was they would return null if the
second table is null.

I'm not sure what you mean here. Do you mean the table doesn't exist, is

empty,

or that the usr_id field is NULL?

I meant the table is empty.

What happens if a record is added to wm_accounts? Do you want a record to

also

be created in users as well, or is users a superset with respect to

wm_accounts

and usr_id?

Users is a superset.

Thanks for your suggestion,

Link.

From bouncefilter Mon Dec 6 04:18:03 1999
Received: from troie.INTRINsec.com (troie.INTRINsec.com [194.98.42.3])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA86511
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 04:17:29 -0500 (EST)
(envelope-from edx@intrinsec.com)
Received: from sync.intrinsec.com (sync.INTRINsec.com [194.98.42.5])
by troie.INTRINsec.com (8.9.3/8.9.3) with ESMTP id LAA04438
for <pgsql-general@postgreSQL.org>;
Mon, 6 Dec 1999 11:19:41 +0100 (GMT+0100)
Received: from dooz.corp.intrinsec.com (dooz.corp.INTRINsec.com [10.100.1.12])
by sync.intrinsec.com (8.8.8/8.8.8) with SMTP id KAA21281
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 10:20:41 +0100 (CET)
From: Edouard DESSIOUX <edx@intrinsec.com>
Organization: INTRINsec
To: pgsql-general@postgreSQL.org
Subject: How to select where ....
Date: Mon, 6 Dec 1999 10:19:32 +0100
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99120610214603.02757@dooz.corp.intrinsec.com>
Content-Transfer-Encoding: 8bit

Hello,

I've encountered a pb while making a simple request :
A have a field date whose type is timestamp and I would like
to make a select like :
select * from truc
where date > (current_timestamp - 10 days)

Anyone know how I could perform such a query

Txs

--
Edouard DESSIOUX
Proverbe chien :
"Si ca se mange pas,
Si ca se baise pas,
Pisse dessus !!"

From bouncefilter Mon Dec 6 04:40:03 1999
Received: from ns1.info-ufr.univ-montp2.fr (ns1.info-ufr.univ-montp2.fr
[162.38.218.218]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA89526
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 04:39:52 -0500 (EST)
(envelope-from frederik.guitton@info-ufr.univ-montp2.fr)
Received: from info-ufr.univ-montp2.fr (respawn.info-ufr.univ-montp2.fr
[162.38.218.213])
by ns1.info-ufr.univ-montp2.fr (8.9.3/8.9.3) with ESMTP id KAA26819
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 10:39:49 +0100
Message-ID: <384B8465.2604259A@info-ufr.univ-montp2.fr>
Date: Mon, 06 Dec 1999 10:39:49 +0100
From: =?iso-8859-1?Q?fr=E9d=E9rik?= GUITTON
<frederik.guitton@info-ufr.univ-montp2.fr>
X-Mailer: Mozilla 4.7 [fr] (WinNT; I)
X-Accept-Language: fr
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: PostGres ODBC Drivers
Content-Type: multipart/mixed; boundary="------------A40155984848F6097C22E0ED"

Il s'agit d'un message multivolet au format MIME.
--------------A40155984848F6097C22E0ED
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
I'm looking for PostGresSQL ODBC driver for winwos NT ?
Can you help me ???

Regards

--------------A40155984848F6097C22E0ED
Content-Type: text/x-vcard; charset=us-ascii;
name="frederik.guitton.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Carte pour fr�d�rik GUITTON
Content-Disposition: attachment;
filename="frederik.guitton.vcf"

begin:vcard
n:GUITTON;Fr�d�rik
x-mozilla-html:FALSE
url:www.ufr.lirmm.fr
org:UM2 - UFR-Science;D�partement informatique
adr:;;Place Eugene Bataillon;Montpellier;;34000;FRANCE
version:2.1
email;internet:fr�d�rik.guitton@info-ufr.univ-montp2.fr
title:technicien micro-r�seau
fn:GUITTON
end:vcard

--------------A40155984848F6097C22E0ED--

From bouncefilter Mon Dec 6 05:11:16 1999
Received: from mailsrv.concept.net.sa ([212.46.175.24])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA96094
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 05:10:29 -0500 (EST)
(envelope-from sko@concept.net.sa)
Received: from localhost.localdomain ([212.46.177.150])
by mailsrv.concept.net.sa (Netscape Messaging Server 3.5)
with SMTP id AAA3FBF10 for <pgsql-general@postgreSQL.org>;
Mon, 6 Dec 1999 13:08:24 +0300
Received: from localhost (sko@localhost)
by localhost.localdomain (8.9.3/8.8.7) with ESMTP id NAA04433
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 13:08:21 +0307
Date: Mon, 6 Dec 1999 13:08:19 +0307 (??)
From: "Stephan Koepp" <sko@concept.net.sa>
To: pgsql-general@postgreSQL.org
Subject: subscribe
Message-ID: <Pine.LNX.4.10.9912061307570.4406-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

subscribe
end

___________________
Stephan Koepp - Al Jubail - Saudi Arabia

From bouncefilter Mon Dec 6 05:06:16 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA95307
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 05:05:30 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id FAA06492;
Mon, 6 Dec 1999 05:01:03 -0500
Message-ID: <384B89F5.A71EDE6@mascari.com>
Date: Mon, 06 Dec 1999 05:03:33 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Lincoln Yeoh <lylyeoh@mecomb.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] null and =
References: <384AB0C5.93F97204@iname.com>
<3.0.5.32.19991206104518.008a8420@pop.mecomb.po.my>
<3.0.5.32.19991206150010.008a9450@pop.mecomb.po.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lincoln Yeoh wrote:

At 10:39 PM 05-12-1999 -0500, Mike Mascari wrote:

I would just do:

SELECT users.usr_id, users.usr_login FROM users WHERE NOT EXISTS
(SELECT wm_accounts.usr_id FROM wm_accounts WHERE
wm_accounts.usr_id = users.usr_id);

OK, my current query is
select usr_id,usr_login from users where usr_id not in (select userid from
wm_accounts);

Your query on small test tables (after vacuum analyze):
Seq Scan on users (cost=1.83 rows=25 width=16)

SubPlan
-> Seq Scan on wm_accounts (cost=1.33 rows=2 width=4)

My query:
Seq Scan on users (cost=1.83 rows=25 width=16)

SubPlan
-> Seq Scan on wm_accounts (cost=1.33 rows=10 width=4)

What does rows mean? But it looks like your query is better :). Don't fully
understand why tho. Would it work if wm_accounts is empty?

Yes, certainly. If you envision what the backend is doing, for NOT EXISTS, its
something like this:

for each users record
perform an index or sequential lookup in wm_accounts for a matching usr_id:
found: continue
not found: output usr_id
next users record

If, however, you use the NOT IN clause, it looks more like this:

for each users record
for each wm_accounts record
if users.usr_id = wm_accounts.usr_id, continue to next users record
next wm_accounts record
output usr_id
next users record

At least with the EXISTS/NOT EXISTS method, you give the backend the opportunity
to use indexes on the correlated table. Most commercial databases will
instantiate a temporary table when processing IN clauses and will rewrite the
query as an EXISTS (or DISTINCT join/outer join). PostgreSQL doesn't do that at
the moment. What indexes do you have on users and wm_accounts? You should have
one on usr_id of both. It may simply be that the optimizer isn't using indexes
since the number of rows is small. Here is a pseudo-equivalent explain plan from
a production database:

explain select webuser from webusers where not exists (
select permitbuy.webuser from permitbuy where webusers.webuser =
permitbuy.webuser);

NOTICE: QUERY PLAN:

Seq Scan on webusers (cost=7.78 rows=145 width=12)
SubPlan
-> Index Scan using k_permitbuy1 on permitbuy (cost=4.36 rows=48 width=12)

EXPLAIN

vs. using IN:

explain select webuser from webusers where webuser not in (select webuser from
permitbuy);

NOTICE: QUERY PLAN:

Seq Scan on webusers (cost=7.78 rows=145 width=12)
SubPlan
-> Seq Scan on permitbuy (cost=32.05 rows=759 width=12)

EXPLAIN

Hope that helps,

Mike

From bouncefilter Mon Dec 6 08:17:21 1999
Received: from test133.ee.ic.ac.uk (IDENT:root@test133.ee.ic.ac.uk
[155.198.133.240]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA19991
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 08:17:05 -0500 (EST)
(envelope-from smacedo@ic.ac.uk)
Received: from localhost (smacedo@localhost)
by test133.ee.ic.ac.uk (8.9.3/8.9.3) with ESMTP id NAA12863;
Mon, 6 Dec 1999 13:15:52 GMT
X-Authentication-Warning: test133.ee.ic.ac.uk: smacedo owned process doing -bs
Date: Mon, 6 Dec 1999 13:15:51 +0000 (GMT)
From: Silvio Macedo <smacedo@ic.ac.uk>
X-Sender: smacedo@test133.ee.ic.ac.uk
To: ussl@usa.net
cc: pgsql general mailing list <pgsql-general@postgresql.org>
Subject: JDBC / JBUILDER
Message-ID: <Pine.LNX.4.21.9912061310130.1181-100000@test133.ee.ic.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Regarding using JDBC on a Windows machine to access a Postgresql DB on
Linux... :

You don't need to do anything special.

See the postgresql/src/interface/jdbc/example directory, specially
the basic.java

It does not matter if you are using JBuilder or Windows...

If you want to use those borland.sql classes, then, you must learn
them from Borland docs.

As far as using java.sql stuff, everything is plain and simple
like in basic.java .

Silvio
--

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
``````````````````````````````````````````````````````````````````````````
Silvio Emanuel Nunes Barbosa de Macedo

From bouncefilter Mon Dec 6 08:41:22 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA23972
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 08:40:24 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id OAA22473;
Mon, 6 Dec 1999 14:40:15 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11uz96-0003Ps-00; Mon, 6 Dec 1999 14:29:44 +0000
Message-ID: <384BBB04.9FA114E5@sferacarta.com>
Date: Mon, 06 Dec 1999 14:32:52 +0100
From: jose soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: Edouard DESSIOUX <edx@intrinsec.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to select where ....
References: <99120610214603.02757@dooz.corp.intrinsec.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

create table truc (a datetime);
CREATE
insert into truc values(current_timestamp);
INSERT 1869961 1
insert into truc values('1999-11-25 12:30:00');
INSERT 1869962 1
select * from truc;
a
--------------------------
06/12/1999 15:28:14.00 CET
25/11/1999 12:30:00.00 CET
(2 rows)

select * from truc
where a > (current_timestamp - interval '10 days');
a
--------------------------
06/12/1999 15:28:14.00 CET
(1 row)

Jos�

Edouard DESSIOUX ha scritto:

Hello,

I've encountered a pb while making a simple request :
A have a field date whose type is timestamp and I would like
to make a select like :
select * from truc
where date > (current_timestamp - 10 days)

Anyone know how I could perform such a query

Txs

--
Edouard DESSIOUX
Proverbe chien :
"Si ca se mange pas,
Si ca se baise pas,
Pisse dessus !!"

************

From bouncefilter Mon Dec 6 09:45:43 1999
Received: from hotmail.com (f118.law3.hotmail.com [209.185.241.118])
by hub.org (8.9.3/8.9.3) with SMTP id JAA33550
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 09:45:08 -0500 (EST)
(envelope-from lv68@hotmail.com)
Received: (qmail 85717 invoked by uid 0); 6 Dec 1999 14:44:37 -0000
Message-ID: <19991206144437.85716.qmail@hotmail.com>
Received: from 192.6.76.68 by www.hotmail.com with HTTP;
Mon, 06 Dec 1999 06:44:37 PST
X-Originating-IP: [192.6.76.68]
From: "vincent leycuras" <lv68@hotmail.com>
To: pgsql-general@postgreSQL.org
Subject: java and postgres
Date: Mon, 06 Dec 1999 13:44:37 EGT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Seems like java doesn't just bring solutions...
I installed pgsql 6.5.1 on my linux 2.2 this Week End. I compiled it not
understanding how the rpms installed the thing. Then I tried to install
JDBC. That time I took the rpm devoted to that driver. I eventually switched
to using the driver provided with the source, as I thought there might be
some question of compatibility hidden behind my problem. Then I tried to run
an example provided with the source. I use Jikes as a compiler and java to
run programs. jikes compiles without even a warning the Basic.java (there
seemed to be a case problem so basic.java became Basic.java). but when I run
the program, I get the following:
Error loading class Basic: Wrong name
And I just can't understand where this error message comes from, nor what it
means!!!
Please help!!
Vincent.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

From bouncefilter Mon Dec 6 10:14:43 1999
Received: from photon.skillbrokers.bg (root@[195.24.42.194])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA37752;
Mon, 6 Dec 1999 10:13:50 -0500 (EST)
(envelope-from nmmm@webfactory.bg)
Received: from niki (proton.skillbrokers.bg [195.24.42.206])
by photon.skillbrokers.bg (8.9.0/8.9.0) with SMTP id RAA26841;
Mon, 6 Dec 1999 17:05:23 +0200
Message-ID: <000501bf3ffc$638f2fe0$ce2a18c3@skillbrokers.bg>
From: "Nikolay Mijaylov" <nmmm@webfactory.bg>
To: "pgsql-general" <pgsql-general@postgreSQL.org>,
<pgsql-sql@postgreSQL.org>,
<pgsql-error@postgreSQL.org>
Subject: Whats happen here?
Date: Mon, 6 Dec 1999 17:13:00 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Whats happen here?
-------------------------

root=> \dt

Database    = root
 +------------------+----------------------------------+----------+
 |  Owner           |             Relation             |   Type   |
 +------------------+----------------------------------+----------+
 | root             | x                                | table    |
 | root             | y                                | table    |
 +------------------+----------------------------------+----------+
root=> \d x

Table    = x
+----------------------------------+----------------------------------+-----
--+
|              Field               |              Type                |
Length|
+----------------------------------+----------------------------------+-----
--+
| a                                | char()                           |
20 |
+----------------------------------+----------------------------------+-----
--+
root=> \d y

Table    = y
+----------------------------------+----------------------------------+-----
--+
|              Field               |              Type                |
Length|
+----------------------------------+----------------------------------+-----
--+
| a                                | varchar()                        |
5 |
+----------------------------------+----------------------------------+-----
--+
root=>select * from x a, y b where a.a = b.a;
ERROR:  There is more than one possible operator '=' for types 'bpchar' and
'varchar'
        You will have to retype this query using an explicit cast

--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

From bouncefilter Mon Dec 6 10:19:46 1999
Received: from photon.skillbrokers.bg (root@[195.24.42.194])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA38631;
Mon, 6 Dec 1999 10:18:48 -0500 (EST) (envelope-from nmmm@nmmm.nu)
Received: from niki (proton.skillbrokers.bg [195.24.42.206])
by photon.skillbrokers.bg (8.9.0/8.9.0) with SMTP id RAA26992;
Mon, 6 Dec 1999 17:10:25 +0200
Message-ID: <002001bf3ffd$17309980$ce2a18c3@skillbrokers.bg>
From: "Nikolay Mijaylov" <nmmm@nmmm.nu>
To: "pgsql-general" <pgsql-general@postgreSQL.org>, <pgsql-sql@postgreSQL.org>
Subject: Fw: Whats happen here?
Date: Mon, 6 Dec 1999 17:17:59 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Whats happen here?
-------------------------

root=> \dt

Database    = root
+------------------+----------------------------------+----------+
|  Owner           |             Relation             |   Type   |
+------------------+----------------------------------+----------+
| root             | x                                | table    |
| root             | y                                | table    |
+------------------+----------------------------------+----------+
root=> \d x

Table = x

+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | char() |
20 |

+----------------------------------+----------------------------------+-----

--+
root=> \d y

Table = y

+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | varchar() |
5 |

+----------------------------------+----------------------------------+-----

--+
root=>select * from x a, y b where a.a = b.a;
ERROR: There is more than one possible operator '=' for types 'bpchar'

and

'varchar'
You will have to retype this query using an explicit cast

root=> select * from x a, y b where text(a.a) = text(b.b);
ERROR: There is more than one possible operator '=' for types 'bpchar' and

'varchar'

You will have to retype this query using an explicit cast

--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

From bouncefilter Mon Dec 6 10:32:43 1999
Received: from mail4.mgfairfax.rr.com (fe4.southeast.rr.com [24.93.67.51])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA41117
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 10:32:08 -0500 (EST)
(envelope-from anon@mgfairfax.rr.com)
Received: from rsdevelop ([24.28.195.168]) by mail4.mgfairfax.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Mon, 6 Dec 1999 10:32:06 -0500
Message-ID: <083b01bf3fff$59d51390$0200a8c0@rsdevelop>
From: "Bruce Bantos" <anon@mgfairfax.rr.com>
To: <pgsql-general@postgresql.org>
Subject: test - please ignore
Date: Mon, 6 Dec 1999 10:34:14 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

From bouncefilter Mon Dec 6 11:23:52 1999
Received: from exchange2.usfreightways.com (usfreight-bh.usfreightways.com
[209.64.217.66]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA49190
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 11:23:08 -0500 (EST)
(envelope-from Lhuynh@USFreightways.com)
Received: by EXCHANGE2 with Internet Mail Service (5.5.2448.0)
id <X9GWRLH2>; Mon, 6 Dec 1999 10:23:11 -0600
Message-ID: <2187AEF0370ED3119EF500805FBB483BE517E3@USFEXCH>
From: "Huynh, Long" <Lhuynh@USFreightways.com>
To: "'pgsql-general@postgreSQL.org'" <pgsql-general@postgreSQL.org>
Subject: ODBC and JDBC setup
Date: Mon, 6 Dec 1999 10:20:06 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

I had Mandrake 6.1 (from RedHat) installed Postgresql on my PC
automatically. I have several newbie questions, if all these are provided
in the doc, please show me where.

1) How do I test to see if it's installed correctly?
2) Do I need to install ODBC and JDBC separately? If so, how?
3) Once I have installed the ODBC and JDBC on the Linux box, do I need to
install Samba in order for PCs with Windows 9x and NT to connect?

Thank you in advance for your kind assistance.

Long

From bouncefilter Mon Dec 6 12:04:59 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA55268
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 12:04:05 -0500 (EST)
(envelope-from kdebisschop@range.infoplease.com)
Received: from alert.infoplease.com ([208.222.166.25])
by trends.net (8.8.8/8.8.8) with ESMTP id LAA04743
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 11:56:29 -0500 (EST)
Received: from skillet.infoplease.com (skillet [10.0.1.212])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id LAA15582
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 11:55:21 -0500 (EST)
Received: (from kdebisschop@localhost)
by skillet.infoplease.com (8.9.3/8.9.1) id LAA19285;
Mon, 6 Dec 1999 11:55:21 -0500
Date: Mon, 6 Dec 1999 11:55:21 -0500
Message-Id: <199912061655.LAA19285@skillet.infoplease.com>
X-Authentication-Warning: skillet.infoplease.com: kdebisschop set sender to
kdebisschop@spaceheater.infoplease.com using -f
From: Karl DeBisschop <kdebisschop@range.infoplease.com>
To: pgsql-general@postgresql.org
Subject: concatenating two text attributes
Reply-to: kdebisschop@range.infoplease.com

I'd like to do something like

SELECT strcat(foo,bar) FROM test;

SELECT foo+bar FROM test;

where test is

CREATE TABLE test (foo char(20), bar char(20));
INSERT INTO test (foo,bar) VALUES ('foo','bar');

Of course it seems like it'd be easy enough to write a PL/TCL funcion
to do this (or pick your favorite PL here). But before I do that I'd
just like to check if PostgreSQL (or generic SQL for that matter)
provides a means of doing that. I've look through te docs, but I
don't see anything like it. Just seems so intuitive though.

So, is anyone aware of a way to to this that doesn't require
scripting? (Sorry if this is a newbie question -- I have looked).

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

From bouncefilter Mon Dec 6 11:58:00 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id LAA54265
for pgsql-general@postgresql.org; Mon, 6 Dec 1999 11:57:19 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: richmond@shadow.net (Rich Ackerman)
X-Newsgroups: comp.databases.postgresql.questions
Subject: backup strategy
Message-ID: <384be8f4.437783619@news.mia.bellsouth.net>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 23
Date: Mon, 06 Dec 1999 17:00:38 GMT
X-Trace: news2.mia 944499424 216.77.244.232 (Mon, 06 Dec 1999 11:57:04 EST)
To: pgsql-questions@postgresql.org

I inherited a website project using Postgres on linux and am now
working on a backup plan for the site.

I figure I can write a cron script to do a pg_dump every so often
(hourly? daily?). The site gets backed up to tape every day. Pretty
scrawny plan, eh?

Then, let's say the site gets hacked or the database crashes and it
needs to be restored. I know I can reverse the dump to get back where
it was when pg_dump was run, but what about the transactions after the
pg_dump? Do people have any strategies for backup that won't cause
those to be lost? It's a membership database with credit card
transactions, if that makes a difference.

The PostgreSQL User's Guide says, "This section needs to be written.
Volunteers?" for Chapter 13, "Database Recovery". Has anybody taken a
cut at it yet?

Thanks,

Rich Ackerman
richmond@shadow.net

From bouncefilter Mon Dec 6 12:29:59 1999
Received: from rapture.cyberflunk.com (root@rapture.cyberflunk.com
[199.217.80.1]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA58385
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 12:29:02 -0500 (EST)
(envelope-from nikm@cyberflunk.com)
Received: from localhost (nikm@localhost)
by rapture.cyberflunk.com (8.9.3/8.9.1) with ESMTP id JAA25910
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 09:28:46 -0800
Date: Mon, 6 Dec 1999 09:28:46 -0800 (PST)
From: Nikos Mouat <nikm@cyberflunk.com>
To: pgsql-general@postgreSQL.org
Subject: timezone correction.
In-Reply-To: <3.0.5.32.19991206104518.008a8420@pop.mecomb.po.my>
Message-ID: <Pine.C=64.4.21.9912060927570.25604-100000@rapture.cyberflunk.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is this a bug?

bleah=> select ('Mon Nov 29 21:47:04 PST 1999'::timestamp);
?column?
----------------------
1999-11-30 00:47:04-05
(1 row)

bleah=> select ('Mon Nov 29 21:47:04 PST 1999'::timestamp)::date;
?column?
----------
11-29-1999
(1 row)

bleah=>

From bouncefilter Mon Dec 6 14:35:01 1999
Received: from dec.contad.unam.mx (dec.contad.unam.mx [132.248.158.18])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA78394
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 14:34:57 -0500 (EST)
(envelope-from sony@dec.contad.unam.mx)
Received: from localhost (sony@localhost) by dec.contad.unam.mx with ESMTP
(8.7.1/8.7.1) id NAA10090 for <pgsql-general@postgresql.org>;
Mon, 6 Dec 1999 13:22:35 -0600 (CST)
Date: Mon, 6 Dec 1999 13:22:35 -0600 (CST)
From: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
X-Sender: sony@dec.contad.unam.mx
To: pgsql-general@postgresql.org
Subject: Question?
Message-ID: <Pine.HPX.4.10.9912061319440.9988-100000@dec.contad.unam.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello there!

I want to install postgresql in my server, but I have not found
some information about the relation between Postgresql and Perl.

Somebody can help me sent me an URL or name of mailing lists where
I can find information about it???

Thanks!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
I thougth I saw a man brougth to life
He was warm, he came around
like he was dignified
He show me what it was to cry
Well , you could be that man I adore...
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Sonia Sanchez Diaz
UNAM_FCA_CIFCA_Admon.Red
e-mail: sony@dec.contad.unam.mx

From bouncefilter Mon Dec 6 14:42:01 1999
Received: from dec.contad.unam.mx (dec.contad.unam.mx [132.248.158.18])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA79386
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 14:41:29 -0500 (EST)
(envelope-from sony@dec.contad.unam.mx)
Received: from localhost (sony@localhost) by dec.contad.unam.mx with ESMTP
(8.7.1/8.7.1) id NAA10279 for <pgsql-general@postgresql.org>;
Mon, 6 Dec 1999 13:29:07 -0600 (CST)
Date: Mon, 6 Dec 1999 13:29:07 -0600 (CST)
From: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
X-Sender: sony@dec.contad.unam.mx
To: pgsql-general@postgresql.org
Subject: Question?
Message-ID: <Pine.HPX.4.10.9912061328410.10258-100000@dec.contad.unam.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello there!

I want to install postgresql in my server, but I have not found
some information about the relation between Postgresql and Perl.

Somebody can help me sent me an URL or name of mailing lists where
I can find information about it???

Thanks!

Sonia Sanchez Diaz
UNAM_FCA_CIFCA_Admon.Red
e-mail: sony@dec.contad.unam.mx

From bouncefilter Mon Dec 6 16:43:10 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA98134
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 16:42:59 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.3.127]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Mon, 6 Dec 1999 15:34:37 -0600
Sender: ed
Message-ID: <384C2DEB.F5A993B0@austin.rr.com>
Date: Mon, 06 Dec 1999 15:43:07 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Question?
References: <Pine.HPX.4.10.9912061328410.10258-100000@dec.contad.unam.mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sanchez Diaz Sonia wrote:

Hello there!

I want to install postgresql in my server, but I have not found
some information about the relation between Postgresql and Perl.

Somebody can help me sent me an URL or name of mailing lists where
I can find information about it???

Thanks!

You might want to read up on perl DBI and DBD::Pg at CPAN, which facilitate
Postgresql access from perl.

Some possibly helpful references:

http://www.cpan.org/
http://www.deja.com/

Cheers.
Ed Loehr

From bouncefilter Mon Dec 6 17:45:11 1999
Received: from www.theinternetdirectory.net ([207.225.37.177])
by hub.org (8.9.3/8.9.3) with SMTP id RAA06238
for <pgsql-general@hub.org>; Mon, 6 Dec 1999 17:44:58 -0500 (EST)
(envelope-from affiliate1@www.theinternetdirectory.net)
From: affiliate1@www.theinternetdirectory.net
Message-Id: <199912062244.RAA06238@hub.org>
To: pgsql-general@hub.org
Subject: The Internet Directories
Date: Mon, 06 Dec 1999 15:47:46 -0700
X-Sender: affiliate1@www.theinternetdirectory.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 3
X-MSMail-Priority: Normal

I visited http://www.se.postgresql.org/mhonarc/pgsql-general and I got your email address.
I felt you might be interested in knowing that 98% of all sites visited
are found on directories or search engines.

The Internet Directories http://www.theinternetdirectories.com
is one of the fastest growing Directories on the Internet.

"Working with you to organize the Internet"

* List your site on The Cyberhound search engine "And Be Found"
A WORLD WIDE search engine There is no cost or obligation
to be listed on the Cyberhound. http://www.thecyberhound.com/
* List your business at a level 1 Free in the Directories.
* Build Web Pages Free with the WEB PAGE WIZARD. " No catch"
http://www.web-page-wizard.com/
* All About Pets (free lost and found database)
* Suggest New Catagories

I read each response and will relpy within a few days.
This is not sent from a spam list. However if you do not want
to be contacted from the site above.

Hit reply and Put remove in the subject line

Sorry If this email was an inconvience.

affiliate1
197 N. Linder
Meridian Idaho

From bouncefilter Mon Dec 6 21:06:13 1999
Received: from mail.pbpower.co.nz (mail.designpower.co.nz [203.97.56.178])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA32489
for <pgsql-general@postgresql.org>; Mon, 6 Dec 1999 21:05:23 -0500 (EST)
(envelope-from DerricuttM@pbworld.com)
Received: by mail.pbpower.co.nz with Internet Mail Service (5.5.2650.21)
id <XSGG11NK>; Tue, 7 Dec 1999 15:06:44 +1300
Message-ID: <93314B6256A5D211BE8B006097B9502717912B@NZAM>
From: "Derricutt, Mark" <DerricuttM@pbworld.com>
To: "'pgsql-general@postgresql.org'" <pgsql-general@postgresql.org>
Subject: Left Join Queries
Date: Tue, 7 Dec 1999 15:05:45 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
charset="iso-8859-1"

Hi, I was just wondering if PostgreSQL supports left join queries yet? Or
if not, if its on the cards to the next release?

I'm in the process of porting an application from Paradox to use several
database servers, and was surprised to read in some older posts (from the
web-archive) that PostgreSQL didn't do left joins.

One of the queries I'm doing is as follows (rather simple as well):

SELECT a.CrossID, a.Name, a.LandScape, COUNT(b.CrossID) AS countfld
FROM ctabhed a LEFT JOIN ctabdat b ON a.CrossID = b.CrossID
GROUP BY a.CrossID, a.Name, a.LandScape

This just returns the header data, and the count of the detail in one table.

Mark

--
Mark Derricutt
Now Playing: Roine Stolt - The flower king

From bouncefilter Mon Dec 6 21:14:15 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA33654;
Mon, 6 Dec 1999 21:13:37 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id KAA25290;
Tue, 7 Dec 1999 10:13:28 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma025284; Tue, 7 Dec 99 10:13:00 +0800
Message-Id: <3.0.5.32.19991207101333.00900430@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 07 Dec 1999 10:13:33 +0800
To: The Hermit Hacker <scrappy@hub.org>, pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
Cc: jeff@pgsql.com, pgsql-hackers@postgreSQL.org
In-Reply-To: <Pine.BSF.4.21.9912052011040.823-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:56 PM 05-12-1999 -0400, The Hermit Hacker wrote:

pages off of http://www.pgsql.com that will provide a cleaner means of
contribute financially towards having features implemented, as well as

How about a website where the public can stick in their credit card number
and donate directly to
1) Postgres Inc/Org (which then could pay out "salaries")
2) A particular Postgres project (if necessary).
3) A particular developer (if it won't be detrimental to team spirit).

And everyone knows how much is going where- logs of total donations,
donations per month, per project etc.

Developers could even donate to each other if they feel that someone is not
being compensated enough for whatever reason (not enough visibility).

Could also have a Thank you page for things like "Keep up the good work",
"Mucho gracias!", etc (criticism and bug reports should be kept to mailing
lists).

I suggested something like this to GNU org some time back, dunno if they
like it at all. Open Destination Donation for Open Source Software.

The main problem is getting the money into bank accounts. But I figure
Postgres Inc could accept the donations, handle the financial details (card
problems etc), and then distribute money/thanks to the projects/developers
accordingly, via cheques, money orders or whatever.

Good idea?

Link.

From bouncefilter Mon Dec 6 22:13:14 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA42785;
Mon, 6 Dec 1999 22:12:48 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA55304;
Mon, 6 Dec 1999 23:12:14 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 6 Dec 1999 23:12:08 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Lincoln Yeoh <lylyeoh@mecomb.com>
cc: pgsql-general@postgreSQL.org, jeff@pgsql.com, pgsql-hackers@postgreSQL.org
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
In-Reply-To: <3.0.5.32.19991207101333.00900430@pop.mecomb.po.my>
Message-ID: <Pine.BSF.4.21.9912062257040.18029-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'm glad we are all thinking alike :)

1. don't like that one...that's what we do the support contracts,
consulting and database hosting for...and the merchandise. the
merchandise has the added benefit of providing advertising for the
project too, so everyone wins.

we are looking into expanding the product line also, currently talking
with our supplier on this...

IMHO, I'd rather have ppl sign up for support contracts and use them,
then just having "donations" flow in...its what we formed PostgreSQL,
Inc to do...

2. see http://www.pgsql.com/features ... its a start, we will expand on it
over the next few days, add a cgi backend, etc etc...

3. I feel that this one ties directly into 2...pick a feature taht that
developer has taken on according to the TODO list...

On Tue, 7 Dec 1999, Lincoln Yeoh wrote:

At 08:56 PM 05-12-1999 -0400, The Hermit Hacker wrote:

pages off of http://www.pgsql.com that will provide a cleaner means of
contribute financially towards having features implemented, as well as

How about a website where the public can stick in their credit card number
and donate directly to
1) Postgres Inc/Org (which then could pay out "salaries")
2) A particular Postgres project (if necessary).
3) A particular developer (if it won't be detrimental to team spirit).

And everyone knows how much is going where- logs of total donations,
donations per month, per project etc.

Developers could even donate to each other if they feel that someone is not
being compensated enough for whatever reason (not enough visibility).

Could also have a Thank you page for things like "Keep up the good work",
"Mucho gracias!", etc (criticism and bug reports should be kept to mailing
lists).

A comments page? Lincoln Yech <lylyech@mecomb.com> says this about
PostreSQL...? Doable, let me play with it...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Dec 6 22:34:14 1999
Received: from smtp.tiscalinet.it (fornax.tiscalinet.it [195.130.224.67])
by hub.org (8.9.3/8.9.3) with SMTP id WAA46770
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 22:33:39 -0500 (EST)
(envelope-from mrsanna@tiscalinet.it)
Received: (qmail 19729 invoked by uid 7770); 7 Dec 1999 03:33:08 -0000
Received: from unknown (HELO msan) (postfix@62.11.155.244)
by fornax.tiscalinet.it with SMTP; 7 Dec 1999 03:33:08 -0000
Received: from tiscalinet.it (unknown [127.0.0.1])
by msan (Postfix) with ESMTP id AC8552480F
for <pgsql-general@postgreSQL.org>;
Tue, 7 Dec 1999 05:05:52 +0100 (CET)
Sender: mrsanna@tiscalinet.it
Message-ID: <384C879F.11335423@tiscalinet.it>
Date: Tue, 07 Dec 1999 05:05:51 +0100
From: Mauro Sanna <mrsanna@tiscalinet.it>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.3 i586)
X-Accept-Language: it, en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

subscribe
end

From bouncefilter Mon Dec 6 22:40:14 1999
Received: from smtp.tiscalinet.it (fornax.tiscalinet.it [195.130.224.67])
by hub.org (8.9.3/8.9.3) with SMTP id WAA47895
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 22:39:43 -0500 (EST)
(envelope-from mrsanna@tiscalinet.it)
Received: (qmail 19832 invoked by uid 7770); 7 Dec 1999 03:39:12 -0000
Received: from unknown (HELO msan) (postfix@62.11.155.244)
by fornax.tiscalinet.it with SMTP; 7 Dec 1999 03:39:12 -0000
Received: from tiscalinet.it (localhost [127.0.0.1])
by msan (Postfix) with ESMTP id 2EFF12480F
for <pgsql-general@postgreSQL.org>;
Tue, 7 Dec 1999 05:12:46 +0100 (CET)
Sender: mrsanna@tiscalinet.it
Message-ID: <384C893A.1CE3EB5E@tiscalinet.it>
Date: Tue, 07 Dec 1999 05:12:42 +0100
From: Mauro Sanna <mrsanna@tiscalinet.it>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.3 i586)
X-Accept-Language: it, en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: I need a help.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi.
How can I insert a string like this CALLADA' with the apostrophe, in a
varchar field?
Thanks.

From bouncefilter Mon Dec 6 22:41:14 1999
Received: from smtp.tiscalinet.it (fornax.tiscalinet.it [195.130.224.67])
by hub.org (8.9.3/8.9.3) with SMTP id WAA48291
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 22:40:44 -0500 (EST)
(envelope-from mrsanna@tiscalinet.it)
Received: (qmail 19855 invoked by uid 7770); 7 Dec 1999 03:40:13 -0000
Received: from unknown (HELO msan) (postfix@62.11.155.244)
by fornax.tiscalinet.it with SMTP; 7 Dec 1999 03:40:13 -0000
Received: from tiscalinet.it (localhost [127.0.0.1])
by msan (Postfix) with ESMTP id 51B4C2480F
for <pgsql-general@postgreSQL.org>;
Tue, 7 Dec 1999 05:13:49 +0100 (CET)
Sender: mrsanna@tiscalinet.it
Message-ID: <384C897D.F868044C@tiscalinet.it>
Date: Tue, 07 Dec 1999 05:13:49 +0100
From: Mauro Sanna <mrsanna@tiscalinet.it>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.3 i586)
X-Accept-Language: it, en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
References: <199912070334.WAA46847@hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

From bouncefilter Mon Dec 6 22:44:14 1999
Received: from xavier.cc.xu.edu.ph (ian@xavier.cc.xu.edu.ph [165.220.40.15])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA48665;
Mon, 6 Dec 1999 22:43:46 -0500 (EST)
(envelope-from ian@xavier.cc.xu.edu.ph)
Received: from localhost (ian@localhost)
by xavier.cc.xu.edu.ph (8.8.6/8.8.6) with SMTP id MAA10114;
Tue, 7 Dec 1999 12:16:20 +0800
Date: Tue, 7 Dec 1999 12:16:20 +0800 (PST)
From: Chris Ian Capon Fiel <ian@xavier.cc.xu.edu.ph>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: Vadim Mikheev <vadim@krs.ru>, Mike Mascari <mascarm@mascari.com>,
Lamar Owen <lamar.owen@wgcr.org>, Tom Lane <tgl@sss.pgh.pa.us>,
Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgresql.org,
PostgreSQL Developers List <hackers@postgresql.org>
Subject: Postgresql in win9x
In-Reply-To: <199911291910.OAA29896@candle.pha.pa.us>
Message-ID: <Pine.LNX.3.96.991207121520.10054B-100000@xavier.cc.xu.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

is there a PostgreSQL in win98 or win95?

From bouncefilter Mon Dec 6 23:27:19 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA56781
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 23:26:59 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id MAA28166;
Tue, 7 Dec 1999 12:26:41 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma028164; Tue, 7 Dec 99 12:26:35 +0800
Message-Id: <3.0.5.32.19991207122703.008d3100@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 07 Dec 1999 12:27:03 +0800
To: The Hermit Hacker <scrappy@hub.org>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
Cc: pgsql-general@postgreSQL.org, jeff@pgsql.com
In-Reply-To: <Pine.BSF.4.21.9912062257040.18029-100000@thelab.hub.org>
References: <3.0.5.32.19991207101333.00900430@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:12 PM 06-12-1999 -0400, The Hermit Hacker wrote:

I'm glad we are all thinking alike :)

Yep. I really would like a credit card thingy tho, coz it's more convenient
than trying to do international bank transfers, money orders and all that.

There's a bit of pain interfacing with the bank/card clearinghouse though.

On Tue, 7 Dec 1999, Lincoln Yeoh wrote:

At 08:56 PM 05-12-1999 -0400, The Hermit Hacker wrote:

pages off of http://www.pgsql.com that will provide a cleaner means of
contribute financially towards having features implemented, as well as

How about a website where the public can stick in their credit card number
and donate directly to
1) Postgres Inc/Org (which then could pay out "salaries")
2) A particular Postgres project (if necessary).
3) A particular developer (if it won't be detrimental to team spirit).

1. don't like that one...that's what we do the support contracts,

OK. Was just an idea for general funding.

2. see http://www.pgsql.com/features ... its a start, we will expand on it
over the next few days, add a cgi backend, etc etc...

Looks ok, heh maybe some bright spark will put a pledge for negative bucks
for stuff they don't like :).

I still would like support for credit card payments..

3. I feel that this one ties directly into 2...pick a feature taht that
developer has taken on according to the TODO list...

Yeah, probably better for teamwork/teamspirit..

Could also have a Thank you page for things like "Keep up the good work",
"Mucho gracias!", etc (criticism and bug reports should be kept to mailing
lists).

A comments page? Lincoln Yech <lylyech@mecomb.com> says this about
PostreSQL...? Doable, let me play with it...

More like a way of saying "Thanks" to the developers. I figure many times a
sincere word of thanks/encouragement at the right moment is priceless.
Problem is there could be abuses by nasty people.

The comments could actually be added to your existing projects page perhaps.

BTW the Postgres elephant doesn't look quite as attractive as the Linux
penguin.

That said, it could still make a decent stuffed toy. Give it big eyes and a
PostgreSQL t-shirt around a roly-poly body.

Thing is at current exchange rates, I can get cute stuffed toys for only
USD2 here. USD20 is like 20 lunches... Got to save up...

Cheerio,

Link.

From bouncefilter Mon Dec 6 23:45:48 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA60020
for <pgsql-general@postgreSQL.org>; Mon, 6 Dec 1999 23:44:26 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA56084;
Tue, 7 Dec 1999 00:44:10 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 7 Dec 1999 00:44:10 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Lincoln Yeoh <lylyeoh@mecomb.com>
cc: pgsql-general@postgreSQL.org, jeff@pgsql.com
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
In-Reply-To: <3.0.5.32.19991207122703.008d3100@pop.mecomb.po.my>
Message-ID: <Pine.BSF.4.21.9912070038490.823-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 7 Dec 1999, Lincoln Yeoh wrote:

At 11:12 PM 06-12-1999 -0400, The Hermit Hacker wrote:

I'm glad we are all thinking alike :)

Yep. I really would like a credit card thingy tho, coz it's more
convenient than trying to do international bank transfers, money
orders and all that.

There's a bit of pain interfacing with the bank/card clearinghouse
though.

We do do credit cards...let me build the backend for that page first...it
will include the ability to do credit cards. Our products page currently
does handle credit cards, but i haven't had a chance to build up the cgi
yet for the 'pledge' page...

1. don't like that one...that's what we do the support contracts,

OK. Was just an idea for general funding.

There is a 'General Pool' option under the Contribute item in the products
page...I'm going to end up throwing in an 'Advertising' option also, for
magazine ads and such...

2. see http://www.pgsql.com/features ... its a start, we will expand on it
over the next few days, add a cgi backend, etc etc...

Looks ok, heh maybe some bright spark will put a pledge for negative bucks
for stuff they don't like :).

I still would like support for credit card payments..

Go make an order on he products page...ti will ask you for your credit
card number...the pledge page will have it too...i'll try hard to get it
in place tomorrow...

Could also have a Thank you page for things like "Keep up the good work",
"Mucho gracias!", etc (criticism and bug reports should be kept to mailing
lists).

A comments page? Lincoln Yech <lylyech@mecomb.com> says this about
PostreSQL...? Doable, let me play with it...

More like a way of saying "Thanks" to the developers. I figure many times a
sincere word of thanks/encouragement at the right moment is priceless.
Problem is there could be abuses by nasty people.

The comments could actually be added to your existing projects page perhaps.

BTW the Postgres elephant doesn't look quite as attractive as the Linux
penguin.

That said, it could still make a decent stuffed toy. Give it big eyes and a
PostgreSQL t-shirt around a roly-poly body.

Jeff? :)

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Tue Dec 7 07:47:37 1999
Received: from arantxa.ii.uam.es (arantxa.ii.uam.es [150.244.56.15])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA24866
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 07:46:50 -0500 (EST)
(envelope-from Rosa.Carro@ii.uam.es)
From: Rosa.Carro@ii.uam.es
Received: from minerva.ii.uam.es (minerva [150.244.56.39])
by arantxa.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id NAA03564
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 13:47:37 GMT
Received: from helena (helena [150.244.56.48])
by minerva.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id NAA02746
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 13:40:36 +0100 (MET)
Message-ID: <384D02D3.92BA3BB5@ii.uam.es>
Date: Tue, 07 Dec 1999 13:51:32 +0100
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: (no subject)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

subscribe pgsql-general

From bouncefilter Tue Dec 7 07:49:37 1999
Received: from arantxa.ii.uam.es (arantxa.ii.uam.es [150.244.56.15])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA25005
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 07:48:52 -0500 (EST)
(envelope-from Rosa.Carro@ii.uam.es)
From: Rosa.Carro@ii.uam.es
Received: from minerva.ii.uam.es (minerva [150.244.56.39])
by arantxa.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id NAA03578
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 13:49:42 GMT
Received: from helena (helena [150.244.56.48])
by minerva.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id NAA02845
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 13:42:40 +0100 (MET)
Message-ID: <384D0350.4EBE1283@ii.uam.es>
Date: Tue, 07 Dec 1999 13:53:36 +0100
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Urgent help: User variables
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello everybody,

I am using PostgresSQL in Linux, and I want to declare a user variable so that I can use its value
for new queries after giving it a value.

While using WinNT and SQL Server I was writting (for example ):

declare @@task_id int
selct @@task_id = id from task were name ='Mytask'
update task set final='N' where id = @@task_id

But when I write these sentences in Postgres for Linux (I am using RedHat 6.0), I am told:

"ERROR: parser: parse error at or near @@"

How can I do the same?

Thank you very much,

Rosa

--------------------------------------
Rosa Maria Carro Salas
E.T.S.Informatica
Universidad Autonoma de Madrid
Cantoblanco 28049, Madrid (Spain)
phone: +34 1 348 2291

From bouncefilter Tue Dec 7 08:01:37 1999
Received: from ns.prov-liege.be (ns.prov-liege.be [193.190.122.12])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA26628;
Tue, 7 Dec 1999 08:00:39 -0500 (EST)
(envelope-from Fabian.Frederick@prov-liege.be)
From: Fabian.Frederick@prov-liege.be
Received: by ns.prov-liege.be; (8.8.8/1.3/10May95) id NAA19403;
Tue, 7 Dec 1999 13:49:57 +0100 (GMT+0100)
Received: by mesepl.epl.prov-liege.be with Internet Mail Service (5.5.1960.3)
id <YNVMFRDW>; Tue, 7 Dec 1999 13:53:40 +0100
Message-ID: <17AB709C82E5D111ACF20000F805F4532B41FE@mesadm.epl.prov-liege.be>
To: ian@xavier.cc.xu.edu.ph, pgman@candle.pha.pa.us
Cc: vadim@krs.ru, mascarm@mascari.com, lamar.owen@wgcr.org, tgl@sss.pgh.pa.us,
lylyeoh@mecomb.com, pgsql-general@postgreSQL.org, hackers@postgreSQL.org
Subject: RE: [GENERAL] Postgresql in win9x
Date: Tue, 7 Dec 1999 13:53:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

www.postgresql.org doesn't speak about any port so I imagine nothing
exist for now on that platform ; however you can release ODBC accesses.

Fabian
http://www.geocities.com/lonestar_teklords

From bouncefilter Tue Dec 7 10:35:39 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1] (may be
forged)) by hub.org (8.9.3/8.9.3) with ESMTP id KAA47571;
Tue, 7 Dec 1999 10:34:44 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id QAA03047;
Tue, 7 Dec 1999 16:33:25 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11vMjn-0000GG-00; Tue, 7 Dec 1999 15:41:11 +0000
Message-ID: <384D1D3B.2BF89CBB@sferacarta.com>
Date: Tue, 07 Dec 1999 15:44:12 +0100
From: jose soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: Nikolay Mijaylov <nmmm@nmmm.nu>
CC: pgsql-general <pgsql-general@postgresql.org>, pgsql-sql@postgresql.org
Subject: Re: [SQL] Fw: Whats happen here?
References: <002001bf3ffd$17309980$ce2a18c3@skillbrokers.bg>
Content-Type: multipart/alternative;
boundary="------------B22AAD1845D9DFF1D252D2A3"

--------------B22AAD1845D9DFF1D252D2A3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Try this:

drop function char_eq_varchar(bpchar,varchar);
create function char_eq_varchar(bpchar,varchar) returns bool as
'
declare
i2 text;
i1 text;
begin
i1:= trim($1);
i2:= $2;
if i1 = i2 then
return TRUE;
else
return FALSE;
end if;
end;
' language 'plpgsql';

drop operator = (bpchar,"varchar");
create operator = (
leftarg=bpchar,
rightarg="varchar",
procedure=char_eq_varchar,
commutator='=',
negator='<>',
restrict=eqsel,
join=eqjoinsel
);

drop table x;
drop table y;
create table x(a char(20));
create table y(a varchar(5));
insert into x values('a');
insert into y values('a');
select * from x, y where x.a = y.a;
a |a
--------------------+-
a |a
(1 row)

Jose'

Nikolay Mijaylov ha scritto:

Whats happen here?
-------------------------

root=> \dt
Database    = root
+------------------+----------------------------------+----------+
|  Owner           |             Relation             |   Type   |
+------------------+----------------------------------+----------+
| root             | x                                | table    |
| root             | y                                | table    |
+------------------+----------------------------------+----------+
root=> \d x
Table = x
+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | char() |
20 |

+----------------------------------+----------------------------------+-----

--+
root=> \d y

Table = y

+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | varchar() |
5 |

+----------------------------------+----------------------------------+-----

--+
root=>select * from x a, y b where a.a = b.a;
ERROR: There is more than one possible operator '=' for types 'bpchar'

and

'varchar'
You will have to retype this query using an explicit cast

root=> select * from x a, y b where text(a.a) = text(b.b);
ERROR: There is more than one possible operator '=' for types 'bpchar' and

'varchar'

You will have to retype this query using an explicit cast

--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

************

--------------B22AAD1845D9DFF1D252D2A3
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<tt>Try this:</tt><tt></tt>
<p><tt>drop function char_eq_varchar(bpchar,varchar);</tt>
<br><tt>create function char_eq_varchar(bpchar,varchar) returns bool as</tt>
<br><tt>'</tt>
<br><tt>declare</tt>
<br><tt> i2 text;</tt>
<br><tt> i1 text;</tt>
<br><tt>begin</tt>
<br><tt> i1:= trim($1);</tt>
<br><tt> i2:= $2;</tt>
<br><tt> if i1 = i2 then</tt>
<br><tt> return TRUE;</tt>
<br><tt> else</tt>
<br><tt> return FALSE;</tt>
<br><tt> end if;</tt>
<br><tt>end;</tt>
<br><tt>' language 'plpgsql';</tt>
<br><tt></tt> <tt></tt>
<p><tt>drop operator = (bpchar,"varchar");</tt>
<br><tt>create operator = (</tt>
<br><tt>        leftarg=bpchar,</tt>
<br><tt>        rightarg="varchar",</tt>
<br><tt>        procedure=char_eq_varchar,</tt>
<br><tt>        commutator='=',</tt>
<br><tt>        negator='<>',</tt>
<br><tt>        restrict=eqsel,</tt>
<br><tt>        join=eqjoinsel</tt>
<br><tt>        );</tt><tt></tt>
<p><tt>drop table x;</tt>
<br><tt>drop table y;</tt>
<br><tt>create table x(a char(20));</tt>
<br><tt>create table y(a varchar(5));</tt>
<br><tt>insert into x values('a');</tt>
<br><tt>insert into y values('a');</tt>
<br><tt>select * from x, y where x.a = y.a;</tt>
<br><tt>a                  
|a</tt>
<br><tt>--------------------+-</tt>
<br><tt>a                  
|a</tt>
<br><tt>(1 row)</tt>
<br><tt></tt> 
<p>Jose'
<br> 
<p>Nikolay Mijaylov ha scritto:
<blockquote TYPE=CITE>> Whats happen here?
<br>> -------------------------
<br>>
<br>> root=> \dt
<br>>
<br>> Database    = root
<br>>  +------------------+----------------------------------+----------+
<br>>  |  Owner          
|            
Relation            
|   Type   |
<br>>  +------------------+----------------------------------+----------+
<br>>  | root            
| x                               
| table    |
<br>>  | root            
| y                               
| table    |
<br>>  +------------------+----------------------------------+----------+
<br>> root=> \d x
<br>>
<br>> Table    = x
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> |             
Field              
|             
Type               
|
<br>> Length|
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> | a                               
| char()                          
|
<br>> 20 |
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> root=> \d y
<br>>
<br>> Table    = y
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> |             
Field              
|             
Type               
|
<br>> Length|
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> | a                               
| varchar()                       
|
<br>> 5 |
<br>>
<br>+----------------------------------+----------------------------------+-----
<br>> --+
<br>> root=>select * from x a, y b where a.a = b.a;
<br>> ERROR:  There is more than one possible operator '=' for types
'bpchar'
<br>and
<br>> 'varchar'
<br>>         You will have to
retype this query using an explicit cast
<br>>
<br>>
<br>>
<br>> root=> select * from x a, y b where text(a.a) = text(b.b);
<br>>ERROR:  There is more than one possible operator '=' for types
'bpchar' and
<br>'varchar'
<br>>        You will have to retype
this query using an explicit cast
<br>>
<br>> --------------------------------------------------------------
<br>> The reboots are for hardware upgrades!
<br>> "<a href="http://www.nmmm.nu">http://www.nmmm.nu</a>; <nmmm@nmmm.nu>
<br>>
<br>>
<p>************</blockquote>
</html>

--------------B22AAD1845D9DFF1D252D2A3--

From bouncefilter Tue Dec 7 11:57:56 1999
Received: from drillich.uniserve.de (drillich.uniserve.de [195.27.4.3])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA63208
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 11:57:36 -0500 (EST)
(envelope-from drillich@uniserve.de)
Received: from uniserve.de (localhost [127.0.0.1])
by drillich.uniserve.de (8.9.3/8.8.8) with ESMTP id RAA18498
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 17:57:54 +0100
Sender: drillich@drillich.uniserve.de
Message-ID: <384D3C92.D0FA629D@uniserve.de>
Date: Tue, 07 Dec 1999 17:57:54 +0100
From: Thomas Drillich <drillich@uniserve.de>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686)
X-Accept-Language: de-DE, en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: no primary key on self designed type
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

create type inrecord (
internallength=VARIABLE,
input=inr_in,
output=inr_out
);

create table test (
data inrecord not null primary key
);
... result ...
ERROR: Can't find a default operator class for type 268128.

how can I define the default operator class ??
--
mit freundlichem Gruss -- regards
,-,
| | Thomas Drillich <drillich@uniserve.de>
___|__|
(___, ) uniserve Internet & Multimedia GmbH
(___, )\ Sophienweg 3
(___, ) \ Technologiezentrum (MIT)
(___,_,)/ \ D-59872 Meschede Germany
\ fon: +49 291 59100 , fax: +49 291 59102

From bouncefilter Tue Dec 7 12:32:55 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id MAA68964
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 12:32:01 -0500 (EST)
(envelope-from szi@khs-ag.de)
Received: (qmail 30622 invoked from network); 7 Dec 1999 17:14:37 -0000
Received: from intra.do.khs-ag.de (HELO intra.do.khs-ag.de.khs-ag.de)
(10.133.122.3)
by intra.do.khs-ag.de with SMTP; 7 Dec 1999 17:14:37 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: Where is IFNULL?
From: Sascha Ziemann <szi@khs-ag.de>
Date: 07 Dec 1999 18:14:36 +0100
Message-ID: <m3u2luekqr.fsf@intra.do.khs-ag.de>
Lines: 14
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hi,

the user manual describes the function IFNULL on page 38, but when I
try to use it I get the following error:

users=> select ifnull (NULL, 'nix');
ERROR: No such function 'ifnull' with the specified attributes

What do I have to do to get the function?

Or does anybody know a simple way to concatenate strings, which can be
NULL?

Sascha

From bouncefilter Tue Dec 7 12:49:55 1999
Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA72077;
Tue, 7 Dec 1999 12:49:13 -0500 (EST)
(envelope-from rison@biochemistry.ucl.ac.uk)
Received: from biochem.ucl.ac.uk (actually host bsmori1.biochem.ucl.ac.uk)
by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP;
Tue, 7 Dec 1999 17:48:46 +0000
Received: from bsmlx17.biochem.ucl.ac.uk (bsmlx17 [128.40.46.142]) by
biochem.ucl.ac.uk (8.9.2/8.9.1)
with ESMTP id RAA06694; Tue, 7 Dec 1999 17:48:59 GMT
Received: from localhost (rison@localhost)
by bsmlx17.biochem.ucl.ac.uk (8.9.3/8.6.6) with ESMTP id RAA01672;
Tue, 7 Dec 1999 17:57:30 GMT
X-Authentication-Warning: bsmlx17.biochem.ucl.ac.uk: rison owned process doing
-bs
Date: Tue, 7 Dec 1999 17:57:30 +0000 (GMT)
From: Stuart Rison <rison@biochemistry.ucl.ac.uk>
X-Sender: rison@bsmlx17
To: jose soares <jose@sferacarta.com>
cc: Nikolay Mijaylov <nmmm@nmmm.nu>,
pgsql-general <pgsql-general@postgreSQL.org>, pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Fw: Whats happen here?
In-Reply-To: <384D1D3B.2BF89CBB@sferacarta.com>
Message-ID: <Pine.LNX.4.10.9912071753340.1210-100000@bsmlx17>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hum, I wonder if it's necessary to create an operator?

I had a similar problem a while back, the failing operator was || the
concatenation operator, for exactly the same reason.

This is the answer I got from Ross Reedstrom (reedstrm@rice.edu) and it
worked a treat:

"> Stuart -

I think this is a consequence of the internal representations of text
and varchar and char being identical, so that the cast finctions think
there's nothing to do.
I think this is fixed in 6.5. A work around for 6.4 is to apply
afunction that does nothing to the text: I've used btrim() in the past
(since I usually want to get rid of trailing whitespace anyway:

test=> select btrim(chromosome) || btrim(arm) as locus from experiment;
locus
-----
22q
17p
(2 rows)"

This was PG 6.4 and perhaps things have changed but at least here you have
a 'generalised' solution for all operator between a bpchar and a varchar.

HTH,

Stuart.

On Tue, 7 Dec 1999, jose soares wrote:

Try this:

drop function char_eq_varchar(bpchar,varchar);
create function char_eq_varchar(bpchar,varchar) returns bool as
'
declare
i2 text;
i1 text;
begin
i1:= trim($1);
i2:= $2;
if i1 = i2 then
return TRUE;
else
return FALSE;
end if;
end;
' language 'plpgsql';

drop operator = (bpchar,"varchar");
create operator = (
leftarg=bpchar,
rightarg="varchar",
procedure=char_eq_varchar,
commutator='=',
negator='<>',
restrict=eqsel,
join=eqjoinsel
);

drop table x;
drop table y;
create table x(a char(20));
create table y(a varchar(5));
insert into x values('a');
insert into y values('a');
select * from x, y where x.a = y.a;
a |a
--------------------+-
a |a
(1 row)

Jose'

Nikolay Mijaylov ha scritto:
Whats happen here?
-------------------------

root=> \dt
Database    = root
+------------------+----------------------------------+----------+
|  Owner           |             Relation             |   Type   |
+------------------+----------------------------------+----------+
| root             | x                                | table    |
| root             | y                                | table    |
+------------------+----------------------------------+----------+
root=> \d x
Table = x
+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | char() |
20 |

+----------------------------------+----------------------------------+-----

--+
root=> \d y

Table = y

+----------------------------------+----------------------------------+-----

--+
| Field | Type |
Length|

+----------------------------------+----------------------------------+-----

--+
| a | varchar() |
5 |

+----------------------------------+----------------------------------+-----

--+
root=>select * from x a, y b where a.a = b.a;
ERROR: There is more than one possible operator '=' for types 'bpchar'

and

'varchar'
You will have to retype this query using an explicit cast

root=> select * from x a, y b where text(a.a) = text(b.b);
ERROR: There is more than one possible operator '=' for types 'bpchar' and

'varchar'

You will have to retype this query using an explicit cast

--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

************

From bouncefilter Tue Dec 7 14:08:56 1999
Received: from usc.edu (root@usc.edu [128.125.253.136])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA24365
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 14:08:21 -0500 (EST)
(envelope-from ymartin@usc.edu)
Received: from aludra.usc.edu (ymartin@aludra.usc.edu [128.125.19.184])
by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
id LAA09581 for <pgsql-general@postgreSQL.org>;
Tue, 7 Dec 1999 11:08:11 -0800 (PST)
Received: from localhost (ymartin@localhost)
by aludra.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
id LAA04697 for <pgsql-general@postgreSQL.org>;
Tue, 7 Dec 1999 11:08:11 -0800 (PST)
Date: Tue, 7 Dec 1999 11:07:55 -0800 (PST)
From: ymartin <ymartin@usc.edu>
To: pgsql-general@postgreSQL.org
Subject: help
Message-ID: <Pine.GSO.4.10.9912071107110.3762-100000@aludra.usc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello
I am a student and I need help on writing some queries.... Please
let me know if you can help...

Thanks
ymartin

From bouncefilter Tue Dec 7 15:50:07 1999
Received: from mail.xnet.com (quake.xnet.com [198.147.221.67])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA50174
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 15:49:49 -0500 (EST)
(envelope-from selkovjr@selkovjr.xnet.com)
Received: from selkovjr.xnet.com ([204.248.57.203]) by mail.xnet.com
(8.9.3+Sun/XNet-3.0R) with ESMTP id OAA22473;
Tue, 7 Dec 1999 14:49:21 -0600 (CST)
Message-Id: <199912072049.OAA22473@mail.xnet.com>
To: Thomas Drillich <drillich@uniserve.de>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] no primary key on self designed type
In-Reply-To: Your message of "Tue, 07 Dec 1999 17:57:54 +0100."
<384D3C92.D0FA629D@uniserve.de>
Date: Tue, 07 Dec 1999 14:57:48 -0600
From: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>

Hello,

create type inrecord (
internallength=VARIABLE,
input=inr_in,
output=inr_out
);

create table test (
data inrecord not null primary key
);
... result ...
ERROR: Can't find a default operator class for type 268128.

how can I define the default operator class ??
--

The short answer is,

INSERT INTO pg_opclass (opcname, opcdeftype)
SELECT 'inrecord_ops', oid
FROM pg_type
WHERE typname = 'inrecord';

But you won't get away with just that. You probably want a non-empty
opclass. For example, if your type, inrecord, needs a btree opclass,
you'll want to do:

SELECT o.oid AS opoid, o.oprname
INTO TABLE inrecord_ops_tmp
FROM pg_operator o, pg_type t
WHERE o.oprleft = t.oid and o.oprright = t.oid
and t.typname = 'inrecord';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 1,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '<';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 2,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '<=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 3,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 4,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '>=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 5,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '>';

DROP table inrecord_ops_tmp;

Which isn't all yet. The code above assumes that you have defined the
operators, '=', '>=', etc.:

CREATE OPERATOR = (
leftarg = inrecord, rightarg = inrecord_code, procedure = inrecord_eq,
restrict = eqsel, join = eqjoinsel
);

If that didn't make you sick already, you also need to define the
procedures, such as inrecord_eq in this example, and possibly write
some c code for them:

CREATE FUNCTION inrecord_eq(inrecord, inrecord) RETURNS bool
AS '${LIBDIR}/inrecord.so' LANGUAGE 'c';

INSERT INTO pg_description (objoid, description)
SELECT oid, 'equals'::text
FROM pg_proc
WHERE proname = 'inrecord_eq'::name;

Thar's, in short, what is required to build a completely new type. One
might as well attempt to borrow some code or the whole opclass from
existing similar types, but I would hesitate to even consider doing that
without the thorough knowledge of the current postgres schema, which
is unfortunately not yet covered by the contemporary docs.

--Gene

From bouncefilter Tue Dec 7 16:03:07 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA51595;
Tue, 7 Dec 1999 16:02:04 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.8.7/8.8.5) with ESMTP id QAA15509;
Tue, 7 Dec 1999 16:00:48 -0500
Message-ID: <384D7577.D4C80586@wgcr.org>
Date: Tue, 07 Dec 1999 16:00:39 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chris Ian Capon Fiel <ian@xavier.cc.xu.edu.ph>
CC: Bruce Momjian <pgman@candle.pha.pa.us>, Vadim Mikheev <vadim@krs.ru>,
Mike Mascari <mascarm@mascari.com>, Tom Lane <tgl@sss.pgh.pa.us>,
Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org,
PostgreSQL Developers List <hackers@postgreSQL.org>
Subject: Re: Postgresql in win9x
References: <Pine.LNX.3.96.991207121520.10054B-100000@xavier.cc.xu.edu.ph>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Ian Capon Fiel wrote:

is there a PostgreSQL in win98 or win95?

http://www.postgresql.org/docs/pgsql/doc/README.NT

The NT port will, AFAIK, run on any Win32 implementation, as long as you
have the Cygwin stuff loaded (talked about in the README.NT file....).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Tue Dec 7 16:17:07 1999
Received: from mercury.shreve.net (IDENT:root@mercury.shreve.net
[208.206.76.23]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA53483
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 16:16:51 -0500 (EST)
(envelope-from kheflin@shreve.net)
Received: from mercury.shreve.net (IDENT:kheflin@mercury.shreve.net
[208.206.76.23])
by mercury.shreve.net (8.9.3/8.9.3) with ESMTP id PAA26841
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 15:16:45 -0600
Date: Tue, 7 Dec 1999 15:16:45 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
To: "PGSQL-General (E-mail)" <pgsql-general@postgreSQL.org>
Subject: viewing dbs
Message-ID: <Pine.LNX.4.10.9912071514420.27925-100000@mercury.shreve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I use \l
to view a list of all the DBs in use on our server.
I'm not sure what order these are in, but is there a way to view all the
DBs in alphabetical order ?

Kevin

From bouncefilter Tue Dec 7 16:10:07 1999
Received: from mail.xnet.com (quake.xnet.com [198.147.221.67])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA52430
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 16:09:30 -0500 (EST)
(envelope-from selkovjr@selkovjr.xnet.com)
Received: from selkovjr.xnet.com ([204.248.57.203]) by mail.xnet.com
(8.9.3+Sun/XNet-3.0R) with ESMTP id PAA29174;
Tue, 7 Dec 1999 15:08:49 -0600 (CST)
Message-Id: <199912072108.PAA29174@mail.xnet.com>
To: Sascha Ziemann <szi@khs-ag.de>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Where is IFNULL?
In-Reply-To: Your message of "07 Dec 1999 18:14:36 +0100."
<m3u2luekqr.fsf@intra.do.khs-ag.de>
Date: Tue, 07 Dec 1999 15:17:16 -0600
From: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>

Hi,

the user manual describes the function IFNULL on page 38, but when I
try to use it I get the following error:

users=> select ifnull (NULL, 'nix');
ERROR: No such function 'ifnull' with the specified attributes

The manual seems to be obsolete. The related functions are named
nullvalue and nonnullvalue, but neither takes more than one argument.

Actually, there is a SQL syntactic sugar for null/not null:

diagrams=> select 1 is not null;
?column?
--------
t
(1 row)

diagrams=> select 1 is null;
?column?
--------
f
(1 row)

'1 is null' is equivalent to 'nullvalue(1)'

Or does anybody know a simple way to concatenate strings, which can be
NULL?

Don't know the answer to this, but it appears to be wrong not to
ignore NULLs in concatenation. Why not trust this job to your client-side
code?

--Gene

From bouncefilter Tue Dec 7 16:43:08 1999
Received: from mercury.shreve.net (IDENT:root@mercury.shreve.net
[208.206.76.23]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA57039
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 16:42:16 -0500 (EST)
(envelope-from kheflin@shreve.net)
Received: from mercury.shreve.net (IDENT:kheflin@mercury.shreve.net
[208.206.76.23])
by mercury.shreve.net (8.9.3/8.9.3) with ESMTP id PAA16120;
Tue, 7 Dec 1999 15:42:09 -0600
Date: Tue, 7 Dec 1999 15:42:09 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
To: kaiq@realtyideas.com
cc: "PGSQL-General (E-mail)" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] viewing dbs
In-Reply-To:
<Pine.LNX.4.10.9912071631510.27615-100000@picasso.realtyideas.com>
Message-ID: <Pine.LNX.4.10.9912071541400.27925-100000@mercury.shreve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 7 Dec 1999 kaiq@realtyideas.com wrote:

select * from pg_database order by datname;

thank you very much for that bit of info. Very helpful. I knew there had
to be something.

thanks again.

Kevin

On Tue, 7 Dec 1999, Kevin Heflin wrote:

I use \l
to view a list of all the DBs in use on our server.
I'm not sure what order these are in, but is there a way to view all the
DBs in alphabetical order ?

Kevin

--------------------------------------------------------------------
Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
VP/Production | 333 Texas St #175 | FAX:318.221.6612
kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
--------------------------------------------------------------------

************

From bouncefilter Tue Dec 7 17:02:08 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id RAA60363
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 17:02:05 -0500 (EST)
(envelope-from szi@khs-ag.de)
Received: (qmail 2130 invoked from network); 7 Dec 1999 21:44:38 -0000
Received: from intra.do.khs-ag.de (HELO intra.do.khs-ag.de.khs-ag.de)
(10.133.122.3)
by intra.do.khs-ag.de with SMTP; 7 Dec 1999 21:44:38 -0000
Sender: szi@intra.do.khs-ag.de
To: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Where is IFNULL?
References: <199912072108.PAA29174@mail.xnet.com>
From: Sascha Ziemann <szi@khs-ag.de>
Date: 07 Dec 1999 22:44:37 +0100
In-Reply-To: "Gene Selkov Jr."'s message of "Tue, 07 Dec 1999 15:17:16 -0600"
Message-ID: <m3ogc2e88q.fsf@intra.do.khs-ag.de>
Lines: 36
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>:

| > the user manual describes the function IFNULL on page 38, but when I
| > try to use it I get the following error:
| >
| > users=> select ifnull (NULL, 'nix');
| > ERROR: No such function 'ifnull' with the specified attributes
|
| The manual seems to be obsolete. The related functions are named
| nullvalue and nonnullvalue, but neither takes more than one argument.

IFNULL isn't syntactic suguar. It is like C's "1 ? 1 : 0".

| > Or does anybody know a simple way to concatenate strings, which can be
| > NULL?
|
| Don't know the answer to this, but it appears to be wrong not to
| ignore NULLs in concatenation.

That is the way Postgresql works:

users=> select 'tach' || NULL;
ERROR: parser: parse error at or near ";"

users=> create function cat (text,text) returns text as 'begin return $1 || $2; end;' language 'plpgsql';
CREATE
users=> select cat ('tach', NULL);
ERROR: typeidTypeRelid: Invalid type - oid = 0

| Why not trust this job to your client-side
| code?

Because I do not write that code and because my computer isn't
religious enough to trust anybody ;-)

Sascha

From bouncefilter Tue Dec 7 16:51:08 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id QAA58383
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 16:50:39 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Panter.DoCS.UU.SE (e99re41@Panter.DoCS.UU.SE [130.238.9.114])
by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP id WAA23533;
Tue, 7 Dec 1999 22:50:36 +0100
Received: from localhost (e99re41@localhost) by Panter.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id WAA03538; Tue, 7 Dec 1999 22:50:32 +0100
X-Authentication-Warning: Panter.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Tue, 7 Dec 1999 22:50:29 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: Kevin Heflin <kheflin@shreve.net>
cc: "PGSQL-General (E-mail)" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] viewing dbs
In-Reply-To: <Pine.LNX.4.10.9912071514420.27925-100000@mercury.shreve.net>
Message-ID: <Pine.GSO.4.02A.9912072249170.3057-100000@Panter.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

select * from pg_database order by datname;

I'm not sure why it's not ordered. That could perhaps be fixed.

On Tue, 7 Dec 1999, Kevin Heflin wrote:

I use \l
to view a list of all the DBs in use on our server.
I'm not sure what order these are in, but is there a way to view all the
DBs in alphabetical order ?

Kevin

--------------------------------------------------------------------
Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
VP/Production | 333 Texas St #175 | FAX:318.221.6612
kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
--------------------------------------------------------------------

************

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Dec 7 16:37:08 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA56380
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 16:36:14 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id QAA27620;
Tue, 7 Dec 1999 16:32:02 -0600
Date: Tue, 7 Dec 1999 16:32:02 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Kevin Heflin <kheflin@shreve.net>
cc: "PGSQL-General (E-mail)" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] viewing dbs
In-Reply-To: <Pine.LNX.4.10.9912071514420.27925-100000@mercury.shreve.net>
Message-ID: <Pine.LNX.4.10.9912071631510.27615-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

select * from pg_database order by datname;

On Tue, 7 Dec 1999, Kevin Heflin wrote:

I use \l
to view a list of all the DBs in use on our server.
I'm not sure what order these are in, but is there a way to view all the
DBs in alphabetical order ?

Kevin

--------------------------------------------------------------------
Kevin Heflin | ShreveNet, Inc. | Ph:318.222.2638 x103
VP/Production | 333 Texas St #175 | FAX:318.221.6612
kheflin@shreve.net | Shreveport, LA 71101 | http://www.shreve.net
--------------------------------------------------------------------

************

From bouncefilter Tue Dec 7 17:36:08 1999
Received: from bigiron.sopac.org.fj (bigiron.sopac.org.fj [202.62.0.150] (may
be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id RAA65016
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 17:35:28 -0500 (EST)
(envelope-from Franck@sopac.org.fj)
Received: by bigiron.sopac.org.fj with Internet Mail Service (5.5.2448.0)
id <Y1SKYKTN>; Wed, 8 Dec 1999 11:33:55 +1300
Message-ID: <F12ECEA0435AD211B5280008C7ACBC857FE779@bigiron.sopac.org.fj>
From: Franck Martin <Franck@sopac.org.fj>
To: pgsql-general@postgreSQL.org
Subject: ODBC Drivers for Win
Date: Wed, 8 Dec 1999 11:33:51 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
charset="iso-8859-1"

Sorry for such trivia, but where can I find Win9.x ODBC drivers to access
PostgreSQL running on Linux ?

Franck@sopac.org.fj

From bouncefilter Tue Dec 7 18:16:09 1999
Received: from rage.hub.org (root@nat202.25.mpoweredpc.net [142.177.202.25])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA70364
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 18:15:53 -0500 (EST)
(envelope-from jeffm@pgsql.com)
Received: from localhost (jeffm@localhost)
by rage.hub.org (8.9.3/8.9.3) with ESMTP id TAA47735;
Tue, 7 Dec 1999 19:15:40 -0400 (AST) (envelope-from jeffm@pgsql.com)
X-Authentication-Warning: rage.hub.org: jeffm owned process doing -bs
Date: Tue, 7 Dec 1999 19:15:40 -0400 (AST)
From: "Jeff MacDonald <jeff@pgsql.com>" <jeffm@pgsql.com>
X-Sender: jeffm@rage.hub.org
Reply-To: Jeff MacDonald <jeff@pgsql.com>
To: Lincoln Yeoh <lylyeoh@mecomb.com>
cc: The Hermit Hacker <scrappy@hub.org>, pgsql-general@postgreSQL.org,
jeff@pgsql.com
Subject: Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL?
In-Reply-To: <3.0.5.32.19991207122703.008d3100@pop.mecomb.po.my>
Message-ID: <Pine.BSF.4.10.9912071913240.13793-100000@rage.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

BTW the Postgres elephant doesn't look quite as attractive as the Linux
penguin.

that being said, the linun penguin isn't nearly as attractive as the freebsd
deemon , but don't get us started :)

That said, it could still make a decent stuffed toy. Give it big eyes and a
PostgreSQL t-shirt around a roly-poly body.

20usd is 30+cdn : for a stuffed toy ? we'll look into it.

on a side note we are looking into cofee mugs, keychains(alredy ordered)
and possibly mouse pads

jeff

From bouncefilter Tue Dec 7 19:12:11 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id TAA76738;
Tue, 7 Dec 1999 19:11:32 -0500 (EST) (envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "Sean Dolphin" <Sean@cadsusa.com>
X-Newsgroups: comp.databases.postgresql.patches,
comp.databases.postgresql.questions,
microsoft.public.sqlserver.misc, microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.programming,
microsoft.public.sqlserver.server
Subject: Memory bug
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.5600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600
Message-ID: <Imh34.20953$Tp.847209@typ11.nn.bcandid.com>
X-Trace: typ11.nn.bcandid.com 944611880 24.104.33.214 (Tue,
07 Dec 1999 19:11:20 EST)
Organization: bCandid - Powering the world's discussions - http://bCandid.com
Date: Tue, 7 Dec 1999 19:20:45 -0500
To: pgsql-patches@postgresql.org.pgsql-questions@postgresql.org

We are currently experiencing a problem with memory usage on our application
server. There is an application on our server that uses SQL Server to keep
track of data that is sent from our mainframe computer here. There are two
databases that are kept PPMDB and HISTDB. Both have the same structure, but
different time periods of updating. PPMDB is updated every 2 minutes, and
HISTDB is every 4 hours. The application that runs on the server connects
to the databases through the ODBC driver. Once that is done, it starts the
SQL engines, which take up a good amount of memory, 8 MB. The starting
point of memory ranges between 75 MB and 85 MB. The system is equipped with
320 MB of memory. What happens is that once the first update occurs SQL
Server uses up a large amount of memory, as said before, but it doesn't
relinquish the memory that it used to make the updates. And with each
update, SQL Server uses up a small amount of memory, but our main concern is
that somewhere down the road it will use up all of the memory on the serve.
The current version of SQL Server that we currently have is 7.0, with
Service Pack 1.0. Is this something that is supposed to happen, or is this
a major problem? I would be most thankful for any information anybody can
supply.

From bouncefilter Tue Dec 7 19:23:09 1999
Received: from fordfamilymarketing.com (jforddsl.wvi.com [204.245.255.187])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA80747
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 19:22:24 -0500 (EST)
(envelope-from stolkd@email.com)
Received: from email.com (localhost [127.0.0.1])
by fordfamilymarketing.com (8.9.3/8.9.3) with ESMTP id QAA04665
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 16:21:41 -0800
Sender: root@fordfamilymarketing.com
Message-ID: <384DA495.F8575ACB@email.com>
Date: Tue, 07 Dec 1999 16:21:41 -0800
From: Daniel Stolk <stolkd@email.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Increasing size of BLCKSZ
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I was wondering if somebody could tell me why the BLCKSZ of a page is so
small? Because this causes considerable waste of space since there is
going to be an empty slot at the end of each page that is too small to
be used. What would happen if I increased it to 32K?

Daniel Stolk

From bouncefilter Tue Dec 7 19:52:10 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA84667
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 19:51:19 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
TAA17942;
Tue, 7 Dec 1999 19:50:59 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912080050.TAA17942@candle.pha.pa.us>
Subject: Re: [GENERAL] Increasing size of BLCKSZ
In-Reply-To: <384DA495.F8575ACB@email.com> from Daniel Stolk at "Dec 7, 1999
04:21:41 pm"
To: Daniel Stolk <stolkd@email.com>
Date: Tue, 7 Dec 1999 19:50:59 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

I was wondering if somebody could tell me why the BLCKSZ of a page is so
small? Because this causes considerable waste of space since there is
going to be an empty slot at the end of each page that is too small to
be used. What would happen if I increased it to 32K?

It is the size of a usual disk file system block.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Dec 7 23:07:04 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA01991
for <pgsql-general@postgresql.org>; Tue, 7 Dec 1999 23:05:34 -0500 (EST)
(envelope-from kheflin@shreve.net)
Received: from mercury.shreve.net (root@mercury.shreve.net [208.206.76.23])
by trends.net (8.8.8/8.8.8) with ESMTP id UAA04056
for <pgsql-general@postgreSQL.org>; Tue, 7 Dec 1999 20:53:59 -0500 (EST)
Received: from mercury.shreve.net (IDENT:kheflin@mercury.shreve.net
[208.206.76.23])
by mercury.shreve.net (8.9.3/8.9.3) with ESMTP id TAA05524;
Tue, 7 Dec 1999 19:26:26 -0600
Date: Tue, 7 Dec 1999 19:26:26 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
To: Franck Martin <Franck@sopac.org.fj>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] ODBC Drivers for Win
In-Reply-To: <F12ECEA0435AD211B5280008C7ACBC857FE779@bigiron.sopac.org.fj>
Message-ID: <Pine.LNX.4.10.9912071924420.4039-100000@mercury.shreve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 8 Dec 1999, Franck Martin wrote:

Sorry for such trivia, but where can I find Win9.x ODBC drivers to access
PostgreSQL running on Linux ?

They do exist, and if you can't find them online somewhere, I do have a
copy for the installer at my office.

It allows me to create ODBC data sources on my WinNT boxes. And I've used
Tango files running with IIS to access postgresql running on our Linux
server.

The driver has options for postgres 6.3 and 6.4, but I've been using with
postgres 6.5x for awhile without problems so far.

Kevin

From bouncefilter Wed Dec 8 02:31:16 1999
Received: (from news@localhost) by hub.org (8.9.3/8.9.3) id CAA17377;
Wed, 8 Dec 1999 02:31:02 -0500 (EST) (envelope-from news)
X-Authentication-Warning: hub.org: news set sender to <news> using -f
From: "Bob Pfeiff" <bobp@spectrumtech.com>
References: <Imh34.20953$Tp.847209@typ11.nn.bcandid.com>
Subject: Re: Memory bug
Date: Tue, 7 Dec 1999 20:56:10 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <#JZwP7RQ$GA.299@cppssbbsa04>
X-Newsgroups: comp.databases.postgresql.patches,
comp.databases.postgresql.questions,
microsoft.public.sqlserver.misc, microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.programming,
microsoft.public.sqlserver.server
Lines: 18
To: pgsql-patches@postgresql.org.pgsql-questions@postgresql.org

The SQL Server will cache data and query plans and maintain them in cache
for performance reasons. There are memory management processes in SQL
Server to decide when to clear items from cache based on aging and on other
memory requirements on the system. Unless you're processes are doing
operations like loading an entire large table in cache (e.g., select * from
somebigtable), I wouldn't expect it to dominate the server's memory.

There is a configuration option to set the maximum amount of system memory
that SQL Server will use, but you shouldn't have to set it unless the SQL
Server is regularly monopolizing memory resources at the expense of other
applications or the OS.
--
Bob Pfeiff
MCDBA, MCSD, MCSE, MCT, SQL Server MVP
Practice Leader, Data Management
CIBER, Washington, DC

From bouncefilter Wed Dec 8 06:49:18 1999
Received: from hotmail.com (law-f314.hotmail.com [209.185.131.18])
by hub.org (8.9.3/8.9.3) with SMTP id GAA54230
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 06:48:24 -0500 (EST)
(envelope-from mssmx@hotmail.com)
Received: (qmail 19392 invoked by uid 0); 8 Dec 1999 11:47:53 -0000
Message-ID: <19991208114753.19391.qmail@hotmail.com>
Received: from 158.195.16.233 by www.hotmail.com with HTTP;
Wed, 08 Dec 1999 03:47:53 PST
X-Originating-IP: [158.195.16.233]
From: "Martin Stanek" <mssmx@hotmail.com>
To: pgsql-general@postgresql.org
Subject: foreign key
Date: Wed, 08 Dec 1999 03:47:53 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Are there any plans for supporting FOREIGN KEY
constraint (directly, i.e. no special triggers)
in following versions of PostgreSQL?

Thank you...

Martin

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

From bouncefilter Wed Dec 8 03:45:16 1999
Received: from r2d2.email.com.ph ([203.176.3.199])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA30553
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 03:43:47 -0500 (EST)
(envelope-from neil@email.com.ph)
Received: from localhost (neil@localhost)
by r2d2.emc.com.ph (8.9.3/8.9.3) with ESMTP id QAA11040
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 16:44:41 +0800
X-Authentication-Warning: r2d2.emc.com.ph: neil owned process doing -bs
Date: Wed, 8 Dec 1999 16:44:41 +0800 (PHT)
From: "neil d. quiogue" <neil@email.com.ph>
X-Sender: neil@r2d2.emc.com.ph
To: pgsql-general@postgresql.org
Subject: REPLICATION
Message-ID: <Pine.LNX.4.10.9912081642150.11038-100000@r2d2.emc.com.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Greetings,

Last February 1999, there had been some interesting discussions on data
replication. What is the current update on this? Is there a replication
agent in the making? Or is there a separate module/application that is
open source/free?

Any help would be great.

Regards,

Neil D. Quiogue

From bouncefilter Wed Dec 8 04:23:16 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA35934
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 04:22:33 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id RAA11769
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 17:22:26 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma011763; Wed, 8 Dec 99 17:22:05 +0800
Message-Id: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Wed, 08 Dec 1999 17:22:43 +0800
To: pgsql-general@postgreSQL.org
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
In-Reply-To: <384DA495.F8575ACB@email.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hi,

Say I have a transaction which goes like this:

begin;
insert into stuff;
do some nondatabase things based on last inserted id;
update a date in stuff;
commit;

It seems that if the date is out of the database range, everything is
thrown out. Is it possible to catch the database error and use a null date
instead, without throwing everything away?

Right now I only have two ways of proceeding:
1) commit before trying to update the date. And if things still don't work
- database has some non date related error, try to delete the previously
inserted stuff.
2) Make sure the dates are nice before trying to stick them in.

Unless there are I'll have to do 2).

Inserting stuff like
'27 Oct 19999 18:21:00 +0800' causes errors even though datetime supposedly
handles dates up to 1465001 AD.

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

Thanks,

Link.

From bouncefilter Wed Dec 8 10:18:42 1999
Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA01622
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 10:17:49 -0500 (EST)
(envelope-from davidb@vectormath.com)
From: davidb@vectormath.com
Received: from bullwinkle (adsl-204-1-67-149.indi.se.verio.net [204.1.67.149])
by sakaki.communique.net (8.8.8/8.8.8) with SMTP id JAA27742;
Wed, 8 Dec 1999 09:15:37 -0600 (CST)
Message-ID: <004b01bf418f$2163ca60$0402010a@bullwinkle.Radix>
To: "Franck Martin" <Franck@sopac.org.fj>, <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] ODBC Drivers for Win
Date: Wed, 8 Dec 1999 09:13:11 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

http://www.insightdist.com/download/psqlodbc_download.html

-----Original Message-----
From: Franck Martin <Franck@sopac.org.fj>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Date: Tuesday, December 07, 1999 4:48 PM
Subject: [GENERAL] ODBC Drivers for Win

Sorry for such trivia, but where can I find Win9.x ODBC drivers to access
PostgreSQL running on Linux ?

Franck@sopac.org.fj

************

From bouncefilter Wed Dec 8 13:04:39 1999
Received: from castle-smtp (firewall-user@ns2.amgen.com [138.133.17.7])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA18373
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 13:04:27 -0500 (EST)
(envelope-from mdalphin@amgen.com)
Received: by castle-smtp; id KAA27167; Wed, 8 Dec 1999 10:05:01 -0800 (PST)
Received: from mailbag.amgen.com(138.133.10.78) by castle-smtp.amgen.com via
smap (V4.2) id xma026776; Wed, 8 Dec 99 10:02:41 -0800
Received: from maat.amgen.com (maat [138.133.145.25])
by mailbag.amgen.com (8.8.5/8.8.5) with ESMTP id KAA13930
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 10:02:02 -0800 (PST)
Received: from amgen.com (mahunui [138.133.147.23])
by maat.amgen.com (8.8.8+Sun/8.8.8) with ESMTP id KAA00034
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 10:01:59 -0800 (PST)
Sender: mdalphin@amgen.com
Message-ID: <384E9D82.CCC45186@amgen.com>
Date: Wed, 08 Dec 1999 10:03:46 -0800
From: Mark Dalphin <mdalphin@amgen.com>
Organization: Amgen, Inc.
X-Mailer: Mozilla 4.6C-SGI [en] (X11; U; IRIX64 6.5 IP30)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Suggested "minor" change to psql
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Ever since I began working with Postgres, I have had one little irritating
problem with psql. It may be that I am mis-using this program; if so, my
suggestion is not helpful, however, if others have encountered this problem,
perhaps the developers can look at a fix for 7.0?

When I develop a new DB schema using psql, I usually first create a file, say
"mySchema.sql". I then "createdb" the database, start up psql, and use the
command "\i mySchema.sql" to load in my new schema. There will be, needless to
say, several errors. These fall nicely below the offending line and I can look
at fixing them. I drop the DB, re-edit my SQL file and re-do the "\i" command.

Sometimes, however, rather than using the "\i" command, I would like to simply
load my schema directly into psql and capture the output on STDOUT (ie "psql <
mySchema.sql >& myOutput"). The problem that arises is that the errors and
notices all come out on STDERR. I am not sure this is the right choice. Because
of the lack of synchronization between STDOUT and STDERR, it becomes impossible
to associate an SQL statement with either a CREATE or an ERROR message. The
option, "-e", is supposed to echo the query, but it doesn't help.

While I can see wanting to separate STDERR and STDOUT when one uses psql to run
an SQL query against a DB from within a shell script, it makes it much more
difficult when developing, and if I were to run several SQL queries into psql,
exactly the same association problem would occur.

Perhaps a combination of the function "isatty()" plus the -e flag would work? So
that if STDOUT "isatty()" then echo errors to STDOUT, otherwise send them to
STDERR. And if the -e flag is set, echo the queries to STDERR, so the
correlation between ERROR, CREATE, etc and SQL could be made.

Just my $0.02.

Mark

PS I only recently learned of the setting of the PAGER environment variable to
make it so I needn't scroll back up 400 lines to find my errors; perhaps this
could be made more prominent in the documentation as it would be a big help.
Then again, perhaps I should completely re-read the docs to see if this is
mentioned; I haven't done that for several releases now.

--
Mark Dalphin email: mdalphin@amgen.com
Mail Stop: 29-2-A phone: +1-805-447-4951 (work)
One Amgen Center Drive +1-805-375-0680 (home)
Thousand Oaks, CA 91320 fax: +1-805-499-9955 (work)

From bouncefilter Wed Dec 8 13:32:40 1999
Received: from tul1po1.tvguideinc.com (bart.uvsg.com [192.40.65.249])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA22245
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 13:31:51 -0500 (EST)
(envelope-from michael.j.davis@tvguide.com)
Received: by bart.uvsg.com with Internet Mail Service (5.5.2650.21)
id <YN05J91Y>; Wed, 8 Dec 1999 12:28:56 -0600
Message-ID: <93C04F1F5173D211A27900105AA8FCFC29949C@lambic.prevuenet.com>
From: Michael J Davis <michael.j.davis@tvguide.com>
To: "'Mark Dalphin'" <mdalphin@amgen.com>, pgsql-general@postgreSQL.org
Subject: RE: [GENERAL] Suggested "minor" change to psql
Date: Wed, 8 Dec 1999 12:27:41 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

Try:

psql < mySchema.sql >& myOutput 2> myOutput.err

Michael Davis
BackOffice Development, TV Guide Networks
Office: 303-267-6809 Fax: 303-267-6889
Home Office: 303-460-7360 Fax: 303-460-7362
Pager: 303-461-4002
Email: Michael.J.Davis@tvguide.com

-----Original Message-----
From: Mark Dalphin [SMTP:mdalphin@amgen.com]
Sent: Wednesday, December 08, 1999 11:04 AM
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] Suggested "minor" change to psql

Hi,

Ever since I began working with Postgres, I have had one little irritating
problem with psql. It may be that I am mis-using this program; if so, my
suggestion is not helpful, however, if others have encountered this
problem,
perhaps the developers can look at a fix for 7.0?

When I develop a new DB schema using psql, I usually first create a file,
say
"mySchema.sql". I then "createdb" the database, start up psql, and use the
command "\i mySchema.sql" to load in my new schema. There will be,
needless to
say, several errors. These fall nicely below the offending line and I can
look
at fixing them. I drop the DB, re-edit my SQL file and re-do the "\i"
command.

Sometimes, however, rather than using the "\i" command, I would like to
simply
load my schema directly into psql and capture the output on STDOUT (ie
"psql <
mySchema.sql >& myOutput"). The problem that arises is that the errors
and
notices all come out on STDERR. I am not sure this is the right choice.
Because
of the lack of synchronization between STDOUT and STDERR, it becomes
impossible
to associate an SQL statement with either a CREATE or an ERROR message.
The
option, "-e", is supposed to echo the query, but it doesn't help.

While I can see wanting to separate STDERR and STDOUT when one uses psql
to run
an SQL query against a DB from within a shell script, it makes it much
more
difficult when developing, and if I were to run several SQL queries into
psql,
exactly the same association problem would occur.

Perhaps a combination of the function "isatty()" plus the -e flag would
work? So
that if STDOUT "isatty()" then echo errors to STDOUT, otherwise send them
to
STDERR. And if the -e flag is set, echo the queries to STDERR, so the
correlation between ERROR, CREATE, etc and SQL could be made.

Just my $0.02.

Mark

PS I only recently learned of the setting of the PAGER environment
variable to
make it so I needn't scroll back up 400 lines to find my errors; perhaps
this
could be made more prominent in the documentation as it would be a big
help.
Then again, perhaps I should completely re-read the docs to see if this is
mentioned; I haven't done that for several releases now.

--
Mark Dalphin email: mdalphin@amgen.com
Mail Stop: 29-2-A phone: +1-805-447-4951 (work)
One Amgen Center Drive +1-805-375-0680 (home)
Thousand Oaks, CA 91320 fax: +1-805-499-9955 (work)

************

From bouncefilter Wed Dec 8 13:42:40 1999
Received: from dec.contad.unam.mx (dec.contad.unam.mx [132.248.158.18])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA23561
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 13:42:16 -0500 (EST)
(envelope-from sony@dec.contad.unam.mx)
Received: from localhost (sony@localhost) by dec.contad.unam.mx with ESMTP
(8.7.1/8.7.1) id MAA13126; Wed, 8 Dec 1999 12:27:44 -0600 (CST)
Date: Wed, 8 Dec 1999 12:27:44 -0600 (CST)
From: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
X-Sender: sony@dec.contad.unam.mx
To: Mark Dalphin <mdalphin@amgen.com>
cc: pgsql-general@postgreSQL.org
Subject: Size of database
In-Reply-To: <384E9D82.CCC45186@amgen.com>
Message-ID: <Pine.HPX.4.10.9912081226020.13070-100000@dec.contad.unam.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Somebody can help me?

I need to know which is the maximum size of the database in
Postgresql and how many records I can keeps into it?

Tnaks!

Sonia Sanchez Diaz
UNAM_FCA_CIFCA_Admon.Red
e-mail: sony@dec.contad.unam.mx

From bouncefilter Wed Dec 8 13:54:40 1999
Received: from biology.nmsu.edu (biology.NMSU.Edu [128.123.5.72])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA24994
for <hackers@postgreSQL.org>; Wed, 8 Dec 1999 13:54:28 -0500 (EST)
(envelope-from brook@biology.nmsu.edu)
Received: (from brook@localhost) by biology.nmsu.edu (8.8.8/8.8.8) id
LAA14035;
Wed, 8 Dec 1999 11:54:26 -0700 (MST)
Date: Wed, 8 Dec 1999 11:54:26 -0700 (MST)
Message-Id: <199912081854.LAA14035@biology.nmsu.edu>
X-Authentication-Warning: biology.nmsu.edu: brook set sender to
brook@biology.nmsu.edu using -f
From: Brook Milligan <brook@biology.nmsu.edu>
To: hackers@postgreSQL.org
Cc: mdalphin@amgen.com
In-reply-to: <384E9D82.CCC45186@amgen.com> (message from Mark Dalphin on Wed,
08 Dec 1999 10:03:46 -0800)
Subject: Re: [GENERAL] Suggested "minor" change to psql
References: <384E9D82.CCC45186@amgen.com>

I think the new stuff allows separating or merging different output
"channels" so that psql can be run in the different ways you wish.

However, this does raise another issue that might make debugging
scripts run through psql easier. I have found that emacs compile
buffer semantics are extremely useful for debugging source code, and
suggest that error messages from psql follow something similar (at
least as an option) to aid in script debugging. The output of
compiler error messages generally gives a filename:linenumber prefix
to the message; emacs can parse that an put you exactly at the correct
point for fixing the error.

If psql would also output messages in the same form, i.e.,

filename:linenumber: error message

then scripts run in emacs compile buffer (easily done either directly
or with make) could be rapidly debugged using the normal mechanisms
available for "normal" source code debugging.

I realize that everyone does not use emacs, but I can't see how
including that information would be detrimental to anyone. It gives
more information useful for anyone debugging scripts.

Cheers,
Brook

From bouncefilter Wed Dec 8 14:06:40 1999
Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA26931
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 14:06:26 -0500 (EST)
(envelope-from moray.mcconnachie@computing-services.oxford.ac.uk)
Received: from ermine.ox.ac.uk ([163.1.2.13])
by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1)
id 11vmPn-0005JT-00; Wed, 8 Dec 1999 19:06:15 +0000
Received: from moray (helo=localhost)
by ermine.ox.ac.uk with local-esmtp (Exim 2.12 #1)
id 11vmPn-00015v-00; Wed, 8 Dec 1999 19:06:15 +0000
Date: Wed, 8 Dec 1999 19:06:15 +0000 (GMT)
From: Moray McConnachie <moray.mcconnachie@computing-services.oxford.ac.uk>
To: Mark Dalphin <mdalphin@amgen.com>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Suggested "minor" change to psql
In-Reply-To: <384E9D82.CCC45186@amgen.com>
Message-ID: <Pine.OSF.4.10.9912081900110.28334-100000@ermine.ox.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

What's wrong with pgsql -d xxxx -c '\i myschema' > databaseload.logfile ?

Seems to work OK for me.

You can always use the 2>&1 syntax to redirect STDERR to STDOUT as well.

Yours,
Moray

From bouncefilter Wed Dec 8 14:24:40 1999
Received: from fordfamilymarketing.com (jforddsl.wvi.com [204.245.255.187])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA28927
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 14:23:48 -0500 (EST)
(envelope-from stolkd@email.com)
Received: from email.com (localhost [127.0.0.1])
by fordfamilymarketing.com (8.9.3/8.9.3) with ESMTP id LAA05905;
Wed, 8 Dec 1999 11:22:54 -0800
Sender: root@fordfamilymarketing.com
Message-ID: <384EB00E.B8BFAD50@email.com>
Date: Wed, 08 Dec 1999 11:22:54 -0800
From: Daniel Stolk <stolkd@email.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
CC: Mark Dalphin <mdalphin@amgen.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Size of database
References: <Pine.HPX.4.10.9912081226020.13070-100000@dec.contad.unam.mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Look at:

http://www.postgresql.org/docs/faq-english.html#4.6

Daniel Stolk

Sanchez Diaz Sonia wrote:

Somebody can help me?

I need to know which is the maximum size of the database in
Postgresql and how many records I can keeps into it?

Tnaks!

Sonia Sanchez Diaz
UNAM_FCA_CIFCA_Admon.Red
e-mail: sony@dec.contad.unam.mx

************

From bouncefilter Wed Dec 8 14:28:42 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA29538
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 14:27:43 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.57.207]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 8 Dec 1999 13:18:40 -0600
Sender: ed
Message-ID: <384EB09A.472A931B@austin.rr.com>
Date: Wed, 08 Dec 1999 13:25:14 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Dalphin <mdalphin@amgen.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Suggested "minor" change to psql
References: <384E9D82.CCC45186@amgen.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mark Dalphin wrote:

Sometimes, however, rather than using the "\i" command, I would like to simply
load my schema directly into psql and capture the output on STDOUT (ie "psql <
mySchema.sql >& myOutput"). The problem that arises is that the errors and
notices all come out on STDERR. I am not sure this is the right choice. Because
of the lack of synchronization between STDOUT and STDERR, it becomes impossible
to associate an SQL statement with either a CREATE or an ERROR message. The
option, "-e", is supposed to echo the query, but it doesn't help.

I have experienced this problem as well. It is a bit of a pain. I would love to
hear how others are handling this. I have one partial workaround.

% psql -d test -f createdb.sql 2>&1 | less

For whatever reason, the above seems to keep the msgs fairly synchronized (at least
on Redhat 6.0), making it useful for visual inspection of short loads.
Unfortunately, that approach far exceeds my patience for my situation. I'm
frequently recreating 150 tables and redoing ~1400 INSERTs via psql with input
scripts. That takes about 4 minutes on a dual PII 450 and generates ~15K lines of
output (~500 PAGER pages @30 lines/page). Instead, I pipe STDERR/STDOUT to a file,
and then grep the file for 'INSERT 0 0', 'ERROR', and other problem signs. I've
gotten pretty good at matching up the error msgs with the problem by interspersing
judiciously comments and queries, but it's still a pain.

It'd be nice to be able to get all psql msgs sync'ed on either STDERR or STDOUT.

Cheers.
Ed

From bouncefilter Wed Dec 8 20:35:46 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id UAA19316
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 20:35:42 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id BA1B11F79; Wed, 8 Dec 1999 20:34:40 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id A62811F75
for <pgsql-general@postgresql.org>;
Wed, 8 Dec 1999 20:34:40 +0000 (GMT)
Date: Wed, 8 Dec 1999 20:34:40 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: update within limits
Message-ID: <Pine.BSF.4.10.9912082032440.5887-100000@server.b0x.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Quick question:
Is there a way to update fields in a table within limits, similarly to
using a select. In other words, something like this:
update from table1 field1='blah' where id=(select id from table2 limit
5,5);

Thanks,
Marc

From bouncefilter Wed Dec 8 17:54:43 1999
Received: from mercury.shreve.net (IDENT:root@mercury.shreve.net
[208.206.76.23]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA01053
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 17:54:32 -0500 (EST)
(envelope-from kheflin@shreve.net)
Received: from mercury.shreve.net (IDENT:kheflin@mercury.shreve.net
[208.206.76.23])
by mercury.shreve.net (8.9.3/8.9.3) with ESMTP id QAA29295
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 16:41:00 -0600
Date: Wed, 8 Dec 1999 16:40:58 -0600 (CST)
From: Kevin Heflin <kheflin@shreve.net>
To: "PGSQL-General (E-mail)" <pgsql-general@postgreSQL.org>
Subject: get the previous assigned sequence value
Message-ID: <Pine.LNX.4.10.9912081639280.11761-100000@mercury.shreve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I've been looking through the online docs, so far have not found this
information.

After an INSERT, I want to retrieve the value of the sequence I use for
unique_ids

Any suggestions ?

Kevin

From bouncefilter Wed Dec 8 19:15:44 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA10559
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 19:15:05 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:63702 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sHjFx114743>; Thu, 9 Dec 1999 01:14:53 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11vrIG-0003Yp-00; Thu, 09 Dec 1999 01:18:48 +0100
Date: Thu, 9 Dec 1999 01:18:48 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Lincoln Yeoh <lylyeoh@mecomb.com>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
In-Reply-To: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
Message-ID: <Pine.LNX.4.20.9912090111190.389-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-08, Lincoln Yeoh mentioned:

begin;
insert into stuff;
do some nondatabase things based on last inserted id;
update a date in stuff;
commit;

It seems that if the date is out of the database range, everything is
thrown out. Is it possible to catch the database error and use a null date
instead, without throwing everything away?

Yes, use no transaction at all. :)

Seriously, why do you use a transaction, when you don't want any errors
caught? Transactions are defined as everything succeeds or nothing goes.
If you want update to succeed anyhow, put it in it's own transaction
(i.e., commit before it).

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

The safest way would be to set a date format with SET DATESTYLE TO and use
that, possibly assisted by library formatting routines.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Wed Dec 8 20:23:45 1999
Received: from mecomb.com (gw.mecomb.com [161.142.249.98])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA17533
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 20:23:17 -0500 (EST)
(envelope-from lylyeoh@mecomb.com)
Received: (from mail@localhost) by mecomb.com (8.8.7/8.8.7) id JAA16197;
Thu, 9 Dec 1999 09:23:17 +0800
Received: from <lylyeoh@mecomb.com> (ilab2.mecomb.po.my [192.168.3.22]) by
ns.mecomb.com via smap (V2.1)
id xma016195; Thu, 9 Dec 99 09:23:01 +0800
Message-Id: <3.0.5.32.19991209092335.008f62c0@pop.mecomb.po.my>
X-Sender: lylyeoh@pop.mecomb.po.my
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 09 Dec 1999 09:23:35 +0800
To: Peter Eisentraut <peter_e@gmx.net>
From: Lincoln Yeoh <lylyeoh@mecomb.com>
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
Cc: pgsql-general@postgreSQL.org
In-Reply-To: <Pine.LNX.4.20.9912090111190.389-100000@localhost.localdoma
in>
References: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:18 AM 09-12-1999 +0100, Peter Eisentraut wrote:

Seriously, why do you use a transaction, when you don't want any errors
caught? Transactions are defined as everything succeeds or nothing goes.
If you want update to succeed anyhow, put it in it's own transaction
(i.e., commit before it).

I want errors caught, most errors abort everything but some errors I want
to try a different update instead, if that doesn't work then only rollback
everything.

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

The safest way would be to set a date format with SET DATESTYLE TO and use
that, possibly assisted by library formatting routines.

OK.

Link.

From bouncefilter Wed Dec 8 22:22:27 1999
Received: from drillich.uniserve.de (drillich.uniserve.de [195.27.4.3])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA01328
for <pgsql-general@postgreSQL.org>; Wed, 8 Dec 1999 22:21:16 -0500 (EST)
(envelope-from drillich@uniserve.de)
Received: from uniserve.de (localhost [127.0.0.1])
by drillich.uniserve.de (8.9.3/8.8.8) with ESMTP id EAA29427;
Thu, 9 Dec 1999 04:08:05 +0100
Sender: drillich@drillich.uniserve.de
Message-ID: <384F1D15.180BC4F4@uniserve.de>
Date: Thu, 09 Dec 1999 04:08:05 +0100
From: Thomas Drillich <drillich@uniserve.de>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686)
X-Accept-Language: de-DE, en
MIME-Version: 1.0
To: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>
CC: pgsql-general@postgreSQL.org
Subject: pg_typemgr ;
-) [was Re: [GENERAL] no primary key on self designed type]
References: <199912072049.OAA22473@mail.xnet.com>
Content-Type: multipart/mixed; boundary="------------45E243A1931B98D6F8498059"

This is a multi-part message in MIME format.
--------------45E243A1931B98D6F8498059
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Gene,

is this correct

pg_typemgr.html # description of my perl-program

pg_typemgr -p inr -d test inrecord # delete type
pg_typemgr -p inr -f in_record.sql test inrecord # delete and restore
pg_typemgr -p inr -l all test inrecord > inrecord.out # list anything
pg_typemgr -p inr -l all test inet > inet.out # to compare

When I have to setup pg_amproc like in inet.out ?
Whats about inet | = | hashsel | hashnpage | hash ..

thanks in advance
tom.

"Gene Selkov Jr." wrote:

Hello,

create type inrecord (
internallength=VARIABLE,
input=inr_in,
output=inr_out
);

create table test (
data inrecord not null primary key
);
... result ...
ERROR: Can't find a default operator class for type 268128.

how can I define the default operator class ??
--

The short answer is,

INSERT INTO pg_opclass (opcname, opcdeftype)
SELECT 'inrecord_ops', oid
FROM pg_type
WHERE typname = 'inrecord';

But you won't get away with just that. You probably want a non-empty
opclass. For example, if your type, inrecord, needs a btree opclass,
you'll want to do:

SELECT o.oid AS opoid, o.oprname
INTO TABLE inrecord_ops_tmp
FROM pg_operator o, pg_type t
WHERE o.oprleft = t.oid and o.oprright = t.oid
and t.typname = 'inrecord';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 1,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '<';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 2,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '<=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 3,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 4,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '>=';

INSERT INTO pg_amop (amopid, amopclaid, amopopr, amopstrategy,
amopselect, amopnpages)
SELECT am.oid, opcl.oid, c.opoid, 5,
'btreesel'::regproc, 'btreenpage'::regproc
FROM pg_am am, pg_opclass opcl, inrecord_ops_tmp c
WHERE amname = 'btree' and opcname = 'inrecord_ops'
and c.oprname = '>';

DROP table inrecord_ops_tmp;

Which isn't all yet. The code above assumes that you have defined the
operators, '=', '>=', etc.:

CREATE OPERATOR = (
leftarg = inrecord, rightarg = inrecord_code, procedure = inrecord_eq,
restrict = eqsel, join = eqjoinsel
);

If that didn't make you sick already, you also need to define the
procedures, such as inrecord_eq in this example, and possibly write
some c code for them:

CREATE FUNCTION inrecord_eq(inrecord, inrecord) RETURNS bool
AS '${LIBDIR}/inrecord.so' LANGUAGE 'c';

INSERT INTO pg_description (objoid, description)
SELECT oid, 'equals'::text
FROM pg_proc
WHERE proname = 'inrecord_eq'::name;

Thar's, in short, what is required to build a completely new type. One
might as well attempt to borrow some code or the whole opclass from
existing similar types, but I would hesitate to even consider doing that
without the thorough knowledge of the current postgres schema, which
is unfortunately not yet covered by the contemporary docs.

--Gene

--
mit freundlichem Gruss -- regards
,-,
| | Thomas Drillich <drillich@uniserve.de>
___|__|
(___, ) uniserve Internet & Multimedia GmbH
(___, )\ Sophienweg 3
(___, ) \ Technologiezentrum (MIT)
(___,_,)/ \ D-59872 Meschede Germany
\ fon: +49 291 59100 , fax: +49 291 59102
--------------45E243A1931B98D6F8498059
Content-Type: text/html; charset=us-ascii;
name="pg_typemgr.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="pg_typemgr.html"

<HTML>
<HEAD>
<TITLE>pg_typemgr</TITLE>
<LINK REV="made" HREF="mailto:drillich@uniserve.de">
</HEAD>

<BODY>

<UL>

<LI><A HREF="#NAME_pg_typemgr_Options_dbnam">NAME pg_typemgr [Options] <dbname> <type> [|<type>[,<prefix>]]</A>
<LI><A HREF="#Description">Description</A>
<LI><A HREF="#Options">Options</A>
<LI><A HREF="#Placeholders">Placeholders</A>
<LI><A HREF="#Bugs">Bugs</A>
<LI><A HREF="#Todo">Todo</A>
<LI><A HREF="#See_Also">See Also</A>
<LI><A HREF="#Copyright">Copyright</A>
<LI><A HREF="#Disclaimer">Disclaimer</A>
</UL>

<HR>
<P>
<H1><A NAME="NAME_pg_typemgr_Options_dbnam">NAME pg_typemgr [Options] <dbname> <type> [|<type>[,<prefix>]]</A></H1>
<P>
<HR>
<H1><A NAME="Description">Description</A></H1>
<P>
pg_typemgr trys to manage self designed types for postgreSQL.

<P>
<HR>
<H1><A NAME="Options">Options</A></H1>
<DL>
<DT><STRONG><A NAME="item__h">-h <host> | --host=<host></A></STRONG><DD>
<P>
set the hostname where the postmaster runs, default `localhost'.

<DT><STRONG><A NAME="item__u">-u <user> | --user=<user></A></STRONG><DD>
<P>
connect to database as <user>.

<DT><STRONG><A NAME="item__pass_password_">--pass=<password></A></STRONG><DD>
<P>
use <password> on connect.

<DT><STRONG><A NAME="item__d">-d | --delete</A></STRONG><DD>
<P>
delete <type>, you have to backup the tables before.

<DT><STRONG><A NAME="item__f">-f <file> | --file=<file></A></STRONG><DD>
<P>
sql command file to redefine <type>.

<DT><STRONG><A NAME="item__l">-l <what> | --l<what></A></STRONG><DD>
<P>
list one of

<DL>
<DT><STRONG><A NAME="item_proc">proc</A></STRONG><DD>
<P>
the procedures depend on type in pg_proc.

<DT><STRONG><A NAME="item_oper">oper</A></STRONG><DD>
<P>
the operators of type in pg_operators.

<DT><STRONG><A NAME="item_opclass">opclass</A></STRONG><DD>
<P>
the defined opclasses in pg_opclass.

<DT><STRONG><A NAME="item_amop">amop</A></STRONG><DD>
<P>
the definitions in pg_amop.

<DT><STRONG><A NAME="item_amproc">amproc</A></STRONG><DD>
<P>
the definitions in pg_amproc.

<DT><STRONG><A NAME="item_table">table</A></STRONG><DD>
<P>
tables and indezies where <type> occours.

</DL>
<DT><STRONG><A NAME="item__p">-p <prefix> | --prefix=<prefix></A></STRONG><DD>
<P>
prefix of functions which should include in the query, eg.
<prefix>_cmp>, on default <prefix> == <type>

<DT><STRONG><A NAME="item__lt_ltfunction_">--lt=<ltfunction></A></STRONG><DD>
<P>
the function for the operator `<' default <EM>bool <prefix</EM><CODE>_lt(<type></CODE> *,<type> *)>.

<DT><STRONG><A NAME="item__le_lefunction_">--le=<lefunction></A></STRONG><DD>
<P>
the function for the operator `<='

<DT><STRONG><A NAME="item__eq_eqfunction_">--eq=<eqfunction></A></STRONG><DD>
<P>
the function for the operator `='

<DT><STRONG><A NAME="item__ge_gefunction_">--ge=<gefunction></A></STRONG><DD>
<P>
the function for the operator `>='

<DT><STRONG><A NAME="item__gt_gtfunction_">--gt=<gtfunction></A></STRONG><DD>
<P>
the function for the operator `>'

<DT><STRONG><A NAME="item__ne_nefunction_">--ne=<nefunction></A></STRONG><DD>
<P>
the function for the operator `!='

<DT><STRONG><A NAME="item__cmp_cmpfunction_">--cmp=<cmpfunction></A></STRONG><DD>
<P>
function which returns (-1,0,1) on (a<b,a==b,a>b) the compare
function, default

<P>
int4 <prefix>_cmp(<type> *,<type> *)

</DL>
<P>
<HR>
<H1><A NAME="Placeholders">Placeholders</A></H1>
<DL>
<DT><STRONG><A NAME="item__dbname_"><dbname></A></STRONG><DD>
<P>
the name of the database where pg_typemgr operates on.

<DT><STRONG><A NAME="item__type_"><type></A></STRONG><DD>
<P>
the name of the data type.

<DT><STRONG><A NAME="item__prefix_"><prefix></A></STRONG><DD>
<P>
the prefix of functions which should include in the query, default
<type>.

<DT><STRONG><A NAME="item__host_"><host></A></STRONG><DD>
<P>
the hostname of the postgreSQL server.

</DL>
<P>
<HR>
<H1><A NAME="Bugs">Bugs</A></H1>
<P>
this is the alpha version, need testing ;-)

<P>
<HR>
<H1><A NAME="Todo">Todo</A></H1>
<P>
correct update pg_amproc on insert of <type>.

<P>
<HR>
<H1><A NAME="See_Also">See Also</A></H1>
<DL>
<DT><STRONG><A NAME="item_psql">psql</A></STRONG><DD>
<DT><STRONG><A NAME="item_http">http://www.postgreSQL.org</A></STRONG><DD>
<DT><STRONG><A NAME="item_http">http://www.uniserve.de my homepage</A></STRONG><DD>
</DL>
<P>
<HR>
<H1><A NAME="Copyright">Copyright</A></H1>
<P>
(c) 1999-2002 Thomas Drillich <<A
HREF="mailto:drillich@uniserve.de">drillich@uniserve.de</A>>

<P>
<HR>
<H1><A NAME="Disclaimer">Disclaimer</A></H1>
<P>
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement
is hereby granted, provided that the above copyright notice and this
paragraph and the following two paragraphs appear in all copies.

<P>
IN NO EVENT SHALL THE AUTHOR OR HIS COMPANY BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

<P>
THE THE AUTHOR OR HIS COMPANY SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON
AN ``AS IS'' BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

</BODY>

</HTML>

--------------45E243A1931B98D6F8498059
Content-Type: text/plain; charset=us-ascii;
name="inet.out"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="inet.out"

--------------45E243A1931B98D6F8498059
Content-Type: text/plain; charset=us-ascii;
name="inrecord.out"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="inrecord.out"

--------------45E243A1931B98D6F8498059
Content-Type: text/plain; charset=us-ascii;
name="in_record.sql"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="in_record.sql"

-----------------------------------------------------------
-- install the in_record type
-----------------------------------------------------------
create function inr_in(opaque)
RETURNS inrecord
AS '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

create function inr_out(opaque)
RETURNS opaque
AS '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

create type inrecord (
internallength=VARIABLE,
input=inr_in,
output=inr_out
);

-----------------------------------------------------------
-- return type as text
create function inr_type(inrecord)
returns bpchar
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
-- or number
create function inr_nr(inrecord)
returns int
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
-----------------------------------------------------------
--
-- return record as text
--
create function inr_data(inrecord)
returns text
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
--
-- inr_inet:
-- return address record as inet
-- drops error on text record
create function inr_inet(inrecord)
returns inet
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
-----------------------------------------------------------
--
-- comparision functions
-- inrecord,inrecord
create function inr_cmp(inrecord,inrecord)
returns int4
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_lt(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_le(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_eq(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_ge(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_gt(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inr_ne(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

--
-- comparision operators
-- inrecord,inrecord
create operator < (
procedure=inr_lt,
leftarg=inrecord,
rightarg=inrecord,
commutator= <,
negator= >=
);
create operator <= (
procedure=inr_le,
leftarg=inrecord,
rightarg=inrecord,
commutator= <=,
negator= >
);
create operator = (
procedure=inr_eq,
leftarg=inrecord,
rightarg=inrecord,
commutator= '=',
negator= '!=',
restrict = eqsel,
join = eqjoinsel,
HASHES
);
create operator >= (
procedure=inr_ge,
leftarg=inrecord,
rightarg=inrecord,
commutator= =,
negator= <
);
create operator > (
procedure=inr_gt,
leftarg=inrecord,
rightarg=inrecord,
commutator= >,
negator= <=
);
create operator != (
procedure=inr_ne,
leftarg=inrecord,
rightarg=inrecord,
commutator= '!=',
negator= '=',
restrict = neqsel,
join = neqjoinsel,
HASHES
);

-----------------------------------------------------------
--
-- comparision functions
-- inrecord,inet
-- inrinet_lt <
-- inrinet_le <=
-- inrinet_eq =
-- inrinet_ge >=
-- inrinet_gt >
-- inrinet_sub <<
-- inrinet_subeq <<=
-- inrinet_sup >>
-- inrinet_supeq >>=

create function inrinet_lt(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_le(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_eq(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_ge(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_gt(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_ne(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_sub(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_subeq(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_sup(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrinet_supeq(inrecord,inet)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

--
-- comparision operators
-- inrecord,inrecord
create operator < (
procedure=inrinet_lt,
leftarg=inrecord,
rightarg=inet,
commutator= <,
negator= >=
);
create operator <= (
procedure=inrinet_le,
leftarg=inrecord,
rightarg=inet,
commutator= <=,
negator= >
);
create operator = (
procedure=inrinet_eq,
leftarg=inrecord,
rightarg=inet,
commutator= =,
negator= !=
);
create operator >= (
procedure=inrinet_ge,
leftarg=inrecord,
rightarg=inet,
commutator= >=,
negator= <
);
create operator > (
procedure=inrinet_gt,
leftarg=inrecord,
rightarg=inet,
commutator= >,
negator= <=
);
create operator << (
procedure=inrinet_sub,
leftarg=inrecord,
rightarg=inet,
commutator= <<
);
create operator <<= (
procedure=inrinet_subeq,
leftarg=inrecord,
rightarg=inet,
commutator= <<=
);
create operator >> (
procedure=inrinet_sup,
leftarg=inrecord,
rightarg=inet,
commutator= >>
);
create operator >>= (
procedure=inrinet_supeq,
leftarg=inrecord,
rightarg=inet,
commutator= >>=
);
---------------------------------------
--
-- comparision functions for cnames
-- (case insensitive)
-- inrecord,inrecord
-- inr_like ~~
-- inr_nlike !~~
-- inr_regexp ~
-- inr_nregexp !~
-- inrecord,text
-- inrtext_like ~~
-- inrtext_nlike !~~
-- inrtext_regexp ~
-- inrtext_nregexp !~
create function inr_like(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_like(inrecord,text)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_like(inrecord,bpchar)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

create function inr_nlike(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_nlike(inrecord,text)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_nlike(inrecord,bpchar)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

create function inr_regexp(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_regexp(inrecord,text)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_regexp(inrecord,bpchar)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';

create function inr_nregexp(inrecord,inrecord)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_nregexp(inrecord,text)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
create function inrtext_nregexp(inrecord,bpchar)
returns bool
as '/home/drillich/src/dns/db/src/in_record.so'
Language 'C';
-- operators
create operator ~~ (
procedure=inr_like,
leftarg=inrecord,
rightarg=inrecord,
commutator= ~~,
negator= !~~
);
create operator ~~ (
procedure=inrtext_like,
leftarg=inrecord,
rightarg=text,
commutator= ~~,
negator= !~~
);
create operator ~~ (
procedure=inrtext_like,
leftarg=inrecord,
rightarg=bpchar,
commutator= ~~,
negator= !~~
);
create operator !~~ (
procedure=inr_nlike,
leftarg=inrecord,
rightarg=inrecord,
commutator= ~~,
negator= !~~
);
create operator !~~ (
procedure=inrtext_nlike,
leftarg=inrecord,
rightarg=text,
commutator= !~~,
negator= ~~
);
create operator !~~ (
procedure=inrtext_nlike,
leftarg=inrecord,
rightarg=bpchar,
commutator= !~~,
negator= ~~
);
create operator ~ (
procedure=inr_regexp,
leftarg=inrecord,
rightarg=inrecord,
commutator= ~,
negator= !~
);
create operator ~ (
procedure=inrtext_regexp,
leftarg=inrecord,
rightarg=text,
commutator= ~,
negator= !~
);
create operator ~ (
procedure=inrtext_regexp,
leftarg=inrecord,
rightarg=bpchar,
commutator= ~,
negator= !~
);
create operator !~ (
procedure=inr_nregexp,
leftarg=inrecord,
rightarg=inrecord,
commutator= !~,
negator= ~
);
create operator !~ (
procedure=inrtext_nregexp,
leftarg=inrecord,
rightarg=text,
commutator= !~,
negator= ~
);
create operator !~ (
procedure=inrtext_nregexp,
leftarg=inrecord,
rightarg=bpchar,
commutator= !~,
negator= ~
);
-- EOF in_record.sql

--------------45E243A1931B98D6F8498059--

From bouncefilter Wed Dec 8 23:17:56 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA63531
for <pgsql-general@postgresql.org>; Wed, 8 Dec 1999 23:17:35 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.57.207]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 8 Dec 1999 22:09:28 -0600
Sender: ed
Message-ID: <384F2CE4.115503C@austin.rr.com>
Date: Wed, 08 Dec 1999 22:15:32 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Kevin Heflin <kheflin@shreve.net>
CC: "PGSQL-General (E-mail)" <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] get the previous assigned sequence value
References: <Pine.LNX.4.10.9912081639280.11761-100000@mercury.shreve.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Kevin Heflin wrote:

I've been looking through the online docs, so far have not found this
information.

After an INSERT, I want to retrieve the value of the sequence I use for
unique_ids

Any suggestions ?

Use the OID returned from the INSERT to select the newly created value,
i.e.,

insert into mytable (stuff...) ...
select id from mytable where oid = NNNN...

How to get the OID in the first example varies depending on your interface
(perl/DBI, PL/pgsql, etc).

Alternatively, use the currval(mytable_id_seq) function within the same
session immediately after the insert.

Cheers.
Ed

From bouncefilter Thu Dec 9 00:03:00 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA56286
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 00:01:59 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
AAA08057;
Thu, 9 Dec 1999 00:00:23 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912090500.AAA08057@candle.pha.pa.us>
Subject: Re: pg_typemgr ;
-) [was Re: [GENERAL] no primary key on self designed
type]
In-Reply-To: <384F1D15.180BC4F4@uniserve.de> from Thomas Drillich at "Dec 9,
1999 04:08:05 am"
To: Thomas Drillich <drillich@uniserve.de>
Date: Thu, 9 Dec 1999 00:00:23 -0500 (EST)
CC: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>,
pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Gene,

is this correct

pg_typemgr.html # description of my perl-program

pg_typemgr -p inr -d test inrecord # delete type
pg_typemgr -p inr -f in_record.sql test inrecord # delete and restore
pg_typemgr -p inr -l all test inrecord > inrecord.out # list anything
pg_typemgr -p inr -l all test inet > inet.out # to compare

When I have to setup pg_amproc like in inet.out ?
Whats about inet | = | hashsel | hashnpage | hash ..

I have just fixed cidr indexing in pg_amproc.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 9 00:07:56 1999
Received: from rage.hub.org (root@nat202.25.mpoweredpc.net [142.177.202.25])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA57138
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 00:07:03 -0500 (EST)
(envelope-from jeff@hub.org)
Received: from localhost (jeff@localhost)
by rage.hub.org (8.9.3/8.9.3) with ESMTP id BAA04232
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 01:07:42 -0400 (AST)
(envelope-from jeff@hub.org)
X-Authentication-Warning: rage.hub.org: jeff owned process doing -bs
Date: Thu, 9 Dec 1999 01:07:41 -0400 (AST)
From: Jeff MacDonald <jeff@hub.org>
Reply-To: Jeff MacDonald <jeff@hub.org>
To: pgsql-general@postgresql.org
Subject: View / Unions
Message-ID: <Pine.BSF.4.10.9912090107030.529-100000@rage.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is they any guess on when it will be possible to do
a view of a union of 2 tables ?

thanks

Jeff MacDonald
jeff@hub.org

===================================================================
So long as the Universe had a beginning, we can suppose it had a
creator, but if the Universe is completly self contained , having
no boundry or edge, it would neither be created nor destroyed
It would simply be.
===================================================================

From bouncefilter Thu Dec 9 00:30:56 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA60620
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 00:30:13 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
AAA09099;
Thu, 9 Dec 1999 00:28:01 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912090528.AAA09099@candle.pha.pa.us>
Subject: Re: [GENERAL] View / Unions
In-Reply-To: <Pine.BSF.4.10.9912090107030.529-100000@rage.hub.org> from Jeff
MacDonald at "Dec 9, 1999 01:07:41 am"
To: Jeff MacDonald <jeff@hub.org>
Date: Thu, 9 Dec 1999 00:28:01 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Is they any guess on when it will be possible to do
a view of a union of 2 tables ?

thanks

I think it needs the new multi-Query tree representation, which is not
planned until around July.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 9 04:23:59 1999
Received: from proterians.net (IDENT:root@chaos.proterians.net.pl
[195.117.150.130]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA84122
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 04:23:20 -0500 (EST)
(envelope-from greg@proterians.net)
From: greg@proterians.net
Received: from localhost (greg@localhost)
by proterians.net (8.9.2/8.9.1) with ESMTP id LAA19185
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 11:29:31 +0100 (EET)
Date: Thu, 9 Dec 1999 11:29:31 +0100 (EET)
To: pgsql-general@postgresql.org
Subject: parse error ???
Message-ID: <Pine.LNX.4.05.9912091122410.18605-100000@proterians.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have one question...

Why postgres returns parse error when i send

select birth_time::date from table;

parse error at or near ":"

I use CBuilder4 and postODBC driver...

when I write

select date(birth_time) from table;

it works...

but in DataBaseExplorer the first query works fine....

please help....

--Greg--

From bouncefilter Thu Dec 9 06:54:01 1999
Received: from www-uk-05.digiserve.com ([195.172.23.32])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA98433
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 06:53:39 -0500 (EST)
(envelope-from dev@archonet.com)
Received: from mainbox.archonet.com (IDENT:postfix@mwynhau.demon.co.uk
[193.237.186.96])
by www-uk-05.digiserve.com (8.9.1/8.9.1) with ESMTP id LAA03812
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 11:23:18 GMT
Received: from client (unknown [192.168.1.16])
by mainbox.archonet.com (Postfix) with SMTP id F2DB45085B
for <pgsql-general@postgreSQL.org>;
Thu, 9 Dec 1999 10:35:46 +0000 (GMT)
Message-ID: <00e301bf4231$4a586140$1001a8c0@client>
From: "Dev Elop" <dev@archonet.com>
To: <pgsql-general@postgreSQL.org>
References: <Pine.LNX.4.10.9912081639280.11761-100000@mercury.shreve.net>
<384F2CE4.115503C@austin.rr.com>
Subject: Re: [GENERAL] get the previous assigned sequence value
Date: Thu, 9 Dec 1999 10:36:40 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

After an INSERT, I want to retrieve the value of the sequence I use for
unique_ids

...

Alternatively, use the currval(mytable_id_seq) function within the same
session immediately after the insert.

With this second method, you'd probably need to beware race conditions. If
another process inserts a record into mytable after you do but before you
call currval(), then you'll get the wrong value.

Not an issue if you've only got one process accessing the table - probably
is one if you have two or more.

-
Richard Huxton

From bouncefilter Thu Dec 9 06:53:01 1999
Received: from mail.woehr.de (IDENT:root@[193.155.162.190])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA98374
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 06:52:24 -0500 (EST)
(envelope-from hr@woehr.de)
Received: from pcedv2 (pc-edv-2.woehr.de [193.155.162.112])
by mail.woehr.de (8.9.3/8.8.7) with SMTP id MAA19282
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 12:52:22 +0100
Reply-To: <Hans.Reichenecker@woehr.de>
From: "Hans Reichenecker" <hr@woehr.de>
To: <pgsql-general@postgresql.org>
Subject: Error: Using Large Objects by perl5-Interface
Date: Thu, 9 Dec 1999 12:51:59 +0100
Message-ID: <NCBBLNMBEIIOPJJOMJEJOEBBDIAA.hr@woehr.de>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_001E_01BF4244.2E77DD80"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MS-TNEF-Correlator: <NCBBLNMBEIIOPJJOMJEJOEBBDIAA.hr@woehr.de>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Disposition-Notification-To: "Hans Reichenecker" <hr@woehr.de>

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01BF4244.2E77DD80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

I want to use Large Objects in PostgreSQL, source is a Perl-Script. But in
unchained mode it won�t work. What else should I do to change in chained
mode ?

Users-Guide: "By default, Postgres executes transactions in
unchained mode (also known as "autocommit" in other database systems)."

Source:
$result = $conn->exec("BEGIN");
$stoeroid = $conn->lo_creat( 'PGRES_INV_ARCHIVE');
$stoeroidlen = $conn->lo_write( $stoeroid, $Meldung, length(
$Meldung));
$ERRor = $conn->lo_close( $stoeroid);
$result = $conn->exec("END");

results in Debug-Backend
query: BEGIN
ProcessUtility: BEGIN
CommitTransactionCommand
StartTransactionCommand
query: select proname, oid from pg_proc where proname = 'lo_open' or
proname = 'lo_close' or proname = 'lo_creat' or proname = 'lo_unlink'
or proname = 'lo_lseek' or proname = 'lo_tell' or proname = 'loread'
or proname = 'lowrite'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
CommitTransactionCommand
StartTransactionCommand
ERROR: lo_write: large obj descriptor (34850) out of range
AbortCurrentTransaction
StartTransactionCommand
ERROR: lo_close: large obj descriptor (34850) out of range
AbortCurrentTransaction
StartTransactionCommand
query: END
ProcessUtility: END
CommitTransactionCommand

Thanks for help.

OTTO W�HR GmbH Tel: 07044 46-0
Hans Reichenecker Tel: 07044 46193
Leiter DVO
�lgrabenstra�e 14 Fax: 07044 46266
71292 Friolzheim http:www.woehr.de

------=_NextPart_000_001E_01BF4244.2E77DD80
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="winmail.dat"

eJ8+IjsLAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAAM8HDAAJAAwAMwAAAAQALgEB
A5AGAGgJAAAmAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAEAAAACATEAAQAAAOoAAABQ
Q0RGRUIwOQABAAIAVwAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAAAAAAAABO
SVRB+b+4AQCqADfZbgAAAEY6XE91dGxvb2suQXJjaGl2XG91dGxvb2sucHN0ABgAAAAAAAAASJ6j
o6C60hG9wQAQWj1p88KBAAAAAAAAGAAAAAAAAABInqOjoLrSEb3BABBaPWnzwoAAABAAAAA5tnhT
ba3TEZKTABBaPWnzLgAAAEVycm9yOiBVc2luZyBMYXJnZSBPYmplY3RzIGJ5IHBlcmw1LUludGVy
ZmFjZQAAAAMANgAAAAAAHgBwAAEAAAAuAAAARXJyb3I6IFVzaW5nIExhcmdlIE9iamVjdHMgYnkg
cGVybDUtSW50ZXJmYWNlAAAAAgFxAAEAAAAWAAAAAb9CO8wwU3i2QK1tEdOSkwAQWj1p8wAAAgEd
DAEAAAARAAAAU01UUDpIUkBXT0VIUi5ERQAAAAALAAEOAAAAAEAABg4AakSpO0K/AQIBCg4BAAAA
GAAAAAAAAABInqOjoLrSEb3BABBaPWnzwoAAAAsAHw4BAAAAAgEJEAEAAAA/BAAAOwQAACgIAABM
WkZ1XPnYDwMACgByY3BnMTI1FjIA+Atgbg4QMDMxTwH3AqQD4wIAY2gKwHPwZXQwIAcTAoMAUANU
/xDJB20Cgw5QBFUQyQhVB7LNAoB9CoAIyCA7CW8OIJY4AoAKgXYIkHdrC4B0ZDQMYGMAUAsDC7Ug
GEkgdwBwBUB0byBSdREgIEwKwGcbgE80YmoFkHQEIAuAIFAIb3N0CcFTUUwsNCBzCGFjG4AEACBh
IxygBJBsLVMFAy4gzEJ1BUAcgXVuEOELgF0JgCAEYhxwBUB3AiBcSCdiNCBycmse4FeTEPAFQGVs
G3FzaAhg9mwf8BrAZBtAGzEQ4Q8g9x3BA6Afmz8KogqECoESAmcL8BmQAZEgVREgERAtCEd1aQEA
OiAiQtZ5IqABEGEiUHQdUBy1OQQgZXgFkB8QB5F0cnMAcQDQdGkCIBxjH30ogwdAHXAga25vdwOg
jmEEISJgAmBxdW8ooMseAB8QbwWgbW0gYAAQ1yvnHHIsMGgWEWQhoAGgCyuQIgF5HNBlbXMpXC4i
JPYLxSSjUx2DOncklC2wMaIkKBEncTGkPUMx8AWgbm4tPihSKIEm8EVHSU4iKRdw6zFaHNBvBJBv
JqAymwkACl8FAGUhoCggJ1AgR1JFU18z8FZfAEFSQ0hJVkUn2zQvNTRsCfA1y3cFECigpzbgNQcd
UCRNIdBkH3B2Zx1QOaFnLhA68TvVKfk4PUVSCAAFwDJ9NmIJAB8RIDr5OD0yHzMoRU5EDzQXJJRB
1BxjRGVidehnLUIA0GsJ8AsxJLN3JeIsEASQeSbQM8NGKVDXA2AdsAQQVSlQbCBgRx/3JgAIUCzS
VCj4SkIAcEYa/lMBkAAgSq9GHybQESA5oMkcQCBwA2BuYQeAHVCnNWIDUk9gZ19PcWMa0C8uIRuA
T3UywSc2YW9w/QnwJy3wBcBRfD/jUp82dY9UHzZwH3BI4G5rJ03pW1W/IeFlVxBX318ooGzubFlP
BbA2sGRavytQOrL7VypIRVFG4kmfTM9Lv2AfX03aX79i72HfZR8gPmFPflIm0DxQOoUm0AtgG8Jv
DxwQJyEE9AWxKDM0OBg1MCkt8B8Rb2YgtyjxG9BN6UEG4AAgQwhw/wlwAjBmiWWPZp9nr2izP+P/
aV9qb2t/bI9tn26vb79GqH9DgV2fSKh6DGQPeHwko1Q9IyFrBCACEAXALiBscHouJJtjAEEMMBRw
G/BUDFRPIXAgwGQ2SFK0IEcG0Eg+tS2wVCHQASbQMDcwNDQgNCw2LQoRMGVIBiJSZT8N4C4gH9BF
0T6lgwsxOTozJJRMhOAooAXARFb2TySVgdFsCcABoAnwHNBrKPCBwWYbgDGDkEFjRkRheIM4MjY2
JJQ3tQ4gOYFARgUQBvB6LiCLB3A+tWgCQHA6d41Awi4gkGVoci4BAIBnFwLRMGUWkQCPcAADAAGA
CCAGAAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAOFAAAA
AAAAAwAJgAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAADADWACCAGAAAAAADAAAAAAAAARgAA
AABShQAAjmoBAB4ANoAIIAYAAAAAAMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAALADeACCAG
AAAAAADAAAAAAAAARgAAAAAGhQAAAAAAAAsAO4AIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAA
AwA8gAggBgAAAAAAwAAAAAAAAEYAAAAAEYUAAAAAAAADAD6ACCAGAAAAAADAAAAAAAAARgAAAAAY
hQAAAAAAAB4ATIAIIAYAAAAAAMAAAAAAAABGAAAAADaFAAABAAAAAQAAAAAAAAAeAE2ACCAGAAAA
AADAAAAAAAAARgAAAAA3hQAAAQAAAAEAAAAAAAAAHgBOgAggBgAAAAAAwAAAAAAAAEYAAAAAOIUA
AAEAAAABAAAAAAAAAAsAVIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAAAAAgH4DwEAAAAQAAAA
SJ6jo6C60hG9wQAQWj1p8wIB+g8BAAAAEAAAAEieo6OgutIRvcEAEFo9afMCAfsPAQAAAFcAAAAA
AAAAOKG7EAXlEBqhuwgAKypWwgAAUFNUUFJYLkRMTAAAAAAAAAAATklUQfm/uAEAqgA32W4AAABG
OlxPdXRsb29rLkFyY2hpdlxvdXRsb29rLnBzdAAAAwD+DwUAAAADAA00/TcAAAIBfwABAAAAKwAA
ADxOQ0JCTE5NQkVJSU9QSkpPTUpFSk9FQkJESUFBLmhyQHdvZWhyLmRlPgAAAwAGEOMi6IADAAcQ
pQQAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABJV0FOVFRPVVNFTEFSR0VPQkpFQ1RTSU5Q
T1NUR1JFU1FMLFNPVVJDRUlTQVBFUkwtU0NSSVBUQlVUSU5VTkNIQUlORURNT0RFSVRXT060VFdP
UktXSEFURUxTRVNIT1VMRElEAAAAAKhb

------=_NextPart_000_001E_01BF4244.2E77DD80--

From bouncefilter Thu Dec 9 07:41:02 1999
Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA04516
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 07:40:44 -0500 (EST)
(envelope-from rison@biochemistry.ucl.ac.uk)
Received: from biochem.ucl.ac.uk (actually host bsmori1.biochem.ucl.ac.uk)
by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP;
Thu, 9 Dec 1999 12:40:21 +0000
Received: from bsmlx17.biochem.ucl.ac.uk (bsmlx17 [128.40.46.142]) by
biochem.ucl.ac.uk (8.9.2/8.9.1)
with ESMTP id MAA02687; Thu, 9 Dec 1999 12:40:34 GMT
Received: from localhost (rison@localhost)
by bsmlx17.biochem.ucl.ac.uk (8.9.3/8.6.6) with ESMTP id MAA05895;
Thu, 9 Dec 1999 12:49:24 GMT
X-Authentication-Warning: bsmlx17.biochem.ucl.ac.uk: rison owned process doing
-bs
Date: Thu, 9 Dec 1999 12:49:24 +0000 (GMT)
From: Stuart Rison <rison@biochemistry.ucl.ac.uk>
X-Sender: rison@bsmlx17
To: Dev Elop <dev@archonet.com>
cc: pgsql-general <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] get the previous assigned sequence value
In-Reply-To: <00e301bf4231$4a586140$1001a8c0@client>
Message-ID: <Pine.LNX.4.10.9912091243580.5807-100000@bsmlx17>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Thu, 9 Dec 1999, Dev Elop wrote:

After an INSERT, I want to retrieve the value of the sequence I use for
unique_ids

...

Alternatively, use the currval(mytable_id_seq) function within the same
session immediately after the insert.

With this second method, you'd probably need to beware race conditions. If
another process inserts a record into mytable after you do but before you
call currval(), then you'll get the wrong value.

Not an issue if you've only got one process accessing the table - probably
is one if you have two or more.

I don't think that's true the currval belongs to the process (as it were)
so that what happens is that currval remains unchanged by inserts by other
processes.

nextval however is 'affected' meaning that nextval won't just return
curval+1, it returns whatever the next sequence item is taking into
account the increasses caused by other processes.

at least I seem to remember that from previous postings... any seconders?

Cheers,

From bouncefilter Thu Dec 9 08:14:02 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id IAA07909
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 08:13:35 -0500 (EST)
(envelope-from szi@khs-ag.de)
Received: (qmail 25326 invoked from network); 9 Dec 1999 13:09:19 -0000
Received: from intra.do.khs-ag.de (HELO intra.do.khs-ag.de.khs-ag.de)
(10.133.122.3)
by intra.do.khs-ag.de with SMTP; 9 Dec 1999 13:09:19 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: operator *=
From: Sascha Ziemann <szi@khs-ag.de>
Date: 09 Dec 1999 14:09:18 +0100
Message-ID: <m3emcw9s75.fsf@intra.do.khs-ag.de>
Lines: 38
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

I have two tables "user_t" and "email_alias_t". The "user_t" table
has the two fields "last_name" and "linux_login" and the
"email_alias_t" table has the two fields "login" and "alias".

In some rows in the "user_t" table the entry "linux_login" is NULL.

Now I need all rows from "user_t" and for those rows which have a
"linux_login" I need the "alias" column from "email_alias_t".

My SQL book descibes the *= operator which should be used for those
queries but Postgres does not have it. I found out that it is
possible to do the select with a union. This union:

select last_name, direct_inward_number, linux_login, alias
from user_t, email_alias_t
where last_name LIKE 'Ni%' AND linux_login = login
union
select last_name, direct_inward_number, linux_login, linux_login
from user_t
where last_name LIKE 'Ni%' AND linux_login = NULL
order by 1;

produces the right output:

last_name|direct_inward_number|linux_login|alias
---------+--------------------+-----------+-----------------
Niebisch | 2608|jni00514 |niebisch.jaroslaw
Niena� | 1365| |
Nilles | 2478|pni00423 |nilles.peter
Nix | 2358|yni00155 |nix.yvonne

My question: Is such a union the only way to emulate the *= operator
in Postgres or is there a better way?

bis sp�ter...
Sascha

From bouncefilter Thu Dec 9 08:23:03 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA08843
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 08:22:59 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id PAA00836; Thu, 9 Dec 1999 15:27:10 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
PAA29452; Thu, 9 Dec 1999 15:22:56 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <384FAD30.45D7DD03@albourne.com>
Date: Thu, 09 Dec 1999 15:22:56 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
CC: Dev Elop <dev@archonet.com>, pgsql-general <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] get the previous assigned sequence value
References: <Pine.LNX.4.10.9912091243580.5807-100000@bsmlx17>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

With this second method, you'd probably need to beware race conditions. If
another process inserts a record into mytable after you do but before you
call currval(), then you'll get the wrong value.

Not an issue if you've only got one process accessing the table - probably
is one if you have two or more.

I don't think that's true the currval belongs to the process (as it were)
so that what happens is that currval remains unchanged by inserts by other
processes.

nextval however is 'affected' meaning that nextval won't just return
curval+1, it returns whatever the next sequence item is taking into
account the increasses caused by other processes.

at least I seem to remember that from previous postings... any seconders?

currval always gives you the most recent sequence value returned by your
own back-end, so that it is not affected by waht other processes do.
With nextval it also depends on what cache size you chose. If youchose
1, the default, nextval is directly affected by whether other processes
have doena nextval. If the caches is larger this is not necessarily the
case.

Adriaan

From bouncefilter Thu Dec 9 08:43:02 1999
Received: from ara.zf.jcu.cz (zakkr@ara.zf.jcu.cz [160.217.161.4])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA11077
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 08:42:35 -0500 (EST)
(envelope-from zakkr@zf.jcu.cz)
Received: from localhost (zakkr@localhost)
by ara.zf.jcu.cz (8.9.3/8.9.3/Debian/GNU) with SMTP id OAA05612;
Thu, 9 Dec 1999 14:28:29 +0100
Date: Thu, 9 Dec 1999 14:28:28 +0100 (CET)
From: Karel Zak - Zakkr <zakkr@zf.jcu.cz>
To: Sascha Ziemann <szi@khs-ag.de>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] operator *=
In-Reply-To: <m3emcw9s75.fsf@intra.do.khs-ag.de>
Message-ID: <Pine.LNX.3.96.991209142041.3593C-100000@ara.zf.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 9 Dec 1999, Sascha Ziemann wrote:

Hi,

I have two tables "user_t" and "email_alias_t". The "user_t" table
has the two fields "last_name" and "linux_login" and the
"email_alias_t" table has the two fields "login" and "alias".

In some rows in the "user_t" table the entry "linux_login" is NULL.

Now I need all rows from "user_t" and for those rows which have a
"linux_login" I need the "alias" column from "email_alias_t".

My SQL book descibes the *= operator which should be used for those
queries but Postgres does not have it. I found out that it is
possible to do the select with a union. This union:

In the PostgreSQL exist a operator *= , but is used for a array
(text[] ..etc), (now is distributed in the contrib tree).

I not sure, if I good undertend you, but good resolution for your
problem is prabably JOIN. But it not implement in PgSQL now
(it will in 7.0) :-(

Karel

From bouncefilter Thu Dec 9 09:22:02 1999
Received: from do.khs-ag.de (gate2.khs-ag.de [195.138.58.218])
by hub.org (8.9.3/8.9.3) with SMTP id JAA15207
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 09:21:39 -0500 (EST)
(envelope-from szi@khs-ag.de)
Received: (qmail 30861 invoked from network); 9 Dec 1999 14:17:08 -0000
Received: from intra.do.khs-ag.de (HELO intra.do.khs-ag.de.khs-ag.de)
(10.133.122.3)
by intra.do.khs-ag.de with SMTP; 9 Dec 1999 14:17:08 -0000
Sender: szi@intra.do.khs-ag.de
To: pgsql-general@postgresql.org
Subject: Function arguments
From: Sascha Ziemann <szi@khs-ag.de>
Date: 09 Dec 1999 15:17:08 +0100
Message-ID: <m3r9gw8ahn.fsf@intra.do.khs-ag.de>
Lines: 7
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

is there a way to define a function, that accepts a TEXT value and
NULL as an argument?

bis sp�ter...
Sascha

From bouncefilter Thu Dec 9 09:38:05 1999
Received: from photon.skillbrokers.bg (root@[195.24.42.194])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA17205
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 09:37:06 -0500 (EST)
(envelope-from nmmm@nmmm.nu)
Received: from niki (proton.skillbrokers.bg [195.24.42.206])
by photon.skillbrokers.bg (8.9.0/8.9.0) with SMTP id QAA07111;
Thu, 9 Dec 1999 16:28:05 +0200
Message-ID: <002001bf4252$a9051fa0$ce2a18c3@skillbrokers.bg>
From: "Nikolay Mijaylov" <nmmm@nmmm.nu>
To: "Adriaan Joubert" <a.joubert@albourne.com>
Cc: "pgsql-general" <pgsql-general@postgreSQL.org>
References: <Pine.LNX.4.10.9912091243580.5807-100000@bsmlx17>
<384FAD30.45D7DD03@albourne.com>
Subject: Re: [GENERAL] get the previous assigned sequence value
Date: Thu, 9 Dec 1999 16:35:35 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Why you discuss it????
The problem is quite clean and it was solvev many years ago.....

1. Get the *next* sequence value:
select nextval("gogo_seq");
2. Store it into a variable (for example $X)
3. Insert proper data (and and sequence value)
insert into gogo values( $X, 'NMMM', 'mailto:nmmm@nmmm.nu');
4. Use value $X, as u want
insert into gogo_detail values( $X, 'bla bla0');
insert into gogo_detail values( $X, 'bla bla1');
insert into gogo_detail values( $X, 'bla bla2');

Am I clear?

nmmm
--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

----- Original Message -----
From: Adriaan Joubert <a.joubert@albourne.com>
Cc: Dev Elop <dev@archonet.com>; pgsql-general
<pgsql-general@postgreSQL.org>
Sent: 09 �� 1999 �. 15:22
Subject: Re: [GENERAL] get the previous assigned sequence value

With this second method, you'd probably need to beware race

conditions. If

another process inserts a record into mytable after you do but before

you

call currval(), then you'll get the wrong value.

Not an issue if you've only got one process accessing the table -

probably

is one if you have two or more.

I don't think that's true the currval belongs to the process (as it

were)

so that what happens is that currval remains unchanged by inserts by

other

processes.

nextval however is 'affected' meaning that nextval won't just return
curval+1, it returns whatever the next sequence item is taking into
account the increasses caused by other processes.

at least I seem to remember that from previous postings... any

seconders?

currval always gives you the most recent sequence value returned by your
own back-end, so that it is not affected by waht other processes do.
With nextval it also depends on what cache size you chose. If youchose
1, the default, nextval is directly affected by whether other processes
have doena nextval. If the caches is larger this is not necessarily the
case.

Adriaan

************

From bouncefilter Thu Dec 9 10:30:03 1999
Received: from smtp1.volny.cz (smtp1.volny.cz [212.20.96.10])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA23454
for <pgsql-general@hub.org>; Thu, 9 Dec 1999 10:29:19 -0500 (EST)
(envelope-from davids@penguin.cz)
Received: from chameleon.localdomain ([195.250.157.253])
by smtp1.volny.cz (8.9.3/8.9.3) with ESMTP id QAA82279
for <pgsql-general@hub.org>; Thu, 9 Dec 1999 16:29:11 +0100 (CET)
X-Envelope-To: <pgsql-general@hub.org>
Received: (from david@localhost)
by chameleon.localdomain (8.9.3/8.9.3) id QAA01442;
Thu, 9 Dec 1999 16:29:10 +0100
X-Authentication-Warning: chameleon.localdomain: david set sender to
davids@penguin.cz using -f
Sender: david@chameleon.localdomain
To: pgsql-general@hub.org
Subject: Setting of locales at runtime ?
From: David Sauer <davids@penguin.cz>
Date: 09 Dec 1999 16:25:46 +0100
Message-ID: <m2zovkf85h.fsf@chameleon.localdomain>
User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Arches)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 21

Hi,

I have question about postgres: it is possible (or planned) to change
locales (and sorting) at runtime ? For example, I will have 2 tables, in 2
different languages. I want following:

set locale cs;
select * from table1 order by 1; // this will sort by first column
// and use czech locale

set locale es;
select * from table2 order by 2; // this will sort using spanish locale

thanks,

David

--
* David Sauer, student of Czech Technical University
* electronic mail: davids@penguin.cz (mime compatible)

From bouncefilter Thu Dec 9 16:15:08 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id QAA08372
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 16:14:25 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id 99E241F85; Thu, 9 Dec 1999 16:13:26 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id 8637B1F75
for <pgsql-general@postgresql.org>;
Thu, 9 Dec 1999 16:13:26 +0000 (GMT)
Date: Thu, 9 Dec 1999 16:13:26 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: using limit instead of seeking
Message-ID: <Pine.BSF.4.10.9912091610320.8952-100000@server.b0x.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Would there be any reasonable performance gain in using LIMIT in an sql
query to print pages of results, instead of seeking to the desired record
and printing a number of records in a while loop?

I have tried both options, but I cannot perceive any significant change in
performance. Is there a way I can actuall test or predict the usefulness
of using one alternative over the other? I am also using SORT in my sql
queries, so perhaps the db server will have to retrieve all records
beforehand anyways in order to perform the sort. In such a case, I guess
using LIMIT wouldn't make much of a difference. On the other hand, there
are perhaps cases when using LIMIT would make a difference.

Any guidance would be appreciated to solving this problem.
Thanks in advance,
Marc

From bouncefilter Thu Dec 9 11:25:16 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA32639
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 11:24:20 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11w6Mc-000LEEC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Thu, 9 Dec 1999 10:24:18 -0600 (CST)
Date: Thu, 9 Dec 1999 10:24:18 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
Message-ID: <19991209102418.A6311@rice.edu>
References: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
<Pine.LNX.4.20.9912090111190.389-100000@localhost.localdoma in>
<3.0.5.32.19991209092335.008f62c0@pop.mecomb.po.my>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <3.0.5.32.19991209092335.008f62c0@pop.mecomb.po.my>;
from lylyeoh@mecomb.com on Thu, Dec 09, 1999 at 09:23:35AM +0800

Hmm, sounds like a vote for nested transactions. The JDBC driver developer
(Peter Mount) was musing that nested transaction would make large object
support easier for him, as well.

As to the other example of Oracle not forcing a rollback, I have a feeling
that this may be specific to syntax errors in an interactive session.
Implementing this sort of behavior has been discussed recently on the
hackers list, in the context of making it easier to work interactively
inside a transaction.

I would be surprised if Oracle allows non-syntax errors inside a
transaction to be ignored, or ignores anything in a non-interactive
session. How about testing an example like links, where you provide data
in a format the backend can't handle, (an out of range int or date or
something) and see how Oracle handles that.

Who's right? Well, as Peter Eisentraut said, what Postgres implements is
the _definition_ of a transaction: all together, or nothing at all. This
isn't just an arbitrary rule: the validity of the relational calculus
depends on transactional semantics.

Ross

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Thu, Dec 09, 1999 at 09:23:35AM +0800, Lincoln Yeoh wrote:

At 01:18 AM 09-12-1999 +0100, Peter Eisentraut wrote:

Seriously, why do you use a transaction, when you don't want any errors
caught? Transactions are defined as everything succeeds or nothing goes.
If you want update to succeed anyhow, put it in it's own transaction
(i.e., commit before it).

I want errors caught, most errors abort everything but some errors I want
to try a different update instead, if that doesn't work then only rollback
everything.

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

The safest way would be to set a date format with SET DATESTYLE TO and use
that, possibly assisted by library formatting routines.

OK.

Link.

************

From bouncefilter Thu Dec 9 11:36:04 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA34617
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 11:35:44 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11w6XU-000LEEC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Thu, 9 Dec 1999 10:35:32 -0600 (CST)
Date: Thu, 9 Dec 1999 10:35:32 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: Dev Elop <dev@archonet.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] get the previous assigned sequence value
Message-ID: <19991209103532.B6311@rice.edu>
References: <Pine.LNX.4.10.9912081639280.11761-100000@mercury.shreve.net>
<384F2CE4.115503C@austin.rr.com>
<00e301bf4231$4a586140$1001a8c0@client>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <00e301bf4231$4a586140$1001a8c0@client>;
from dev@archonet.com on Thu, Dec 09, 1999 at 10:36:40AM -0000

Gah, this is getting a bit annoying, correcting this bit of
mis-information.

currval() is kept as part of the session context, as is completely
multi-user safe. That's why the person you quoted said 'in the same
session'.

Where is everyone coming up with the wrong idea on this? Is there a
major commercial DB with sequence objects that gets this wrong?

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Thu, Dec 09, 1999 at 10:36:40AM -0000, Dev Elop wrote:

After an INSERT, I want to retrieve the value of the sequence I use for
unique_ids

...

Alternatively, use the currval(mytable_id_seq) function within the same
session immediately after the insert.

With this second method, you'd probably need to beware race conditions. If
another process inserts a record into mytable after you do but before you
call currval(), then you'll get the wrong value.

Not an issue if you've only got one process accessing the table - probably
is one if you have two or more.

-
Richard Huxton

************

From bouncefilter Thu Dec 9 10:49:03 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA26279
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 10:48:38 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id KAA27763;
Thu, 9 Dec 1999 10:44:32 -0600
Date: Thu, 9 Dec 1999 10:44:32 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Hans.Reichenecker@woehr.de
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Error: Using Large Objects by perl5-Interface
In-Reply-To: <NCBBLNMBEIIOPJJOMJEJOEBBDIAA.hr@woehr.de>
Message-ID: <Pine.LNX.4.10.9912091040260.27698-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.org id KAA26295

in your perl script:
$dbh->{AutoCommit}=0;

you can get more info by perldoc DBI and perldoc DBD::Pg

On Thu, 9 Dec 1999, Hans Reichenecker wrote:

I want to use Large Objects in PostgreSQL, source is a Perl-Script. But in
unchained mode it won�t work. What else should I do to change in chained
mode ?

Users-Guide: "By default, Postgres executes transactions in
unchained mode (also known as "autocommit" in other database systems)."

Source:
$result = $conn->exec("BEGIN");
$stoeroid = $conn->lo_creat( 'PGRES_INV_ARCHIVE');
$stoeroidlen = $conn->lo_write( $stoeroid, $Meldung, length(
$Meldung));
$ERRor = $conn->lo_close( $stoeroid);
$result = $conn->exec("END");

results in Debug-Backend
query: BEGIN
ProcessUtility: BEGIN
CommitTransactionCommand
StartTransactionCommand
query: select proname, oid from pg_proc where proname = 'lo_open' or
proname = 'lo_close' or proname = 'lo_creat' or proname = 'lo_unlink'
or proname = 'lo_lseek' or proname = 'lo_tell' or proname = 'loread'
or proname = 'lowrite'
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
CommitTransactionCommand
StartTransactionCommand
ERROR: lo_write: large obj descriptor (34850) out of range
AbortCurrentTransaction
StartTransactionCommand
ERROR: lo_close: large obj descriptor (34850) out of range
AbortCurrentTransaction
StartTransactionCommand
query: END
ProcessUtility: END
CommitTransactionCommand

Thanks for help.

OTTO W�HR GmbH Tel: 07044 46-0
Hans Reichenecker Tel: 07044 46193
Leiter DVO
�lgrabenstra�e 14 Fax: 07044 46266
71292 Friolzheim http:www.woehr.de

From bouncefilter Thu Dec 9 11:52:04 1999
Received: from web2106.mail.yahoo.com (web2106.mail.yahoo.com [128.11.68.250])
by hub.org (8.9.3/8.9.3) with SMTP id LAA37162
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 11:51:54 -0500 (EST)
(envelope-from psrajan@yahoo.com)
Received: (qmail 3745 invoked by uid 60001); 9 Dec 1999 16:49:08 -0000
Message-ID: <19991209164908.3744.qmail@web2106.mail.yahoo.com>
Received: from [205.172.146.235] by web2106.mail.yahoo.com;
Thu, 09 Dec 1999 08:49:08 PST
Date: Thu, 9 Dec 1999 08:49:08 -0800 (PST)
From: soundar rajan <psrajan@yahoo.com>
Subject: JDBC2.0 and pg
To: pgsql-general@postgreSQL.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hi all,

Any idea whether pg6.5.3 supports (all functions) of
JDBC 2.0 API ?

=====
Thanks.
Soundar.
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

From bouncefilter Thu Dec 9 11:51:04 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA37034
for <pgsql-general@hub.org>; Thu, 9 Dec 1999 11:50:20 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
LAA26932;
Thu, 9 Dec 1999 11:50:13 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912091650.LAA26932@candle.pha.pa.us>
Subject: Re: [GENERAL] Problems with pg_dump
In-Reply-To: <009e01bf4283$a1992320$6400a8c0@rainbowsend.ns.ca> from Peter
Bojanic at "Dec 9, 1999 12:26:09 pm"
To: Peter Bojanic <pbojanic@pictorius.com>
Date: Thu, 9 Dec 1999 11:50:13 -0500 (EST)
CC: pgsql-general@hub.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

[Charset iso-8859-1 unsupported, filtering to ASCII...]

I'm running Postgresql 6.5.3 on RedHat Linux 6.0.

When I try to use pg_dump:

# pg_dump mmt

I get the following error message:

pg_dump: couldn't find the template1 database. You are really hosed. Giving
up.

Both my database, "mmt" and the "template1" database are present and I can
connect to them with psql and query against them. I've got another Linux
system with the same configuration and pg_dump works fine.

Any suggestions or similar experiences?

Connect to template1 database, and do 'select * from pg_database' If
there is more than one template1, delete it by using it's oid, and try
the dump again. 6.6/7.0 will fix this.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 9 11:00:03 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA28113
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 10:59:28 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id KAA28281;
Thu, 9 Dec 1999 10:55:18 -0600
Date: Thu, 9 Dec 1999 10:55:18 -0600 (CST)
From: <kaiq@realtyideas.com>
To: greg@proterians.net
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] parse error ???
In-Reply-To: <Pine.LNX.4.05.9912091122410.18605-100000@proterians.net>
Message-ID: <Pine.LNX.4.10.9912091049190.27698-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

cast is not necessarily extract, if you really want portablility,
use extract(), which is sql92.

select extract (day from d1) from datetime_tbl;

On Thu, 9 Dec 1999 greg@proterians.net wrote:

I have one question...

Why postgres returns parse error when i send

select birth_time::date from table;

parse error at or near ":"

I use CBuilder4 and postODBC driver...

when I write

select date(birth_time) from table;

it works...

but in DataBaseExplorer the first query works fine....

please help....

--Greg--

************

From bouncefilter Thu Dec 9 12:59:43 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA07580
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 12:59:38 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.226]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Thu, 9 Dec 1999 11:51:08 -0600
Sender: ed
Message-ID: <384FED8C.CF02D1FE@austin.rr.com>
Date: Thu, 09 Dec 1999 11:57:32 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: Dev Elop <dev@archonet.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] get the previous assigned sequence value
References: <Pine.LNX.4.10.9912081639280.11761-100000@mercury.shreve.net>
<384F2CE4.115503C@austin.rr.com>
<00e301bf4231$4a586140$1001a8c0@client>
<19991209103532.B6311@rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Ross J. Reedstrom" wrote:

Gah, this is getting a bit annoying, correcting this bit of
mis-information.

currval() is kept as part of the session context, as is completely
multi-user safe. That's why the person you quoted said 'in the same
session'.

Where is everyone coming up with the wrong idea on this? Is there a
major commercial DB with sequence objects that gets this wrong?

I think it is primarily because (a) it is intuitive to think there is a race
condition, which fortunately psgql folks have gone to significant efforts to
avoid, and (b) the documentation at

http://www.postgresql.org/docs/postgres/sql-createsequence.htm

is less than concise/clear on this issue.

Same thing is true for the question of how to retrieve the newly-inserted
serial, which is why people keep asking the same question over and over (that,
and because people don't know about www.deja.com or the mailing list search
engine...or the engine is broken).

Cheers.
Ed

From bouncefilter Thu Dec 9 13:24:43 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA12582
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 13:24:29 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
NAA00275;
Thu, 9 Dec 1999 13:23:44 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912091823.NAA00275@candle.pha.pa.us>
Subject: Re: [GENERAL] get the previous assigned sequence value
In-Reply-To: <384FED8C.CF02D1FE@austin.rr.com> from Ed Loehr at "Dec 9, 1999
11:57:32 am"
To: Ed Loehr <ELOEHR@austin.rr.com>
Date: Thu, 9 Dec 1999 13:23:44 -0500 (EST)
CC: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dev Elop <dev@archonet.com>, pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I think it is primarily because (a) it is intuitive to think there is a race
condition, which fortunately psgql folks have gone to significant efforts to
avoid, and (b) the documentation at

http://www.postgresql.org/docs/postgres/sql-createsequence.htm

is less than concise/clear on this issue.

Same thing is true for the question of how to retrieve the newly-inserted
serial, which is why people keep asking the same question over and over (that,
and because people don't know about www.deja.com or the mailing list search
engine...or the engine is broken).

My book will cover that in detail.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 16 08:20:52 1999
Received: from news.tht.net (news.hub.org [216.126.91.242])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA15885
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 08:20:29 -0500 (EST)
(envelope-from news@news.tht.net)
Received: (from news@localhost) by news.tht.net (8.9.3/8.9.3) id IAA59681
for pgsql-general@postgresql.org; Thu, 16 Dec 1999 08:17:35 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: news.tht.net: news set sender to <news> using -f
From: "M.E. Versteeg" <actofgod@chello.nl>
X-Newsgroups: comp.databases.postgresql.questions
Subject: How is the Query for 3 highest ranking values ?
Lines: 13
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <SNS34.3350$uG.44216@typhoon.chello.nl>
Date: Thu, 09 Dec 1999 18:46:10 GMT
X-Complaints-To: newsmaster@chello.nl
X-Trace: typhoon.chello.nl 944765170 212.187.42.133 (Thu,
09 Dec 1999 19:46:10 MET)
Organization: "Chello Netherlands"
To: pgsql-questions@postgresql.org

I want to retrieve the 3 highest salaries on my SQL database.
Empno. Salary
(key)

How is the query for this?

It would be appreciated, if anyone could send/post the query?

Caio!

From bouncefilter Thu Dec 9 14:19:15 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA02803
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 14:18:50 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from picasso.realtyideas.com (kaiq@207-18-128-210.flex.net
[207.18.128.210]) by trends.net (8.8.8/8.8.8) with ESMTP id NAA11893
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 13:49:58 -0500 (EST)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id NAA31073;
Thu, 9 Dec 1999 13:26:32 -0600
Date: Thu, 9 Dec 1999 13:26:32 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Ed Loehr <ELOEHR@austin.rr.com>
cc: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
Dev Elop <dev@archonet.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] get the previous assigned sequence value
In-Reply-To: <384FED8C.CF02D1FE@austin.rr.com>
Message-ID: <Pine.LNX.4.10.9912091317100.30180-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Orakle's fault :-) I remembered there was a thorough (very thorough)
discussion months before. This raises a question: because the web
based search engine is slow, why can't setup a text file achive?
so that people can ftp the big file and use vi do whatever they
want locally? does using the search engine increase potential value
to the site? if in that case, I'd better shut up ;-), but I can not
see any, it is rather a load burden. perhaps some commercialization
plan for future?

On Thu, 9 Dec 1999, Ed Loehr wrote:

"Ross J. Reedstrom" wrote:

Gah, this is getting a bit annoying, correcting this bit of
mis-information.

currval() is kept as part of the session context, as is completely
multi-user safe. That's why the person you quoted said 'in the same
session'.

Where is everyone coming up with the wrong idea on this? Is there a
major commercial DB with sequence objects that gets this wrong?

I think it is primarily because (a) it is intuitive to think there is a race
condition, which fortunately psgql folks have gone to significant efforts to
avoid, and (b) the documentation at

http://www.postgresql.org/docs/postgres/sql-createsequence.htm

is less than concise/clear on this issue.

Same thing is true for the question of how to retrieve the newly-inserted
serial, which is why people keep asking the same question over and over (that,
and because people don't know about www.deja.com or the mailing list search
engine...or the engine is broken).

Cheers.
Ed

************

From bouncefilter Thu Dec 9 04:45:59 1999
Received: from intercept-india.com (intercep@intercept-india.com
[192.41.37.131]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA86284
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 04:45:49 -0500 (EST)
(envelope-from kimi@intercept.co.in)
Received: from vsnl.net.in ([202.9.149.131]) by intercept-india.com (8.8.5) id
CAA13551; Thu, 9 Dec 1999 02:45:43 -0700 (MST)
Message-Id: <199912090945.CAA13551@intercept-india.com>
X-Authentication-Warning: intercept-india.com: Host [202.9.149.131] claimed to
be vsnl.net.in
From: "V Krishnaraj" <kimi@intercept.co.in>
To: pgsql-general@postgreSQL.org
Date: Thu, 9 Dec 1999 15:22:07 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Please help with these error messages
Priority: normal
X-mailer: Pegasus Mail for Win32 (v3.01b)

Dear Community need your help once again:

We are running on one installation 2 databases: one for tracking
any activity on a site another for serving out ads based on certain
targeting parameters.

The OS is Linux and the Web Server is Apache

We keep getting around 5-7 requests / sec and activity involves
continuous read and writes into the databases.

Now for some unknown reasons ( I mean unknown to us !!!)
postmaster keeps shutting off..We worked on it for a while and
found one apparent reason to be corrupted data being written...we
rectified that..and now we find that postgres shuts itself off with the
following error messages:

=====

IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
size=120, permi
ssion=700
IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010,
size=120, permis
sion=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1: AttachSLockMemory: could not attach segment

=====

On another occasion we got the following error message:

SISegmentGet: failed: Identifier removed
FATAL 1: CreateSharedInvalidationState: failed segment init
ERROR: cannot open segment 1 of relation sessions_index1
NOTICE: LockReleaseAll: xid table corrupted

FATAL: s_lock(4017aaa4) at bufmgr.c:665, stuck spinlock.
Aborting.

FATAL: s_lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
NOTICE: LockReleaseAll: xid loop detected, giving up
pq_flush: send() failed: Bad file descriptor

=====

Please help.

Also, I wanted to have a quick check on using Postgresql. We are
planning to use it as a large scale adserver where one installation
could need to handle about 75 requests per second on a 24 / 7
basis. This means picking parameters from an HTTP requests
making 5 SELECTS, 25 reads and 5 writes...concurrency issues
already taken care off.

Thanks for taking time off to write to this one.

Kimi

From bouncefilter Thu Dec 9 11:25:05 1999
Received: from the_tower.pictorius.com (cpx.pictorius.com [192.219.29.90] (may
be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id LAA32981
for <pgsql-general@hub.org>; Thu, 9 Dec 1999 11:25:04 -0500 (EST)
(envelope-from pbojanic@pictorius.com)
Received: from bojanic [154.5.34.103] by the_tower.pictorius.com
(SMTPD32-5.04) id A81D660298; Thu, 09 Dec 1999 12:26:05 -0300
Message-ID: <009e01bf4283$a1992320$6400a8c0@rainbowsend.ns.ca>
From: "Peter Bojanic" <pbojanic@pictorius.com>
To: <pgsql-general@hub.org>
Subject: Problems with pg_dump
Date: Thu, 9 Dec 1999 12:26:09 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

I'm running Postgresql 6.5.3 on RedHat Linux 6.0.

When I try to use pg_dump:

# pg_dump mmt

I get the following error message:

pg_dump: couldn't find the template1 database. You are really hosed. Giving
up.

Both my database, "mmt" and the "template1" database are present and I can
connect to them with psql and query against them. I've got another Linux
system with the same configuration and pg_dump works fine.

Any suggestions or similar experiences?

----------
Peter Bojanic, VP Professional Services, Pictorius Incorporated
URL: http://www.pictorius.com; Phone: (902) 492-2880 x223; Fax: (902)
492-3409

From bouncefilter Thu Dec 9 20:24:06 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA23382
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 20:24:00 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:64807 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sI3MH184363>; Fri, 10 Dec 1999 02:23:31 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11wErR-0000DE-00; Fri, 10 Dec 1999 02:28:41 +0100
Date: Fri, 10 Dec 1999 02:28:41 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Mark Dalphin <mdalphin@amgen.com>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Suggested "minor" change to psql
In-Reply-To: <384E9D82.CCC45186@amgen.com>
Message-ID: <Pine.LNX.4.20.9912090130100.389-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-08, Mark Dalphin mentioned:

Sometimes, however, rather than using the "\i" command, I would like to simply
load my schema directly into psql and capture the output on STDOUT (ie "psql <
mySchema.sql >& myOutput"). The problem that arises is that the errors and
notices all come out on STDERR. I am not sure this is the right choice. Because
of the lack of synchronization between STDOUT and STDERR, it becomes impossible
to associate an SQL statement with either a CREATE or an ERROR message. The
option, "-e", is supposed to echo the query, but it doesn't help.

You might be glad to hear that I've been addressing these issues. The way
it currently looks is that everything that is related to backend traffic
(query results, INSERT xxx, notices, errors) will all go to the same
stream (the \o one) in the order they arrive. I think this is what
everyone wanted. If you are running interactively, it doesn't make a
difference anyway, but in a automated script you'll rarely have the need
to have the errors without the commands that caused them.

The only thing that will keep going to stderr are fatal notices from psql
itself. The only thing that always goes to stdout is psql internal
messages ("Turned on expanded mode.").

One additional feature that's coming up, which you might like, is the
possibility to stop such a psql script after the first error it
encounters.

While I can see wanting to separate STDERR and STDOUT when one uses psql to run
an SQL query against a DB from within a shell script, it makes it much more
difficult when developing, and if I were to run several SQL queries into psql,
exactly the same association problem would occur.

You can check the return code and decide what to do with the output that
way.

Perhaps a combination of the function "isatty()" plus the -e flag would work? So
that if STDOUT "isatty()" then echo errors to STDOUT, otherwise send them to
STDERR. And if the -e flag is set, echo the queries to STDERR, so the
correlation between ERROR, CREATE, etc and SQL could be made.

There are already about 4 or 5 different output sources and 2 or 3 states
controlling them; I'm hesitant to adding more confusion, especially
subtle things.

Also, the meaning of the -e flag has been adjusted. In interactive mode it
doesn't do anything, in script mode it prints every line as it reads it.
If you don't give it, you don't see the code of your script. That is more
like a regular shell.

PS I only recently learned of the setting of the PAGER environment variable to
make it so I needn't scroll back up 400 lines to find my errors; perhaps this
could be made more prominent in the documentation as it would be a big help.

That part has been changed, because the purpose of the PAGER environment
variable in general is not to toggle the use of the pager in psql. There
is now an internal switch.

Then again, perhaps I should completely re-read the docs to see if this is
mentioned; I haven't done that for several releases now.

Well, I rewrote the complete manual, so you're in for a great work of
literature. :)

When will you be able to reach this promised land? You could start by
flaming the hackers list about a 6.6 release in Feb/Mar ... ;)

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Thu Dec 9 22:13:55 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA03316
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 22:13:51 -0500 (EST)
(envelope-from oexel@economatica.com.br)
Received: from queluz.economatica.com.br (mail@queluz.economatica.com.br
[200.231.195.36]) by trends.net (8.8.8/8.8.8) with ESMTP id VAA02435
for <pgsql-general@postgresql.org>; Thu, 9 Dec 1999 21:00:10 -0500 (EST)
Received: from oexel by queluz.economatica.com.br with local (Exim 2.05 #1
(Debian)) id 11wFFZ-0000BP-00; Thu, 9 Dec 1999 23:53:37 -0200
Date: Thu, 9 Dec 1999 23:53:37 -0200
From: Otavio Exel <oexel@economatica.com.br>
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Suggested "minor" change to psql
Message-ID: <19991209235337.F26171@economatica.com.br>
Reply-To: oexel@economatica.com.br
References: <93C04F1F5173D211A27900105AA8FCFC29949C@lambic.prevuenet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <93C04F1F5173D211A27900105AA8FCFC29949C@lambic.prevuenet.com>;
from Michael J Davis on Wed, Dec 08, 1999 at 12:27:41PM -0600
Organization: Economatica Ltda

Michael J Davis wrote:

Try:

psql < mySchema.sql >& myOutput 2> myOutput.err

or (assuming you use bash)

psql < mySchema.sql > myOutput 2>&1

to have stdout & stderr together and 'in sync' sent to myOutput

beers,

--
Otavio Exel /<\oo/>\ oexel@economatica.com.br

From bouncefilter Thu Dec 9 22:41:55 1999
Received: from mail.pbpower.co.nz (mail.designpower.co.nz [203.97.56.178])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA09736
for <pgsql-general@postgreSQL.org>; Thu, 9 Dec 1999 22:41:01 -0500 (EST)
(envelope-from DerricuttM@pbworld.com)
Received: by mail.pbpower.co.nz with Internet Mail Service (5.5.2650.21)
id <XSGG1G5J>; Fri, 10 Dec 1999 16:41:56 +1300
Message-ID: <93314B6256A5D211BE8B006097B9502717914B@NZAM>
From: "Derricutt, Mark" <DerricuttM@pbworld.com>
To: pgsql-general@postgreSQL.org
Subject: Result Sets from INSERT/DELETE queries
Date: Fri, 10 Dec 1999 16:41:49 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
charset="iso-8859-1"

If I issue a DELETE/UPDATE/INSERT query, is there anyway to get a result set
of the records modified/inserted/deleted?

When using Database Desktop (part of Delphi) against Paradox tables, I get
such a result set, and it's very handy to know what's changed, is this
possible under postgres?

Mark

From bouncefilter Fri Dec 10 02:56:58 1999
Received: from mx.yeah.net ([202.106.185.87])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA72572
for <pgsql-general@hub.org>; Fri, 10 Dec 1999 02:56:14 -0500 (EST)
(envelope-from bluexiao@yeah.net)
Received: from xiaoqing (unknown [202.101.54.185])
by mx.yeah.net (Postfix) with SMTP id 0955D3F97CF
for <pgsql-general@hub.org>; Fri, 10 Dec 1999 15:57:55 +0800 (CST)
Message-ID: <000e01bf42e4$002589a0$b93665ca@xiaoqing>
Reply-To: "XiaoQing" <tsingxiao@yeah.net>
From: "XiaoQing" <bluexiao@yeah.net>
To: <pgsql-general@hub.org>
Subject: ANY small and smart DBMS running on Win32 platform?
Date: Fri, 10 Dec 1999 15:55:59 +0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

except MySQL, that's something commerical.
I need your help!

From bouncefilter Fri Dec 10 04:07:58 1999
Received: from fep132.fep.ru (mail@fep132.fep.ru [195.230.89.88])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA93010
for <pgsql-general@hub.org>; Fri, 10 Dec 1999 04:07:15 -0500 (EST)
(envelope-from phd@phd.russ.ru)
Received: from localhost [127.0.0.1] (phd)
by fep132.fep.ru with esmtp (Exim 2.05 #1 (Debian))
id 11wM0m-0001M2-00; Fri, 10 Dec 1999 12:06:48 +0300
Date: Fri, 10 Dec 1999 09:06:48 +0000 (GMT)
From: Oleg Broytmann <phd@phd.russ.ru>
X-Sender: phd@fep132.fep.ru
Reply-To: phd2@earthling.net
To: XiaoQing <tsingxiao@yeah.net>
cc: pgsql-general@hub.org
Subject: Re: [GENERAL] ANY small and smart DBMS running on Win32 platform?
In-Reply-To: <000e01bf42e4$002589a0$b93665ca@xiaoqing>
Message-ID: <Pine.LNX.4.21.9912100857290.5149-100000@fep132.fep.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 10 Dec 1999, XiaoQing wrote:

except MySQL, that's something commerical.
I need your help!

If you need realy small database and not client-server, you may consider
bsddb. AFAIK perl for windows comes with prebuilt bsddb.

Python-based solutions can be found here:
http://www.vex.net/parnassus/apyllo.py/973100124.

There are Flat ASCII Database (all platforms), gdbmmodule-win32, MkWrap
(python wrapper for MetaKit), mxODBC (so you can connect to ANY
ODBC-compliant db), and finally, the GadFly. GadFly is an SQL engine,
written entirely in Python, and thus portable to any platform. URL -
http://www.chordate.com/gadfly.html

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net
Programmers don't die, they just GOSUB without RETURN.

From bouncefilter Fri Dec 10 04:50:59 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA02195
for <pgsql-general@postgresql.org>;
Fri, 10 Dec 1999 04:50:43 -0500 (EST)
(envelope-from eloehr@austin.rr.com)
Received: from austin.rr.com ([24.93.43.19]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Fri, 10 Dec 1999 03:42:34 -0600
Sender: root
Message-ID: <3850CD25.477C87@austin.rr.com>
Date: Fri, 10 Dec 1999 03:51:33 -0600
From: Ed Loehr <eloehr@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: "ExecInitIndexScan: both left and right op's are rel-vars"
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Anyone know what this error is or how to prevent it? Seems to usually
show up on large queries...

"ExecInitIndexScan: both left and right op's are rel-vars"

I've seen it before, but can't recall a solution and couldn't find one
in archives/deja...

Thanks in advance...

pgsql 6.5.2, redhat 6.0 (2.2.5-15smp).

From bouncefilter Fri Dec 10 10:17:03 1999
Received: from mailhub2-dmz1.bloomberg.com (mailhub2-dmz1.bloomberg.com
[199.172.169.81]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA69284
for <pgsql-general@postgresql.org>;
Fri, 10 Dec 1999 10:16:44 -0500 (EST)
(envelope-from kagel@bloomberg.net)
Received: from ns2.bloomberg.com by mailhub2-dmz1.bloomberg.com;
Fri, 10 Dec 1999 10:11:28 -0500
Received: from bloomberg.net by ns2.bloomberg.com (8.6.13/200.20.1.1)
id KAA27064; Fri, 10 Dec 1999 10:16:43 -0500
Message-ID: <3851192D.E56FD243@bloomberg.net>
Date: Fri, 10 Dec 1999 10:15:57 -0500
From: "Art S. Kagel" <kagel@bloomberg.net>
Reply-To: kagel@bloomberg.net
Organization: Bloomberg LP
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: RE: a comparison of 4 databases
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

As an, admittedly avid, and long time user of Informix database products I
felt I could not leave this shoddy comparison stand without comment. There
are many errors concerning the features and capabilities of Informix database
servers and Mr. Kirkwood conducted several of his tests poorly which did not
fairly represent this fine set of database server products, nor, likely, the
other fine databases included in the comparison either. Anyone interested in
his results should read on. Since I have moused the original post I will
preceed my own comments with 'ASK - ' and indent to make them clear.

A Comparison Of 4 Databases
---------------------------

Intro
-----

This paper shows the results of an evaluation of 4 databases. I am posting it
to this mail group as I think Postgresql emerged quite favourably.

The evaluated databases were Oracle, Informix, Mysql and Postgresql.

Features and performance were examined.

Hardware And Operating System
-----------------------------

2 x HP Vertra VE 7 each with 160M RAM + 1x3.2G + 1x13G Quantum IDE Drives were
used.
Redhat 6.0 was used as the operating system. No kernel changes were made.

Initial Experiences
-------------------

Mysql was obtained in rpm format and was amazingly easy to install. The
installation process created and started a database. The version was 3.22.27

Documentation was supplied and was good.

Postgresql was similarly elementary to install, and again a database was
created and started. The product comes with the flavour of Linux used and
was in rpm format. The version was 6.5.2

Documentation was supplied and was very good.

ASK - Indeed the install can be cryptic but there are detailed installation
instructions that can be downloaded from the Informix site as well
as an available How-To that explains how to make an initial
configuration and bring up the engine for the first time. All of
which are also explained in detail in the Informix Administrators
Guide.

Using some of the (not supplied) documentation it was discovered how to create
and configure a database. The version was 7.30 ( This is old, but all they
are supplying on this platform - 9.x is current)

ASK - I assume Mr. Kirkwood downloaded the Informix Dynamic Server v7.30
which is NOT old. The Informix server product line includes 4
different servers and Informix is in the process of merging the code
lines of some of these. The Informix enterprise level engine for
transaction processing IS the IDS7.3x product the latest release of
which is 7.31 which IS available for Linux but the link that Mr.
Kirkwood followed took him to the older (by 3 months) 7.30 version.
The IDS/UDO v9.1x product is known as the Universal Data Option and
is Informix's Object Relational product descended ultimately, like
PostgreSQL, from the Postgres project. UDO was based on the older
IDS 7.1x code base and some features needed for transaction oriented
applications were missing. In the last 3 weeks, indeed on the same
day Mr. Kirkwood posted his report, Informix released IDS.2000 which
is IDS v9.20 and is a merger of the 7.31 and 9.1x code bases in a new
product promising Object Relational features, full transaction server
features, and enterprise quality performance. But, this is a brand
new code base - and so - many users are waiting for IDS.2000 v9.21
or at least the first few maintenance releases of v9.20. It is
important to note that Informix considers Linux a Tier I port and
released the IDS.2000 product on Linux on the same day as it did its
other Tier I ports like Sun/Solaris and HP/HP-UX.

Documentation was not supplied, it was available on the Informix web site. It is
ok.

ASK - The documentation is available for perusal online at the Informix
website from whence it can also be downloaded for local access or
you can purchase the docs on CD-ROM for $45US or in hard copy (I
think they are about $750US) from Informix. Note that Informix's
documentation has won numerous awards for quality and clarity and
compared to Oracle's completely opaque docs I have always found it
a pleasure to use.

Documentation is not supplied, it is available from the Oracle web site. It is
ok.

Tests And results
-----------------

Database Feature
Comparison

Database Cost Trans Row Const Program Sec Fail Hot
actions Lock raints mable ure Safe back

Mysql 0 /3000 No No No Partial Yes No No
Postgresql 0 Yes Yes Partial Yes Yes Yes No
Oracle 3200 Yes Yes Yes Yes Yes Yes Yes
Informix 2000 Yes No Yes Yes Yes No No

ASK - See below. ALL OF THE 'No's above should be 'Yes'es. I address
each point below.

Cost

NZ$ for 10 user license. Two prices mean that the product is charged
for if resold as part of an application ( Mysql )
Support is not included

Transactions

Commit, rollback, isolation levels of at least read commited

ASK - Informix permits the user to create a database in one of four modes.
Three of these: Mode ANSI, Buffered Logged, and Unbuffered Logged
support multiple statement transactions with BEGIN WORK (ANSI mode
databases infer a BEGIN WORK with the first statement not in a
transaction, ie following a COMMIT or ROLLBACK). The fourth, which
for historical reasons is the default mode, is non-logged which does
NOT support multiple statement transactions, though individual SQL
statements are treated as singleton transactions. Based on the
results for Fail Safe I'd say that the database was created in
default mode without logging or perhaps in BUFFERED LOG mode and
the COMMIT record was still in the log buffer and had not flushed
to disk in which case Informix rightly rolled back the transaction
(this would be noted in the engine's message log at the time the
engine was restarted). For this type of secure testing Mr. Kirkwood
should have beenusing an UNBUFFERED LOG mode database which
automatically flushes the log buffer when a commit record is written
to it. There is an extensive discussion of these issues and their
ramifications for performance and safety in the Administrators
Guide. Note that most Informix DBAs run their databases in
UNBUFFERED LOG mode.

Row Locking

select for update that locks only the rows selected and does not
block reads

ASK - Informix DOES indeed support row level locking though the default
for tables is page level locking. One need only include the LOCK
MODE ROW clause in the CREATE TABLE statement or ALTER the table
afterward to have row level locks.

Constraints

primary and foreign key, with ability to enable/ disable or drop / add
existence will give ""Partial"" and enable etc will give "Yes"

Programmable

create trigger, procedural language extensions to SQL
A "Partial" means that external functions only are supported

Secure

Requires username and password validation

Fail Safe

delete of 100 out of 100000 rows, commit ( if have it ) then power
off and on, check after power on - 999900 rows gets a "Yes"

ASK - If Mr. Kirkwood had created his database with one of the logged
transaction modes he would have had complete 'fail safe' behavior
from the Informix server. Informix cannot recover transactions
that have not been checkpointed out to disk in a database without
logging (the default) but it can for a logged database.

Hot Backup

Can a consistent backup of the database be run backup while it is up
with transactions performed against it.

ASK - Informix was the first relational database to support online live
consistent backup of its database servers. Indeed Informix provides
three archive products all of which can backup the server while being
actively updated. Only one of these, ontape, is available on Linux
so far (due to some third party software the others, onarchive and
onbar, depend on which was not available for Linux at release time)
but that may soon change.

Database Performance Comparison - Data
Warehouse

Database Bulk Load Summarize 3% Summarize 0.3% Summarize 0.3%
1M of 3M of 3M of 3M
1 dim 1 fact 2 dim 1 fact 3 dim 1 fact

Mysql 20 14 90 57
Postgresql 420 16 4 7
Oracle 65 5 3 3
Informix 170 8 5 6

Notes

Bulk Load

elapsed seconds to load 1000000 rows via whatever bulk load tool is
supplied.

ASK - Informix has several bulk load utilities. It would appear that Mr.
Kirkwood either did not use the ipoader or did not run it in either
of the higher speed modes which includes a mode which bypasses all
logging and is several times faster than logged modes.

ASK - On the performance tests, Informix performance is very dependent on
the tuning of the engine and the presence of proper database
statistics. I cannot know how well or poorly Mr. Kirkwood tuned the
engine or whether he ran the recommended suite of UPDATE STATISTICS
commands after loading the database. Without details of how well
he prepared the various servers and databases so the optimizers
could do their jobs properly one cannot evaluate the quality of
his results. Note that I state all of this even though Informix
performed reasonably anyway. I just wonder how much better ANY of
the tested server could have performed.

Summarize 3%
1 dim + 1 fact

Measure elapsed seconds to display summarized count and one timelike
dimension attribute for basic star query
Access path can be via an index scan

Summarize 0.3%
2 dim + 1 fact

Measure elapsed seconds to display summarized count and one non timelike
dimesion attribute for less basic star query
Access path can be via index scans

Summarize 0.3%
3 dim + 1 fact

Measure elapsed seconds to display a summarized count and 1 non timelike
dimension attribute for more complex star query
Access path can be via index scans

Database Performance Comparison -
Online

Database Create Create Query 1 Query 4 Query Summary
10K 1M of 10K of 1M 10% of 1M

Mysql 7 891 0 0 1
Postgresql 21 4430 0 0 2
Oracle 31 3694 0 0 2
Informix 0 0 10

Database Tpm Tpm Tpm Tpm
1 sess. 2 sess. 4 sess. 8 sess.

Mysql 59/58 59/115 59/229 58/425
Postgresql 48 90 169 233
Oracle 55 108 180 291
Informix

Notes

Unfortunately no Informix SDK was available, so there is no result for
the first two or last tests.

ASK - Informix's SDK is not included in the basic engine download but IS
available for free download for Linux. The SDK includes ESQL/C,
CLI/ODBC, JDBC, a C++ interface, and more. Also available in
separate packages are I4GL (compiled version of Informix's award
winning 4th Generation Language), R4GL (pcode version of I4GL which
includes a source level pcode debugger), ISQL (Informix's forms,
menus, and report writer package), and D4GL (a GUI aware version of
I4GL). All of these are available for download including free
evaluation licenses and most are available with a free single user
development license. The SDK is free for all developers and the
runtime package, iConnect, is free for all users. With VERY little
effort Mr. Kirkwood could have compiled and run his tests with
Informix.

Create 10K

elapsed seconds for Php app to insert 10000 rows one by
one

Create 1M

elapsed seconds for Php app to insert 1000000 rows one by one

Query 1

0 seconds means that no delay was measurable
Measure elapsed seconds to show master record 1 row located 70% though
the table. Access path can be via an index scan

Query 4

Measure elapsed seconds to display 4 detail rows for one of the master
records in previous test. Access path can be via index scans

Query Summary

Measure elapsed seconds to display a summarized sum and count
for 5% of 1000000 rows. This is a 2 table join . Access path can be via
index scans

Tpm n sessions

Transactions per minute for n sessions, achievable for lightweight Perl
DBI application. Two results for Mysql refer to two possible locking
schemes

Analysis
--------

Features

Oracle clearly has the most features. However it is Postgresql that is next in
line.

The features fail safe, transactions and security are seen as essential,
with row locking as highly desirable.

This means that at face value only Oracle and Postgresql satisfy the criteria.

ASK - As does Informix if one takes the 10 seconds it takes to add the
WITH LOG clause to the CREATE DATABASE and LOCK MODE ROW clause to
the CREATE TABLE statements. In several cases below Mr. Kirkwood
bothered to check the docs and even contact developers to find out
if or how he could get some feature he wanted that Oracle or
PostgreSQL did not seem to have could be made to work. It is
suspect that he did not do the same for MySQL and Informix. His
Informix download came with a free support contract so if reading
the docs or posting queries to comp.databases.informix did not get
the information he needed (and I assure you either the docs or the
newsgroup would have given him the answers) he could have called
tech support toll free.

It should be noted that Oracle needed a patch to be fail safe, and that this
was not advertised on the web site, thus is possible that Informix and Mysql
can also be similarly patched.

Repeated tests with Informix page level locks showed that readers were blocked
at this point. This was viewed as extremely undesirable.

ASK - In addition to setting row level locking mode for the tables Mr.
Kirkwood should note that Informix implements all of the ANSI
Isolation Modes. The default for a logged database

In conclusion on the features front, Oracle and Postgresql emerge as the
leaders.

Performance

1 Online operations

Initially Postgreql refused to use indexes to help with queries. A mail to one
of the Postgresql Development Team traced this to an unusual pickiness with
respect to the implied datatypes of constants in the where clause.

Informix had problems with the summary query, it would not go faster that 10s,
however it seemed to perform ok for the 10000 and 1000000 query searches.

Mysql demonstrates the overhead associated with multiple versioning and
transactions. It was obviously the fastest raw speed terms. It was in
general 4-5 times faster than anything else.

Postgresql was in general about 20% slower than Oracle.

Thus Mysql is fastest, and most scalable if applications locks can be used.
Oracle and Postgreql are similar in scalability, but Postgresql begins to tail
off a little before Oracle does.

2 Data warehousing operations

Mysql has a very fast bulk load facility.
Oracle also has a very fast bulk load.
Infomix has a reasonably fast one.
Postgresql is noticeably slower than any of the others.

Mysql performed extremely poorly at the star type queries.
Oracle and Informix performed very well.
Postgresql performed very well in all but the first query - the simplest
(ironically), but it scanned the most data. This points to Oracle and Informix
having faster Nested Loop or Sort algorithms.

Both Oracle and Postgresql would experience a period of poor performance on a
table immediately after it was bulk loaded - typically until it was vacuumed or
analyzed.

In conclusion for this section Oracle, Informix are very good.
Postgresql is good but is hampered by slow bulk load and sorting of large
datasets.
Mysql can get the data in fast but is poor at querying it.

Overall
-------

Informix performs mostly ok, but its locking scheme precludes it for serious on
line use (it would have been interesting to test this).

ASK - Does this make sense? There are literally thousands of mission
critical, speed dependent, multi-user applications running against
Informix engines. It makes no sense that Informix's locking
prohibits reasonable performance. Just this reasonablness test
should have clued the author in that he had missed something.

Oracle performs well.
Mysql's lack of transactions would have been ok for data warehousing, but it
could not do star queries. This rules it out.
Postgresql performed about 20% slower than Oracle, except for bulk loads and
large dataset sorts. These things mean that it is suitable for data warehousing
and on line operations, with the proviso that large data loads and some large
summary queries may be unpleasantly slow.

ASK - In brief, these tests need to be performed again, certainly for
Informix but most likely for Oracle and the rest as well, with
an eye to more accurately portraying the performance and features
of each. More care is needed.

[Benchmark code SNIPPED]

Art S. Kagel

From bouncefilter Fri Dec 10 12:04:04 1999
Received: from alert.infoplease.com (range.infoplease.com [208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA01371
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:03:16 -0500 (EST)
(envelope-from kdebisschop@range.infoplease.com)
Received: from skillet.infoplease.com (skillet [10.0.1.212])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id MAA18419
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:02:40 -0500 (EST)
Received: (from kdebisschop@localhost)
by skillet.infoplease.com (8.9.3/8.9.1) id MAA27140;
Fri, 10 Dec 1999 12:02:46 -0500
Date: Fri, 10 Dec 1999 12:02:46 -0500
Message-Id: <199912101702.MAA27140@skillet.infoplease.com>
X-Authentication-Warning: skillet.infoplease.com: kdebisschop set sender to
kdebisschop@spaceheater.infoplease.com using -f
From: Karl DeBisschop <kdebisschop@range.infoplease.com>
To: pgsql-general@postgreSQL.org
Subject: \d shows all my tables twice
Reply-to: kdebisschop@range.infoplease.com

I'm using the postgresql-6.5.3-1 rpm from PostgreSQLs website on
redhat 6.0

Some time between yesterday and today postgres developed the habit of
listing all may table twice when I do \d or \dS from psql. Right now
this is only annoying, but does this mean there is a system corruption
I need to fix?

I've destroyed all my databases other than template1 and vacuumed in
template1. My next thought is to reinstall, but I'd rather not if I
don't have too.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

Netsaint Development
http://netsaintplug.sourceforge.net

From bouncefilter Fri Dec 10 12:11:04 1999
Received: from test133.ee.ic.ac.uk (IDENT:root@test133.ee.ic.ac.uk
[155.198.133.240]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA03313
for <pgsql-general@postgresql.org>;
Fri, 10 Dec 1999 12:10:49 -0500 (EST)
(envelope-from smacedo@ic.ac.uk)
Received: from localhost (smacedo@localhost)
by test133.ee.ic.ac.uk (8.9.3/8.9.3) with ESMTP id RAA30816;
Fri, 10 Dec 1999 17:08:51 GMT
X-Authentication-Warning: test133.ee.ic.ac.uk: smacedo owned process doing -bs
Date: Fri, 10 Dec 1999 17:08:51 +0000 (GMT)
From: Silvio Macedo <smacedo@ic.ac.uk>
X-Sender: smacedo@test133.ee.ic.ac.uk
To: nmmm@nmmm.nu, pgsql general mailing list <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] get the previous assigned sequence value
Message-ID: <Pine.LNX.4.21.9912101658560.30628-100000@test133.ee.ic.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Date: Thu, 9 Dec 1999 16:35:35 +0200
From: "Nikolay Mijaylov" <nmmm@nmmm.nu>
Re: [GENERAL] get the previous assigned sequence value
Why you discuss it????
The problem is quite clean and it was solvev many years ago.....
1. Get the *next* sequence value:
select nextval("gogo_seq");
2. Store it into a variable (for example $X)
3. Insert proper data (and and sequence value)
insert into gogo values( $X, 'NMMM', 'mailto:nmmm@nmmm.nu');
4. Use value $X, as u want
insert into gogo_detail values( $X, 'bla bla0');
insert into gogo_detail values( $X, 'bla bla1');
insert into gogo_detail values( $X, 'bla bla2');
Am I clear?
nmmm

No comments...
Just imagine that the transaction aborts after you did select
nexval().

--
``````````````` Silvio Emanuel Nunes Barbosa de Macedo '''''''''''''''''''
smacedo@ic.ac.uk smacedo@inescn.pt
Imperial College, University of London INESC Porto
Intelligent and Interactive Systems Telecom. and Multimedia
Exhibition Road, Pc da Republica, 93
London SW7 2AZ, England 4050-497 PORTO PORTUGAL
Tel:+44 171 5946323 Tel:+351 22 2094220

From bouncefilter Fri Dec 10 12:16:04 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA04524
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:15:25 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA04476;
Fri, 10 Dec 1999 12:15:13 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912101715.MAA04476@candle.pha.pa.us>
Subject: Re: [GENERAL] \d shows all my tables twice
In-Reply-To: <199912101702.MAA27140@skillet.infoplease.com> from Karl
DeBisschop at "Dec 10, 1999 12:02:46 pm"
To: kdebisschop@range.infoplease.com
Date: Fri, 10 Dec 1999 12:15:13 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

You have duplicate entries in pg_shadow/pg_user table.

I'm using the postgresql-6.5.3-1 rpm from PostgreSQLs website on
redhat 6.0

Some time between yesterday and today postgres developed the habit of
listing all may table twice when I do \d or \dS from psql. Right now
this is only annoying, but does this mean there is a system corruption
I need to fix?

I've destroyed all my databases other than template1 and vacuumed in
template1. My next thought is to reinstall, but I'd rather not if I
don't have too.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

Netsaint Development
http://netsaintplug.sourceforge.net

************

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Fri Dec 10 12:26:04 1999
Received: from alert.infoplease.com (range.infoplease.com [208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA06842
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:25:37 -0500 (EST)
(envelope-from kdebisschop@range.infoplease.com)
Received: from skillet.infoplease.com (skillet [10.0.1.212])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id MAA19578
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:25:01 -0500 (EST)
Received: (from kdebisschop@localhost)
by skillet.infoplease.com (8.9.3/8.9.1) id MAA27793;
Fri, 10 Dec 1999 12:25:06 -0500
Date: Fri, 10 Dec 1999 12:25:06 -0500
Message-Id: <199912101725.MAA27793@skillet.infoplease.com>
X-Authentication-Warning: skillet.infoplease.com: kdebisschop set sender to
kdebisschop@spaceheater.infoplease.com using -f
From: Karl DeBisschop <kdebisschop@range.infoplease.com>
To: pgsql-general@postgreSQL.org
In-reply-to: <199912101715.MAA04476@candle.pha.pa.us> (message from Bruce
Momjian on Fri, 10 Dec 1999 12:15:13 -0500 (EST))
Subject: Re: [GENERAL] \d shows all my tables twice
Reply-to: kdebisschop@range.infoplease.com
References: <199912101715.MAA04476@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>

You have duplicate entries in pg_shadow/pg_user table.

I'm using the postgresql-6.5.3-1 rpm from PostgreSQLs website on
redhat 6.0

Some time between yesterday and today postgres developed the habit of
listing all may table twice when I do \d or \dS from psql. Right now
this is only annoying, but does this mean there is a system corruption
I need to fix?

I've destroyed all my databases other than template1 and vacuumed in
template1. My next thought is to reinstall, but I'd rather not if I
don't have too.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>

Dead on right. Duplicates for postgres itself and the two admins.
Thanks.

By the way, you guys are great. I really appreciate the work you do.
And I wanted to say the the RPM packaging was very well done in my
opinion - it installed like a dream, and the init script did a perfect
job of saving me the effort of manually initializing the DBMS. Kudos
to all involved.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

Netsaint Plugins Development
http://netsaintplug.sourceforge.net

From bouncefilter Fri Dec 10 11:39:07 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA93052
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 11:38:26 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id LAA11699;
Fri, 10 Dec 1999 11:32:26 -0600
Date: Fri, 10 Dec 1999 11:32:26 -0600 (CST)
From: <kaiq@realtyideas.com>
To: "Art S. Kagel" <kagel@bloomberg.net>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] RE: a comparison of 4 databases
In-Reply-To: <3851192D.E56FD243@bloomberg.net>
Message-ID: <Pine.LNX.4.10.9912101123300.10905-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

another example that do not trust any "comparison" that is done
by one party. As our beloved pg developer suggested, any real
comparison should by done based on some reasonable-often-used-real-life
cases and by at least more than 2 or 3 proved (certificed -- for
Orakal -- or beloved -- for PG) EXPERTS of each target-dbms
by using all possible approaches available for that database system.

this kind of thing, like religion/culture "comparison", should
be read VERY VERY carefully.

On Fri, 10 Dec 1999, Art S. Kagel wrote:

As an, admittedly avid, and long time user of Informix database products I
felt I could not leave this shoddy comparison stand without comment. There
are many errors concerning the features and capabilities of Informix database
servers and Mr. Kirkwood conducted several of his tests poorly which did not
fairly represent this fine set of database server products, nor, likely, the
other fine databases included in the comparison either. Anyone interested in
his results should read on. Since I have moused the original post I will
preceed my own comments with 'ASK - ' and indent to make them clear.

A Comparison Of 4 Databases
---------------------------

Intro
-----

This paper shows the results of an evaluation of 4 databases. I am posting it
to this mail group as I think Postgresql emerged quite favourably.

The evaluated databases were Oracle, Informix, Mysql and Postgresql.

Features and performance were examined.

Hardware And Operating System
-----------------------------

2 x HP Vertra VE 7 each with 160M RAM + 1x3.2G + 1x13G Quantum IDE Drives were
used.
Redhat 6.0 was used as the operating system. No kernel changes were made.

Initial Experiences
-------------------

Mysql was obtained in rpm format and was amazingly easy to install. The
installation process created and started a database. The version was 3.22.27

Documentation was supplied and was good.

Postgresql was similarly elementary to install, and again a database was
created and started. The product comes with the flavour of Linux used and
was in rpm format. The version was 6.5.2

Documentation was supplied and was very good.

Informix was more cryptic to install. It was obtained in rpm format and
installed. However this merely installed an archive and the real installation
process had to be run thereafter. After this it had to be divined as to what
was required next - the install does not create a database.

ASK - Indeed the install can be cryptic but there are detailed installation
instructions that can be downloaded from the Informix site as well
as an available How-To that explains how to make an initial
configuration and bring up the engine for the first time. All of
which are also explained in detail in the Informix Administrators
Guide.

Using some of the (not supplied) documentation it was discovered how to create
and configure a database. The version was 7.30 ( This is old, but all they
are supplying on this platform - 9.x is current)

ASK - I assume Mr. Kirkwood downloaded the Informix Dynamic Server v7.30
which is NOT old. The Informix server product line includes 4
different servers and Informix is in the process of merging the code
lines of some of these. The Informix enterprise level engine for
transaction processing IS the IDS7.3x product the latest release of
which is 7.31 which IS available for Linux but the link that Mr.
Kirkwood followed took him to the older (by 3 months) 7.30 version.
The IDS/UDO v9.1x product is known as the Universal Data Option and
is Informix's Object Relational product descended ultimately, like
PostgreSQL, from the Postgres project. UDO was based on the older
IDS 7.1x code base and some features needed for transaction oriented
applications were missing. In the last 3 weeks, indeed on the same
day Mr. Kirkwood posted his report, Informix released IDS.2000 which
is IDS v9.20 and is a merger of the 7.31 and 9.1x code bases in a new
product promising Object Relational features, full transaction server
features, and enterprise quality performance. But, this is a brand
new code base - and so - many users are waiting for IDS.2000 v9.21
or at least the first few maintenance releases of v9.20. It is
important to note that Informix considers Linux a Tier I port and
released the IDS.2000 product on Linux on the same day as it did its
other Tier I ports like Sun/Solaris and HP/HP-UX.

Documentation was not supplied, it was available on the Informix web site. It is
ok.

ASK - The documentation is available for perusal online at the Informix
website from whence it can also be downloaded for local access or
you can purchase the docs on CD-ROM for $45US or in hard copy (I
think they are about $750US) from Informix. Note that Informix's
documentation has won numerous awards for quality and clarity and
compared to Oracle's completely opaque docs I have always found it
a pleasure to use.

Oracle was difficult to judge as the author frequently installs it. However
pretending to be coming to it new, it would be very difficult to install.
It does not come in rpm format. It is downloadable from the Oracle web site.
The small amount of included documentation is sufficient to enable someone
to work out how to start the installer program. This program is a rudimentary
wizard that asks questions and presents a list of components to choose....
a newcomer would suffer confusion here. The installer can create a database as
part of the install. The version was 8.0.5 (this is slightly old - 8.1.5 is
Current but buggy, 8.0.5 is the latest stable release on this platform).

Documentation is not supplied, it is available from the Oracle web site. It is
ok.

Tests And results
-----------------

Database Feature
Comparison

Database Cost Trans Row Const Program Sec Fail Hot
actions Lock raints mable ure Safe back

Mysql 0 /3000 No No No Partial Yes No No
Postgresql 0 Yes Yes Partial Yes Yes Yes No
Oracle 3200 Yes Yes Yes Yes Yes Yes Yes
Informix 2000 Yes No Yes Yes Yes No No

ASK - See below. ALL OF THE 'No's above should be 'Yes'es. I address
each point below.

Cost

NZ$ for 10 user license. Two prices mean that the product is charged
for if resold as part of an application ( Mysql )
Support is not included

Transactions

Commit, rollback, isolation levels of at least read commited

ASK - Informix permits the user to create a database in one of four modes.
Three of these: Mode ANSI, Buffered Logged, and Unbuffered Logged
support multiple statement transactions with BEGIN WORK (ANSI mode
databases infer a BEGIN WORK with the first statement not in a
transaction, ie following a COMMIT or ROLLBACK). The fourth, which
for historical reasons is the default mode, is non-logged which does
NOT support multiple statement transactions, though individual SQL
statements are treated as singleton transactions. Based on the
results for Fail Safe I'd say that the database was created in
default mode without logging or perhaps in BUFFERED LOG mode and
the COMMIT record was still in the log buffer and had not flushed
to disk in which case Informix rightly rolled back the transaction
(this would be noted in the engine's message log at the time the
engine was restarted). For this type of secure testing Mr. Kirkwood
should have beenusing an UNBUFFERED LOG mode database which
automatically flushes the log buffer when a commit record is written
to it. There is an extensive discussion of these issues and their
ramifications for performance and safety in the Administrators
Guide. Note that most Informix DBAs run their databases in
UNBUFFERED LOG mode.

Row Locking

select for update that locks only the rows selected and does not
block reads

ASK - Informix DOES indeed support row level locking though the default
for tables is page level locking. One need only include the LOCK
MODE ROW clause in the CREATE TABLE statement or ALTER the table
afterward to have row level locks.

Constraints

primary and foreign key, with ability to enable/ disable or drop / add
existence will give ""Partial"" and enable etc will give "Yes"

Programmable

create trigger, procedural language extensions to SQL
A "Partial" means that external functions only are supported

Secure

Requires username and password validation

Fail Safe

delete of 100 out of 100000 rows, commit ( if have it ) then power
off and on, check after power on - 999900 rows gets a "Yes"

ASK - If Mr. Kirkwood had created his database with one of the logged
transaction modes he would have had complete 'fail safe' behavior
from the Informix server. Informix cannot recover transactions
that have not been checkpointed out to disk in a database without
logging (the default) but it can for a logged database.

Hot Backup

Can a consistent backup of the database be run backup while it is up
with transactions performed against it.

ASK - Informix was the first relational database to support online live
consistent backup of its database servers. Indeed Informix provides
three archive products all of which can backup the server while being
actively updated. Only one of these, ontape, is available on Linux
so far (due to some third party software the others, onarchive and
onbar, depend on which was not available for Linux at release time)
but that may soon change.

Database Performance Comparison - Data
Warehouse

Database Bulk Load Summarize 3% Summarize 0.3% Summarize 0.3%
1M of 3M of 3M of 3M
1 dim 1 fact 2 dim 1 fact 3 dim 1 fact

Mysql 20 14 90 57
Postgresql 420 16 4 7
Oracle 65 5 3 3
Informix 170 8 5 6

Notes

Bulk Load

elapsed seconds to load 1000000 rows via whatever bulk load tool is
supplied.

ASK - Informix has several bulk load utilities. It would appear that Mr.
Kirkwood either did not use the ipoader or did not run it in either
of the higher speed modes which includes a mode which bypasses all
logging and is several times faster than logged modes.

ASK - On the performance tests, Informix performance is very dependent on
the tuning of the engine and the presence of proper database
statistics. I cannot know how well or poorly Mr. Kirkwood tuned the
engine or whether he ran the recommended suite of UPDATE STATISTICS
commands after loading the database. Without details of how well
he prepared the various servers and databases so the optimizers
could do their jobs properly one cannot evaluate the quality of
his results. Note that I state all of this even though Informix
performed reasonably anyway. I just wonder how much better ANY of
the tested server could have performed.

Summarize 3%
1 dim + 1 fact

Measure elapsed seconds to display summarized count and one timelike
dimension attribute for basic star query
Access path can be via an index scan

Summarize 0.3%
2 dim + 1 fact

Measure elapsed seconds to display summarized count and one non timelike
dimesion attribute for less basic star query
Access path can be via index scans

Summarize 0.3%
3 dim + 1 fact

Measure elapsed seconds to display a summarized count and 1 non timelike
dimension attribute for more complex star query
Access path can be via index scans

Database Performance Comparison -
Online

Database Create Create Query 1 Query 4 Query Summary
10K 1M of 10K of 1M 10% of 1M

Mysql 7 891 0 0 1
Postgresql 21 4430 0 0 2
Oracle 31 3694 0 0 2
Informix 0 0 10

Database Tpm Tpm Tpm Tpm
1 sess. 2 sess. 4 sess. 8 sess.

Mysql 59/58 59/115 59/229 58/425
Postgresql 48 90 169 233
Oracle 55 108 180 291
Informix

Notes

Unfortunately no Informix SDK was available, so there is no result for
the first two or last tests.

ASK - Informix's SDK is not included in the basic engine download but IS
available for free download for Linux. The SDK includes ESQL/C,
CLI/ODBC, JDBC, a C++ interface, and more. Also available in
separate packages are I4GL (compiled version of Informix's award
winning 4th Generation Language), R4GL (pcode version of I4GL which
includes a source level pcode debugger), ISQL (Informix's forms,
menus, and report writer package), and D4GL (a GUI aware version of
I4GL). All of these are available for download including free
evaluation licenses and most are available with a free single user
development license. The SDK is free for all developers and the
runtime package, iConnect, is free for all users. With VERY little
effort Mr. Kirkwood could have compiled and run his tests with
Informix.

Create 10K

elapsed seconds for Php app to insert 10000 rows one by
one

Create 1M

elapsed seconds for Php app to insert 1000000 rows one by one

Query 1

0 seconds means that no delay was measurable
Measure elapsed seconds to show master record 1 row located 70% though
the table. Access path can be via an index scan

Query 4

Measure elapsed seconds to display 4 detail rows for one of the master
records in previous test. Access path can be via index scans

Query Summary

Measure elapsed seconds to display a summarized sum and count
for 5% of 1000000 rows. This is a 2 table join . Access path can be via
index scans

Tpm n sessions

Transactions per minute for n sessions, achievable for lightweight Perl
DBI application. Two results for Mysql refer to two possible locking
schemes

Analysis
--------

Features

Oracle clearly has the most features. However it is Postgresql that is next in
line.

The features fail safe, transactions and security are seen as essential,
with row locking as highly desirable.

This means that at face value only Oracle and Postgresql satisfy the criteria.

ASK - As does Informix if one takes the 10 seconds it takes to add the
WITH LOG clause to the CREATE DATABASE and LOCK MODE ROW clause to
the CREATE TABLE statements. In several cases below Mr. Kirkwood
bothered to check the docs and even contact developers to find out
if or how he could get some feature he wanted that Oracle or
PostgreSQL did not seem to have could be made to work. It is
suspect that he did not do the same for MySQL and Informix. His
Informix download came with a free support contract so if reading
the docs or posting queries to comp.databases.informix did not get
the information he needed (and I assure you either the docs or the
newsgroup would have given him the answers) he could have called
tech support toll free.

Initially Postgresql did not force password entry and thus was not secure,
however it was discovered that access to the database is configured at install
time as trusted and has to be changed to require passwords.

It should be noted that Oracle needed a patch to be fail safe, and that this
was not advertised on the web site, thus is possible that Informix and Mysql
can also be similarly patched.

Repeated tests with Informix page level locks showed that readers were blocked
at this point. This was viewed as extremely undesirable.

ASK - In addition to setting row level locking mode for the tables Mr.
Kirkwood should note that Informix implements all of the ANSI
Isolation Modes. The default for a logged database

Mysql's lack of transactions was a killer for it, the complexity of having to
programmatically undo an n-table operation was viewed as prohibitive.
( It was noted that the Mysql to do list had atomic operations - pseudo
transactions, on it .)

In conclusion on the features front, Oracle and Postgresql emerge as the
leaders.

Performance

1 Online operations

Initially Postgreql refused to use indexes to help with queries. A mail to one
of the Postgresql Development Team traced this to an unusual pickiness with
respect to the implied datatypes of constants in the where clause.

Informix had problems with the summary query, it would not go faster that 10s,
however it seemed to perform ok for the 10000 and 1000000 query searches.

Mysql demonstrates the overhead associated with multiple versioning and
transactions. It was obviously the fastest raw speed terms. It was in
general 4-5 times faster than anything else.

Postgresql was in general about 20% slower than Oracle.

The multiple session transaction test is most interesting. The idea was to
mimic a Tpc A style banking application with some user think time during the
transaction (1 second ).
Clearly Mysql with its table level locks could not scale at all. However it has
application locks that are nameable, so can mimic row locks - as long as every
access uses them. If these were turned on then a dramatic turnaround was
observed.

Thus Mysql is fastest, and most scalable if applications locks can be used.
Oracle and Postgreql are similar in scalability, but Postgresql begins to tail
off a little before Oracle does.

2 Data warehousing operations

Mysql has a very fast bulk load facility.
Oracle also has a very fast bulk load.
Infomix has a reasonably fast one.
Postgresql is noticeably slower than any of the others.

Mysql performed extremely poorly at the star type queries.
Oracle and Informix performed very well.
Postgresql performed very well in all but the first query - the simplest
(ironically), but it scanned the most data. This points to Oracle and Informix
having faster Nested Loop or Sort algorithms.

Both Oracle and Postgresql would experience a period of poor performance on a
table immediately after it was bulk loaded - typically until it was vacuumed or
analyzed.

In conclusion for this section Oracle, Informix are very good.
Postgresql is good but is hampered by slow bulk load and sorting of large
datasets.
Mysql can get the data in fast but is poor at querying it.

Overall
-------

Informix performs mostly ok, but its locking scheme precludes it for serious on
line use (it would have been interesting to test this).

ASK - Does this make sense? There are literally thousands of mission
critical, speed dependent, multi-user applications running against
Informix engines. It makes no sense that Informix's locking
prohibits reasonable performance. Just this reasonablness test
should have clued the author in that he had missed something.

Oracle performs well.
Mysql's lack of transactions would have been ok for data warehousing, but it
could not do star queries. This rules it out.
Postgresql performed about 20% slower than Oracle, except for bulk loads and
large dataset sorts. These things mean that it is suitable for data warehousing
and on line operations, with the proviso that large data loads and some large
summary queries may be unpleasantly slow.

ASK - In brief, these tests need to be performed again, certainly for
Informix but most likely for Oracle and the rest as well, with
an eye to more accurately portraying the performance and features
of each. More care is needed.

[Benchmark code SNIPPED]

Art S. Kagel

************

From bouncefilter Fri Dec 10 12:48:04 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA14416
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:47:19 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA20030;
Fri, 10 Dec 1999 12:47:06 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912101747.MAA20030@candle.pha.pa.us>
Subject: Re: [GENERAL] \d shows all my tables twice
In-Reply-To: <199912101725.MAA27793@skillet.infoplease.com> from Karl
DeBisschop at "Dec 10, 1999 12:25:06 pm"
To: kdebisschop@range.infoplease.com
Date: Fri, 10 Dec 1999 12:47:06 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Dead on right. Duplicates for postgres itself and the two admins.
Thanks.

By the way, you guys are great. I really appreciate the work you do.
And I wanted to say the the RPM packaging was very well done in my
opinion - it installed like a dream, and the init script did a perfect
job of saving me the effort of manually initializing the DBMS. Kudos
to all involved.

Next release will not allow this problem to happen.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Fri Dec 10 12:53:05 1999
Received: from galileo.csun.edu (swalton@galileo.csun.edu [130.166.114.38])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA15298
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 12:52:49 -0500 (EST)
(envelope-from swalton@galileo.csun.edu)
Received: from localhost (swalton@localhost)
by galileo.csun.edu (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id JAA08280
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 09:52:47 -0800 (PST)
Date: Fri, 10 Dec 1999 09:52:47 -0800 (PST)
From: Stephen Walton <swalton@galileo.csun.edu>
Reply-To: swalton@galileo.csun.edu
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] \d shows all my tables twice
In-Reply-To: <199912101725.MAA27793@skillet.infoplease.com>
Message-ID: <Pine.HPX.4.03.9912100949340.7460-100000@galileo.csun.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I second Karl DeBisschop's comments below. It took me hours to get
postgresql working on an HP/UX system, compared with minutes on Linux.
I'm using Linux as our main database server now.

By the way, I know about using pg_dump to backup the database and I do
that. Is there a good way to maintain a second identical copy of the
database on another machine? Will simply copying the dump over and
restoring it with psql do the trick? Would I need to delete an old copy
of the same database first? We have a somewhat slow Internet connection
to our Linux system's location and it would be nice to have an alternate
site with the same data.

--
Stephen Walton, Professor of Physics and Astronomy,
California State University, Northridge
stephen.walton@csun.edu

On Fri, 10 Dec 1999, Karl DeBisschop wrote:

By the way, you guys are great. I really appreciate the work you do.
And I wanted to say the the RPM packaging was very well done in my
opinion - it installed like a dream, and the init script did a perfect
job of saving me the effort of manually initializing the DBMS. Kudos
to all involved.

From bouncefilter Fri Dec 10 13:10:05 1999
Received: from alert.infoplease.com (range.infoplease.com [208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA20696
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 13:09:49 -0500 (EST)
(envelope-from kdebisschop@range.infoplease.com)
Received: from skillet.infoplease.com (skillet [10.0.1.212])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id NAA20488;
Fri, 10 Dec 1999 13:09:13 -0500 (EST)
Received: (from kdebisschop@localhost)
by skillet.infoplease.com (8.9.3/8.9.1) id NAA30180;
Fri, 10 Dec 1999 13:09:18 -0500
Date: Fri, 10 Dec 1999 13:09:18 -0500
Message-Id: <199912101809.NAA30180@skillet.infoplease.com>
X-Authentication-Warning: skillet.infoplease.com: kdebisschop set sender to
kdebisschop@spaceheater.infoplease.com using -f
From: Karl DeBisschop <kdebisschop@range.infoplease.com>
To: swalton@galileo.csun.edu
CC: pgsql-general@postgreSQL.org
In-reply-to: <Pine.HPX.4.03.9912100949340.7460-100000@galileo.csun.edu>
(message from Stephen Walton on Fri, 10 Dec 1999 09:52:47 -0800 (PST))
Subject: Mirroring a DB (was Re: [GENERAL] \d shows all my tables twice)
Reply-to: kdebisschop@range.infoplease.com
References: <Pine.HPX.4.03.9912100949340.7460-100000@galileo.csun.edu>

By the way, I know about using pg_dump to backup the database and I do
that. Is there a good way to maintain a second identical copy of the
database on another machine? Will simply copying the dump over and
restoring it with psql do the trick? Would I need to delete an old copy
of the same database first? We have a somewhat slow Internet connection
to our Linux system's location and it would be nice to have an alternate
site with the same data.

We sometimes do:

pg_dump -o -h <live> <table> | psql -h <mirror> <table>

(Note that you will probably want -z as well if pre-6.5)

This generally works, but has a habit recreating the views as actual
tables. Often you can live with this, and there may be a simple way
to prevent it. I just haven't found one yet.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

Netsaint Plugins Development
http://netsaintplug.sourceforge.net

From bouncefilter Fri Dec 10 16:12:09 1999
Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA56314
for <pgsql-general@postgresql.org>;
Fri, 10 Dec 1999 16:11:28 -0500 (EST)
(envelope-from danfitzgerald@home.com)
Received: from renata ([24.112.95.186]) by mail.rdc3.on.home.com
(InterMail v4.01.01.02 201-229-111-106) with SMTP
id <19991210210926.NHIE3896.mail.rdc3.on.home.com@renata>
for <pgsql-general@postgresql.org>; Fri, 10 Dec 1999 13:09:26 -0800
Message-ID: <000901bf4352$a9b76150$ba5f7018@renata.24.112.92.1>
From: "Dan Fitzgerald" <danfitzgerald@home.com>
To: <pgsql-general@postgresql.org>
Subject: JDBC Question
Date: Fri, 10 Dec 1999 16:08:10 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0006_01BF4328.C0BB33B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01BF4328.C0BB33B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is there a JDBC Driver Available for PostGre ?

Dan Fitzgerald

danfitzgerald@home.com

------=_NextPart_000_0006_01BF4328.C0BB33B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

------=_NextPart_000_0006_01BF4328.C0BB33B0--

From bouncefilter Fri Dec 10 16:31:07 1999
Received: from dec.contad.unam.mx (dec.contad.unam.mx [132.248.158.18])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA59857
for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 16:30:43 -0500 (EST)
(envelope-from sony@dec.contad.unam.mx)
Received: from localhost (sony@localhost) by dec.contad.unam.mx with ESMTP
(8.7.1/8.7.1) id PAA11963 for <pgsql-general@postgreSQL.org>;
Fri, 10 Dec 1999 15:18:00 -0600 (CST)
Date: Fri, 10 Dec 1999 15:18:00 -0600 (CST)
From: Sanchez Diaz Sonia <sony@dec.contad.unam.mx>
X-Sender: sony@dec.contad.unam.mx
To: pgsql-general@postgreSQL.org
Subject: doubt about UNIX!!!
Message-ID: <Pine.HPX.4.10.9912101510340.11881-100000@dec.contad.unam.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hy!!

I know the next question it is not about the list, but I need
someone help me PLEASE!!!!

I have a server HP-UX 900 with OS 90.05 but I can not configure
the Window System, when I log in from the console I need to choose the
Faile-safe section because I don not the system does not let me to log
in!!!

Somebody Can help me or know about a mailing list where I can ask
about my question (and resolve my problem?)

Thanks!

Facultad de Contaduria y Administracion

\|/ ____ \|/
@~/ ,. \~@
/_( __/ )_\
__U_/ Sanchez Diaz Sonia

e-mail: sony@dec.contad.unam.mx
ssanchezd@correoweb.com
sadsli@latinmail.com

From bouncefilter Fri Dec 10 13:12:05 1999
Received: from the_tower.pictorius.com (cpx.pictorius.com [192.219.29.90] (may
be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id NAA20901
for <pgsql-general@hub.org>; Fri, 10 Dec 1999 13:11:36 -0500 (EST)
(envelope-from pbojanic@pictorius.com)
Received: from bojanic [192.219.29.11] by the_tower.pictorius.com
(SMTPD32-5.04) id A29910E01E6; Fri, 10 Dec 1999 14:12:41 -0300
Message-ID: <014e01bf435b$ae2cf4d0$0b1ddbc0@pictorius.com>
From: "Peter Bojanic" <pbojanic@pictorius.com>
To: <pgsql-general@hub.org>
Subject: Database connections
Date: Fri, 10 Dec 1999 14:12:43 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

My development team is running out of connections on our PostgreSQL database
server. Does anyone know how to increase the number of connections?

Many thanks.

----------
Peter Bojanic, VP Professional Services, Pictorius Incorporated
URL: http://www.pictorius.com; Phone: (902) 492-2880 x223; Fax: (902)
492-3409

From bouncefilter Fri Dec 10 20:56:14 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA11212
for <pgsql-general@postgresql.org>;
Fri, 10 Dec 1999 20:55:27 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:63119 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sIOvy10305>; Sat, 11 Dec 1999 02:55:10 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11wbpU-0001gz-00; Sat, 11 Dec 1999 03:00:13 +0100
Date: Sat, 11 Dec 1999 03:00:12 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Karl DeBisschop <kdebisschop@range.infoplease.com>
cc: swalton@galileo.csun.edu, pgsql-general@postgresql.org
Subject: Re: Mirroring a DB
In-Reply-To: <199912101809.NAA30180@skillet.infoplease.com>
Message-ID: <Pine.LNX.4.20.9912110244240.1875-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-10, Karl DeBisschop mentioned:

pg_dump -o -h <live> <table> | psql -h <mirror> <table>

This generally works, but has a habit recreating the views as actual
tables. Often you can live with this, and there may be a simple way
to prevent it. I just haven't found one yet.

I view *is* a table, with a ON SELECT rule on it. So writing

CREATE TABLE foo ( ... );
CREATE RULE _RETfoo AS ON SELECT DO INSTEAD SELECT your_stuff_here;

is equivalent to

CREATE VIEW foo AS SELECT your_stuff_here;

Perhaps it would be nicer if the dump contained the second version, but
you're not supposed to read these dumps (in case you didn't know :).

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Fri Dec 10 21:56:11 1999
Received: from smtp02.infoave.net (smtp02.infoave.net [165.166.0.27])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA26790;
Fri, 10 Dec 1999 21:55:22 -0500 (EST)
(envelope-from jscottb@infoave.com)
Received: from dial-16.r3.scwlbo.InfoAve.Net ("port 1114"@[206.74.39.146])
by SMTP00.InfoAve.Net (PMDF V5.1-12 #23426)
with ESMTP id <01JJCOAU0QVK8ZEJAK@SMTP00.InfoAve.Net>; Fri,
10 Dec 1999 21:51:49 EST
Date: Fri, 10 Dec 1999 21:46:07 -0500 (EST)
From: Scott Beasley <jscottb@infoave.com>
Subject: First draft of pg_group admin tool.
To: pgsql-admin@postgresql.org, pgsql-announce@postgresql.org,
pgsql-general@postgresql.org
Message-id: <Pine.LNX.4.10.9912102133460.1160-100000@cowbox.infoave.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII

I have a small tool I have written to do admin work on pg_group. With it
I hope we will be able to do most group admin without going into psql.
Like I said, it is a first draft, so it may have a bug or two :-)

It has the following syntax:

usage: pg_group options -- dB group [user ...] || [table ...]
where options is one of:
 -c create group
 -d delete group
 -a add user(s) to group
 -r remove user(s) to group
 +g give group access to tables
 -g revoke group access to tables
 -p privlages to grant/revoke. This is only used with the +g and -g
    options.
 -- end of switches.

examples:
pg_group -c -- guestbook grp_gstbook_usr nobody tux
pg_group -a -- guestbook grp_gstbook_usr webuser
pg_group -d -- guestbook grp_gstbook_usr
pg_group -r -- guestbook grp_gstbook_usr nobody
pg_group +g -p "insert,select" -- guestbook grp_gstbook_usr gstbook
pg_group -g -p "insert" -- guestbook grp_gstbook_usr gstbook

You can get it from: http://www.lowcountry.com/~jscottb/pg_group.tar.gz

If you have any questions, comments, patches or total rewrites email me
at: jscottb@infoave.com

scott

From bouncefilter Sat Dec 11 02:06:13 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA79243;
Sat, 11 Dec 1999 02:06:07 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-190-209.bng.vsnl.net.in [203.197.190.209])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id MAA23270;
Sat, 11 Dec 1999 12:36:53 +0500 (GMT+0500)
Message-ID: <001901bf43a6$16f12dc0$dcbec5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <pgsql-general@postgresql.org>, <vadim@krs.ru>,
<pgsql-interfaces@postgresql.org>
Cc: "Kimi" <kimi@intercept.co.in>
Subject: Spin lock error
Date: Sat, 11 Dec 1999 12:33:31 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0016_01BF43D3.EF61FCC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01BF43D3.EF61FCC0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit

Hi,

We are getting spinlock errors under the following conditions

Background :
We have developed a high performance application using postgres database ( a
3rd party application server).
This application should be scalanble to server 50 requests a second.
Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92 and Redhat
linux 6.0
A request consists of one singleton select on a table of 200,000 rows on
it's primary key, a heavy duty cursor which is a 4 table join but which
returns 100 rows from tables containing maximum of 250 rows, a light sql
opening a cursor on a table containing 500 rows, 2 inserts into tables which
don't have primary key.

We are connecting to the database with autoconnect off.

Problem description :
On a light load there are no problems. As we have increased the load on the
application, the requests get piled up. We keep monitoring the requests
getting piled up using ps ax +AHw- grep post.
Somewhere when the requests crosses 20(ps returns more than 20 rows)....
suddenly postmaster comes down +ACEAIQ- In the server log the following message is
written out.
FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.

FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.

FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock. Aborting.
After this postmaster shutdown.

One observation If we try to recreate this in another linux machine...
multiple postmasters run in the linux machine when the number of requests
become more.
I'm also attaching a file containing 'ps' at the instance postmaster
crashed.

Can anybody please help

Thanks and regards,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

------=_NextPart_000_0016_01BF43D3.EF61FCC0
Content-Type: text/plain;
name="ps.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="ps.txt"

6155 p0 S 0:00 grep post
4957 p2 S 0:00 /usr/local/bin/postmaster -i -p 5433
5992 p2 R 0:01 /usr/local/bin/postgres localhost postgres websight =
COPY
6009 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
commit
6020 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6024 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6038 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6051 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
commit
6062 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6072 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6076 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6077 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
6078 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6110 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6112 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6122 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6137 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6141 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6147 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6149 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
6151 p2 R 0:00 /usr/local/bin/postmaster -i
6165 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6172 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
6184 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
20964 p6 S 0:00 su - postgres
23112 p4 S 0:00 su - postgres
27664 p2 R 0:03 /usr/local/bin/postmaster -i

bash: /bin/ps: Too many open files in system=20

4957 p2 S 0:00 /usr/local/bin/postmaster -i -p 5433
8952 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
idle
8958 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
idle
8981 p2 S 0:00 /usr/local/bin/postgres localhost postgres websight =
idle
8984 p2 S 0:01 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9012 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9013 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
9052 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9054 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9066 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9071 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
9077 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9082 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9083 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9097 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9119 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9127 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9128 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9149 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
SELECT
9155 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
9156 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
9158 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
9159 p2 S 0:00 /usr/local/bin/postgres localhost postgres adcept =
idle
20964 p6 S 0:00 su - postgres
23112 p4 S 0:00 su - postgres

------=_NextPart_000_0016_01BF43D3.EF61FCC0--

From bouncefilter Sat Dec 11 06:39:17 1999
Received: from test133.ee.ic.ac.uk (IDENT:root@test133.ee.ic.ac.uk
[155.198.133.240]) by hub.org (8.9.3/8.9.3) with ESMTP id GAA33226
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 06:38:53 -0500 (EST)
(envelope-from smacedo@ic.ac.uk)
Received: from localhost (smacedo@localhost)
by test133.ee.ic.ac.uk (8.9.3/8.9.3) with ESMTP id LAA00495;
Sat, 11 Dec 1999 11:37:28 GMT
X-Authentication-Warning: test133.ee.ic.ac.uk: smacedo owned process doing -bs
Date: Sat, 11 Dec 1999 11:37:28 +0000 (GMT)
From: Silvio Macedo <smacedo@ic.ac.uk>
X-Sender: smacedo@test133.ee.ic.ac.uk
To: danfitzgerald@home.com
cc: pgsql general mailing list <pgsql-general@postgresql.org>
Subject: Re: JDBC Question
Message-ID: <Pine.LNX.4.21.9912111129200.31408-100000@test133.ee.ic.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there a JDBC Driver Available for PostGre ?

Dan Fitzgerald

danfitzgerald@home.com

Sure. Check <postgres_source_dir>/src/interfaces/jdbc .

To make the driver do a :
make all
The makefile will create a "postgresql.jar" that you should add to your
CLASSPATH, (or add to the java commmand line everytime).

To see examples, check <postgres_source_dir>/src/interfaces/jdbc/example

If you used RedHat RPM, I'm not sure, but you may need to download the
pg source tar.gz in order to have this stuff.

Good Luck!

From bouncefilter Sat Dec 11 06:57:17 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id GAA34885
for <pgsql-general@postgreSQL.org>;
Sat, 11 Dec 1999 06:56:31 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.3/8.9.2) with SMTP id MAA14477
for <pgsql-general@postgreSQL.org>;
Sat, 11 Dec 1999 12:56:26 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Sat, 11 Dec 1999 12:56:26 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
cc: pgsql general mailing list <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: JDBC Question
In-Reply-To: <Pine.LNX.4.21.9912111129200.31408-100000@test133.ee.ic.ac.uk>
Message-ID: <Pine.BSF.3.96.991211125432.12803A-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 11 Dec 1999, Silvio Macedo wrote:

Is there a JDBC Driver Available for PostGre ?

You can find in redhat-contrib, there is a .rpm with it.
mazek

From bouncefilter Sat Dec 11 07:51:17 1999
Received: from chekov.Belgium.EU.net (chekov.belgium.eu.net [193.74.208.161])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA44135
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 07:50:51 -0500 (EST)
(envelope-from wim.ceulemans@nice.be)
Received: from (IDENT:0@idialup405.brussels2.eunet.be [193.75.159.150])
by chekov.Belgium.EU.net with ESMTP id NAA14216
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 13:50:40 +0100 (MET)
Received: from nice.be (aladdin.nice.be [192.168.250.110])
by uni-box.nice.be (8.9.1/8.9.1) with ESMTP id NAA28111
for <pgsql-general@postgresql.org>; Sat, 11 Dec 1999 13:46:42 +0100
Message-ID: <3852493A.5484BB07@nice.be>
Date: Sat, 11 Dec 1999 13:53:14 +0100
From: Wim Ceulemans <wim.ceulemans@nice.be>
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Installation problem on Suse linux 6.3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I can't seem to install the latest postgresql opn Suse linux 6.3 (kernel
2.2.13, glibc 2.1.2). I always get the following message when I run
./configure :

checking for c++... c++
checking wheather the C++ compiler (C++ ) works... no
configure: error: installation or configuration problem': C++ compiler
cannot create executables.

I checked if I did install all C/C++ related packages and that seems to
be ok.
Does anybody have any idea?

P.S.
Searching the mailing list archives on postgresql.org does not seem to
work anymore (the result is always nothing found)?

Regards

Wim Ceulemans
wim.ceulemans@nice.be

From bouncefilter Sat Dec 11 08:17:18 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA49696
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 08:17:04 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-190-217.bng.vsnl.net.in [203.197.190.217])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id SAA20268
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 18:48:00 +0500 (GMT+0500)
Message-ID: <000d01bf43d9$ee0914c0$d9bec5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <pgsql-general@postgresql.org>
Subject: Only single postmaster running
Date: Sat, 11 Dec 1999 18:46:14 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

We have 2 linux machine (Rehat linux 5.2 and 6.0) running postgresql 6.5.1.
On one machine (Linux 6.0), for multiple postgres requests, postmaster forks
into multiple processes).
In another (Linux 5.2), there's only one postmaster all the time.
Questions are
a) Why ??
b) Can this result in locking and other limiting problems.

Thanks and regards,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

From bouncefilter Sat Dec 11 09:13:18 1999
Received: from hermes.iol.cz (hermes.iol.cz [194.228.2.36])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA73217
for <pgsql-general@postgreSQL.org>;
Sat, 11 Dec 1999 09:13:15 -0500 (EST)
(envelope-from robert@robert.cz)
Received: from robert.cz ([194.228.143.121]) by hermes.iol.cz
(Post.Office MTA v3.5.3 release 223
ID# 631-64078U55000L55000S0V35) with ESMTP id cz
for <pgsql-general@postgreSQL.org>; Sat, 11 Dec 1999 15:12:40 +0100
Message-ID: <38525CB7.5A0DE3A@robert.cz>
Date: Sat, 11 Dec 1999 15:16:23 +0100
From: Robert <robert@robert.cz>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Czech Win1250 sorting q
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

Hi,
ISO-8851-2 Czech support (esp. sorting) works fine, but my data use
Win1250. PG 6.5.1+ is supposed to support it, can some kind soul tell me
how can I use it? Thanks.

- Robert

P.S. This is Linux / RH6.1 with Windows clients (browsers).

From bouncefilter Sat Dec 11 09:30:18 1999
Received: from mail.enterprise.net (mail.enterprise.net [194.72.192.18])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA86829
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 09:30:00 -0500 (EST) (envelope-from olly@lfix.co.uk)
Received: from linda.lfix.co.uk (root@max02-027.enterprise.net
[194.72.195.147])
by mail.enterprise.net (8.8.5/8.8.5) with ESMTP id OAA16570;
Sat, 11 Dec 1999 14:29:47 GMT
Received: from lfix.co.uk (olly@localhost [127.0.0.1])
by linda.lfix.co.uk (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id OAA17771;
Sat, 11 Dec 1999 14:29:29 GMT
Message-Id: <199912111429.OAA17771@linda.lfix.co.uk>
X-Authentication-Warning: linda.lfix.co.uk: Host olly@localhost [127.0.0.1]
claimed to be lfix.co.uk
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
X-URL: http://www.lfix.co.uk/oliver
X-face:
"xUFVDj+ZJtL_IbURmI}!~xAyPC"Mrk=MkAm&tPQnNq(FWxv49R}\>0oI8VM?O2VY+N7@F-
KMLl*!h}B)u@TW|B}6<X<J|}QsVlTi:RA:O7Abc(@D2Y/"J\S,
b1!<&<B/J}b.Ii9@B]H6V!+#sE0Q
_+=`K$5TI|4I0-=Cp%pt~L#QYydO'iBXR~\tT?uftep9n9AF`@SzTwsw6uqJ}pL,
h(cZi}T#PB"#!k
p^e=Z.K~fuw$l?]lUV)?R]U}l; f*~Ol)#fpKR)Yt}XOr6BI\_Jjr0!@GMnpCTnTym4f; c{;
Ms=0{`D Lq9MO6{wj%s-*N"G,g
To: "Best21" <best21@best21.com>
cc: pgsql-general@postgresql.org
Subject: Re: I can't drop a table
In-reply-to: Message from "Best21" <best21@best21.com> of Sat,
11 Dec 1999 11:10:45 +0900.
<001b01bf437c$f76106c0$0100a8c0@killer9.e-seoul.thrunet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0
Date: Sat, 11 Dec 1999 14:29:29 +0000
From: "Oliver Elphick" <olly@lfix.co.uk>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id JAA87165

"Best21" wrote:

I wanted drop a table. but error was occured.
Below is error message
�
=====================
guestbook=> drop table guestbook2;
ERROR:� DeletePgTypeTuple: guestbook2 type nonexistent
=====================
�
What's the error message mean?
And how can I drop a table named guestbook?

� >

I am a korean and very few koreans know about PostgreSQL.
So I don't have ask to.
please help me...

I don't know the answer to this; I am forwarding this message to the PostgreSQL
mailing list.

--
Vote against SPAM: http://www.politik-digital.de/spam/
========================================
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"The spirit of the Lord GOD is upon me; because the
LORD hath anointed me to preach good tidings unto the
meek; he hath sent me to bind up the brokenhearted, to
proclaim liberty to the captives, and the opening of
the prison to them that are bound."
Isaiah 61:1

From bouncefilter Sat Dec 11 09:43:19 1999
Received: from alert.infoplease.com (range.infoplease.com [208.222.166.25])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA90622
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 09:42:42 -0500 (EST)
(envelope-from kdebisschop@range.infoplease.com)
Received: from skillet.infoplease.com (skillet [10.0.1.212])
by alert.infoplease.com (8.9.3+Sun/8.9.3) with ESMTP id JAA05594;
Sat, 11 Dec 1999 09:41:40 -0500 (EST)
Received: (from kdebisschop@localhost)
by skillet.infoplease.com (8.9.3/8.9.1) id JAA26603;
Sat, 11 Dec 1999 09:41:41 -0500
Date: Sat, 11 Dec 1999 09:41:41 -0500
Message-Id: <199912111441.JAA26603@skillet.infoplease.com>
X-Authentication-Warning: skillet.infoplease.com: kdebisschop set sender to
kdebisschop@spaceheater.infoplease.com using -f
From: Karl DeBisschop <kdebisschop@range.infoplease.com>
To: peter_e@gmx.net
CC: swalton@galileo.csun.edu, pgsql-general@postgresql.org
In-reply-to: <Pine.LNX.4.20.9912110244240.1875-100000@localhost.localdomain>
(message from Peter Eisentraut on Sat, 11 Dec 1999 03:00:12 +0100
(CET))
Subject: Re: Mirroring a DB
Reply-to: kdebisschop@range.infoplease.com
References: <Pine.LNX.4.20.9912110244240.1875-100000@localhost.localdomain>

From: Peter Eisentraut <peter_e@gmx.net>

On 1999-12-10, Karl DeBisschop mentioned:

pg_dump -o -h <live> <table> | psql -h <mirror> <table>

This generally works, but has a habit recreating the views as actual
tables. Often you can live with this, and there may be a simple way
to prevent it. I just haven't found one yet.

I view *is* a table, with a ON SELECT rule on it. So writing

CREATE TABLE foo ( ... );
CREATE RULE _RETfoo AS ON SELECT DO INSTEAD SELECT your_stuff_here;

is equivalent to

CREATE VIEW foo AS SELECT your_stuff_here;

Perhaps it would be nicer if the dump contained the second version, but
you're not supposed to read these dumps (in case you didn't know :).

I was in fact aware of everything that you mentioned here. The only
point I was trying make, albeit not clearly, is that when executing
the above pipe, the create rule provided by pg_dump is often ambiguous.

to use a real world example, this is the output from pg_dump for a
view that we have:

CREATE RULE "_RETelement_types" AS ON SELECT TO "element_types" DO INSTEAD SELECT "ref", "fcat", "ecat", "oid" AS "ecat_oid", "ord", "emin", "emax", "rows" FROM "fcat", "ecat" WHERE "ref" = "fcat";

In fact, it needs to be modified before it will parse to:

CREATE RULE "_RETelement_types" AS ON SELECT TO "element_types" DO INSTEAD SELECT "ref", fcat.fcat, "ecat", ecat.oid AS "ecat_oid", "ord", "emin", "emax", "rows" FROM "fcat", "ecat" WHERE fcat.ref = ecat.fcat;

Since the rules come at the end of the pg_dump, the transfer mostly
works. But I would not depend on it.

Now I'm not sure if this is a bug, since I think there are choices of
attribute names that will make the rule parse. But it might be a bug, and
certainly the questioner should be aware that there are common
database structures for which the above command can fail to correctly
create the views.

Please forgive the sloppiness of my nomenclature if the this was not
clear before. I had just assumed that this was a known issue, and
that a caution was justified.

--
Karl DeBisschop <kdebisschop@alert.infoplease.com>
617.832.0332 (Fax: 617.956.2696)

Information Please - your source for FREE online reference
http://www.infoplease.com - Your Ultimate Fact Finder
http://kids.infoplease.com - The Great Homework Helper

Netsaint Plugins Development
http://netsaintplug.sourceforge.net

From bouncefilter Sat Dec 11 09:52:20 1999
Received: from Radha.DoCS.UU.SE (root@Radha.DoCS.UU.SE [130.238.9.99])
by hub.org (8.9.3/8.9.3) with SMTP id JAA91478
for <hackers@postgresql.org>; Sat, 11 Dec 1999 09:51:56 -0500 (EST)
(envelope-from e99re41@DoCS.UU.SE)
Received: from Krabba.DoCS.UU.SE (e99re41@Krabba.DoCS.UU.SE [130.238.9.177])
by Radha.DoCS.UU.SE (8.6.12/8.6.12) with ESMTP id PAA28194;
Sat, 11 Dec 1999 15:51:47 +0100
Received: from localhost (e99re41@localhost) by Krabba.DoCS.UU.SE
(8.6.12/8.6.12) with SMTP id PAA05493;
Sat, 11 Dec 1999 15:51:45 +0100
X-Authentication-Warning: Krabba.DoCS.UU.SE: e99re41 owned process doing -bs
Date: Sat, 11 Dec 1999 15:51:44 +0100 (MET)
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
Reply-To: Peter Eisentraut <peter_e@gmx.net>
To: hackers@postgresql.org
cc: swalton@galileo.csun.edu,
Karl DeBisschop <kdebisschop@range.infoplease.com>
Subject: Re: Mirroring a DB
In-Reply-To: <199912111441.JAA26603@skillet.infoplease.com>
Message-ID: <Pine.GSO.4.02A.9912111546350.5375-100000@Krabba.DoCS.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Could the God of Rules please comment on this? It seems to be a deficiency
in the get_rule_def (sp?) backend function. Perhaps to play it safe all
attributes should be fully qualified, but that's probably not as easy as
it sounds.

On Sat, 11 Dec 1999, Karl DeBisschop wrote:

to use a real world example, this is the output from pg_dump for a
view that we have:

CREATE RULE "_RETelement_types" AS ON SELECT TO "element_types" DO
INSTEAD SELECT "ref", "fcat", "ecat", "oid" AS "ecat_oid", "ord",

^^^^^^ ^^^^^

"emin", "emax", "rows" FROM "fcat", "ecat" WHERE "ref" = "fcat";

In fact, it needs to be modified before it will parse to:

CREATE RULE "_RETelement_types" AS ON SELECT TO "element_types" DO
INSTEAD SELECT "ref", fcat.fcat, "ecat", ecat.oid AS "ecat_oid",

^^^^^^^^^ ^^^^^^^^

"ord", "emin", "emax", "rows" FROM "fcat", "ecat" WHERE fcat.ref =
ecat.fcat;

[my highlightings]

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Sat Dec 11 18:21:25 1999
Received: from h00a0cc3b7988.ne.mediaone.net (h00a0cc3b7988.ne.mediaone.net
[24.218.72.149]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA15032
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 18:20:27 -0500 (EST)
(envelope-from kdebisschop@h00a0cc3b7988.ne.mediaone.net)
Received: (from kdebisschop@localhost)
by h00a0cc3b7988.ne.mediaone.net (8.9.3/8.8.7) id SAA12300;
Sat, 11 Dec 1999 18:20:18 -0500
Date: Sat, 11 Dec 1999 18:20:18 -0500
Message-Id: <199912112320.SAA12300@h00a0cc3b7988.ne.mediaone.net>
From: Karl DeBisschop <kdebisschop@h00a0cc3b7988.ne.mediaone.net>
To: pgsql-general@postgresql.org
Subject: Mirroring a DB (was Re: [GENERAL] \d shows all my tables twice)

By the way, I know about using pg_dump to backup the database and I do
that. Is there a good way to maintain a second identical copy of the
database on another machine? Will simply copying the dump over and
restoring it with psql do the trick? Would I need to delete an old copy
of the same database first? We have a somewhat slow Internet connection
to our Linux system's location and it would be nice to have an alternate
site with the same data.

We sometimes do:

pg_dump -o -h <live> <table> | psql -h <mirror> <table>

(Note that you will probably want -z as well if pre-6.5)

This generally works, but has a habit recreating the views as actual
tables. Often you can live with this, and there may be a simple way
to prevent it. I just haven't found one yet.

Based on notes from the PostgreSQL development team and subsequent
testing on our machines, it appears this issue was fixed by either
6.5.2 or 6.5.3 - so the pipe above should work reliably now, assuming
your view was created using a DBMS version 6.5.3 (or maybe 6.5.2 will
do as well). To avoid needing to destory/create the DB, use:

pg_dump -c -o -h <live> <database> | psql -h <mirror> <database>

Note the addition of the -c option and the correction of my typo --
where I meant <database> I said <table> earlier.

Hope this helps.

Karl

From bouncefilter Sat Dec 11 18:51:25 1999
Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net
[194.217.242.38]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA22116
for <pgsql-general@postgresql.org>;
Sat, 11 Dec 1999 18:50:46 -0500 (EST)
(envelope-from rick@ricken.demon.co.uk)
Received: from ricken.demon.co.uk ([194.222.244.59])
by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1)
id 11wwHk-0000i2-0A
for pgsql-general@postgresql.org; Sat, 11 Dec 1999 23:50:45 +0000
Message-ID: <3852E39F.2B9C1E0F@ricken.demon.co.uk>
Date: Sat, 11 Dec 1999 23:51:59 +0000
From: Rick Dearman <rick@ricken.demon.co.uk>
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Getting lists of databases
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

How can I get a listing from the postmaster about what databases exist
on the machine?

so if I had

template1
phone_numbers
friend

as three db on my machine is there a SQL that will tell me what they
are??

From bouncefilter Sat Dec 11 20:31:27 1999
Received: from smtp1.volny.cz (smtp1.volny.cz [212.20.96.10])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA40281
for <pgsql-general@postgreSQL.org>;
Sat, 11 Dec 1999 20:30:43 -0500 (EST)
(envelope-from davids@penguin.cz)
Received: from chameleon.localdomain (kladnoa-76.vol.cz [212.20.117.13])
by smtp1.volny.cz (8.9.3/8.9.3) with ESMTP id CAA12538;
Sun, 12 Dec 1999 02:30:38 +0100 (CET)
X-Envelope-To: pgsql-general@postgreSQL.org
Received: (from david@localhost)
by chameleon.localdomain (8.9.3/8.9.3) id CAA00629;
Sun, 12 Dec 1999 02:30:41 +0100
X-Authentication-Warning: chameleon.localdomain: david set sender to
davids@penguin.cz using -f
Sender: david@chameleon.localdomain
To: pgsql-general@postgreSQL.org
CC: Robert <robert@robert.cz>
Subject: Re: [GENERAL] Czech Win1250 sorting q
References: <38525CB7.5A0DE3A@robert.cz>
From: David Sauer <davids@penguin.cz>
Date: 12 Dec 1999 02:30:31 +0100
In-Reply-To: Robert's message of "Sat, 11 Dec 1999 15:16:23 +0100"
Message-ID: <m2iu25eyiw.fsf@chameleon.localdomain>
User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Arches)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 21

"Robert" == Robert <robert@robert.cz> writes:

Robert> Hi, ISO-8851-2 Czech support (esp. sorting) works fine, but my
Robert> data use Win1250. PG 6.5.1+ is supposed to support it, can some
Robert> kind soul tell me how can I use it? Thanks.

Robert> - Robert

Just do:

set client encoding to 'WIN1250';

Server will store its data in iso-8859-2, but will recode input and
output for windoze clients.

The reason is, that postgres database server uses locales to sort tables
and there is no 'cs_CZ.WIN-1250' locale - and I hope, that never will be.

--
* David Sauer, student of Czech Technical University
* electronic mail: davids@penguin.cz (mime compatible)

From bouncefilter Sun Dec 12 00:20:29 1999
Received: from jason03.u.washington.edu (root@jason03.u.washington.edu
[140.142.77.10]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA78307
for <pgsql-general@postgreSQL.org>;
Sun, 12 Dec 1999 00:19:35 -0500 (EST)
(envelope-from fpm@u.washington.edu)
Received: from saul7.u.washington.edu (fpm@saul7.u.washington.edu
[140.142.82.2])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id
VAA23444
for <pgsql-general@postgreSQL.org>; Sat, 11 Dec 1999 21:19:29 -0800
Received: from localhost (fpm@localhost)
by saul7.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id
VAA02691 for <pgsql-general@postgreSQL.org>;
Sat, 11 Dec 1999 21:19:29 -0800 (PST)
Date: Sat, 11 Dec 1999 21:19:28 -0800 (PST)
From: Frank Miles <fpm@u.washington.edu>
To: pgsql-general@postgreSQL.org
Subject: c function return not recognized?
Message-ID: <Pine.OSF.4.10.9912112108340.20779-100000@saul7.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I've got an external C function that I call from a SELECT, for example:

select * from <table> where <cond1> and CFunction(columnName) > 1.0;

The 'CFunction' has been installed into Postgreql using CREATE FUNCTION,
with a single 'text' argument, and returning a float8 (i.e. double).
I can tell that the 'CFunction' is getting called with the correct
argument, because it can be compiled to echo its activities to a file.
Also, if I rewrite the second condition (for example, leaving out the
'>' sign), psql complains that the function returns a float8, not a
boolean value.

The problem is that Postgresql seems to treat the latter condition
as an "fail always". I can compile the function to return a constant,
say for example, 1.0. Without the second condition, I always get the
expected set of results. With the second condition, no results are
returned regardless of the sense of the comparison: >, <, =, <> all
return nothing.

I would appreciate it if someone could help me be able to use an
externally compiled function that returns a result.

TIA!

-frank

From bouncefilter Sun Dec 12 02:28:30 1999
Received: from hermes.iol.cz (hermes.iol.cz [194.228.2.36])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA04057
for <pgsql-general@postgreSQL.org>;
Sun, 12 Dec 1999 02:27:34 -0500 (EST)
(envelope-from robert@robert.cz)
Received: from robert.cz ([194.228.143.52]) by hermes.iol.cz
(Post.Office MTA v3.5.3 release 223
ID# 631-64078U55000L55000S0V35) with ESMTP id cz;
Sun, 12 Dec 1999 08:26:59 +0100
Message-ID: <38534F22.57EA6E8A@robert.cz>
Date: Sun, 12 Dec 1999 08:30:42 +0100
From: Robert <robert@robert.cz>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: David Sauer <davids@penguin.cz>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Czech Win1250 sorting q
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

netkof=> show client encoding;
ERROR: parser: parse error at or near "encoding"
netkof=> set client encoding to 'WIN1250';
ERROR: parser: parse error at or near "encoding"
netkof=> set client-encoding to 'WIN1250';
ERROR: parser: parse error at or near "-"

Hmm, what did you say I should write? Well, this is PG6.5.2 installed
from RPM, should it be compiled with some special option? Thanks.

- Robert

David Sauer wrote:

"Robert" == Robert <robert@robert.cz> writes:

Robert> Hi, ISO-8851-2 Czech support (esp. sorting) works fine, but my
Robert> data use Win1250. PG 6.5.1+ is supposed to support it, can some
Robert> kind soul tell me how can I use it? Thanks.

Robert> - Robert

Just do:

set client encoding to 'WIN1250';

Server will store its data in iso-8859-2, but will recode input and
output for windoze clients.

The reason is, that postgres database server uses locales to sort tables
and there is no 'cs_CZ.WIN-1250' locale - and I hope, that never will be.

--
* David Sauer, student of Czech Technical University
* electronic mail: davids@penguin.cz (mime compatible)

From bouncefilter Sun Dec 12 01:36:30 1999
Received: from mail.xnet.com (quake.xnet.com [198.147.221.67])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA93583
for <pgsql-general@postgreSQL.org>;
Sun, 12 Dec 1999 01:35:43 -0500 (EST)
(envelope-from selkovjr@selkovjr.xnet.com)
Received: from selkovjr.xnet.com ([204.248.57.203]) by mail.xnet.com
(8.9.3+Sun/XNet-3.0R) with ESMTP id AAA29334;
Sun, 12 Dec 1999 00:35:40 -0600 (CST)
Message-Id: <199912120635.AAA29334@mail.xnet.com>
To: Frank Miles <fpm@u.washington.edu>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] c function return not recognized?
In-Reply-To: Your message of "Sat, 11 Dec 1999 21:19:28 PST."
<Pine.OSF.4.10.9912112108340.20779-100000@saul7.u.washington.edu>
Date: Sun, 12 Dec 1999 01:37:18 -0600
From: "Gene Selkov Jr." <selkovjr@selkovjr.xnet.com>

Frank Miles wrote:

I've got an external C function that I call from a SELECT, for example:

select * from <table> where <cond1> and CFunction(columnName) > 1.0;

The 'CFunction' has been installed into Postgreql using CREATE FUNCTION,
with a single 'text' argument, and returning a float8 (i.e. double).

This is becoming a VFAQ, which is nice because it means that the
extensibility features gain popularity (which IMO make postgres stand
out very impressively), but it is disturbing that the message in the
docs and in examples is not getting through.

One can't get anything back from a C function by other means than
reference. One needs to first palloc() the space for the value and
then return the pointer to it. The reason Frank's function behaved as
he describes is likely because the caller treats the return values as
pointers which indeed points to random locations depending on the
input.

There could be other reasons, too, but then again, it is always helpful
to paste a bit of your code so we don't have to speculate about the
exact nature of your problem.

--Gene

From bouncefilter Sun Dec 12 08:57:35 1999
Received: from clavius.jezuici.krakow.pl (clavius.jezuici.krakow.pl
[195.116.89.78]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA79341
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 08:56:42 -0500 (EST)
(envelope-from rj@jezuici.krakow.pl)
Received: from jezuici.krakow.pl (porta.jezuici.krakow.pl [195.116.89.74])
by clavius.jezuici.krakow.pl (Postfix) with ESMTP id AC2ED13A78
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 14:58:28 +0100 (CET)
Sender: rj@jezuici.krakow.pl
Message-ID: <3853A9CD.29F5685D@jezuici.krakow.pl>
Date: Sun, 12 Dec 1999 14:57:33 +0100
From: "R.J." <rj@jezuici.krakow.pl>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i586)
X-Accept-Language: Polish, pl, en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Index of words form a field.
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

I have a database. In a filed (let's say Title) there are many words.

How to create an index of every word from Title that is related with the
original record and field?
I want also that after correction of the main record this index would
update its content.

Thanks for ideas.

From bouncefilter Sun Dec 12 12:32:37 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA16430
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 12:32:07 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.3/8.9.2) with SMTP id SAA22867
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 18:31:59 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Sun, 12 Dec 1999 18:31:59 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
To: pgsql-general@postgresql.org
Subject: Large objects + JDBC
In-Reply-To: <Pine.OSF.4.10.9912112108340.20779-100000@saul7.u.washington.edu>
Message-ID: <Pine.BSF.3.96.991212182541.20684A-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,
I'm put several gifa into a table. I did as a exercise:) form psql using:
INSERT INTO images (id, data)
VALUES (3, lo_import('/usr/local/apache/servlets/images/a.gif'));

but I have a problem with creating Java stream to read these data. Here
serveral lines of code I was using:
PreparedStatement ps=db.prepareStatement("select oid from imag where id=?");
ps.setInt(1,1);
ResultSet rs = ps.executeQuery();
rs.next();
InputStream is = rs.getBinaryStream(0);
and nothing happens:( Several messages from exceptions:
[13/12/1999 18:11:04:815 CET] ShowImageServlet1: 0
null
Fastpath: ERROR: lo_tell: large object descriptor (-1) out of range

Anybody know how to read LargeObjects with java?
btw I read about postgres JDBC extensions LargeObject and
LargeObjectManager and everthing would be great except nobody mentioned
that they are not completely implemented:)
Anybody can send me a small exapmle how to read these data?
mazek

From bouncefilter Sun Dec 12 22:04:44 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA43920
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 22:04:15 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA55137
for <pgsql-general@postgresql.org>;
Sun, 12 Dec 1999 23:04:13 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Sun, 12 Dec 1999 23:04:12 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
Subject: radius.detaillog -> pgsql parser?
Message-ID: <Pine.BSF.4.21.9912122301360.3883-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

anyone have one of these? I hate "recreating the wheel" if at all
possible.

thanks...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Mon Dec 13 00:24:45 1999
Received: from smtp2.volny.cz (smtp2.volny.cz [212.20.96.11])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA74064
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 00:24:39 -0500 (EST)
(envelope-from davids@penguin.cz)
Received: from chameleon.localdomain (kladnoa-124.vol.cz [212.20.117.59])
by smtp2.volny.cz (8.9.3/8.9.3) with ESMTP id GAA61499;
Mon, 13 Dec 1999 06:24:37 +0100 (CET)
Received: (from david@localhost)
by chameleon.localdomain (8.9.3/8.9.3) id GAA00673;
Mon, 13 Dec 1999 06:24:42 +0100
X-Authentication-Warning: chameleon.localdomain: david set sender to
davids@penguin.cz using -f
Sender: david@chameleon.localdomain
To: Robert <robert@robert.cz>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Czech Win1250 sorting q
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
From: David Sauer <davids@penguin.cz>
Date: 13 Dec 1999 06:24:40 +0100
In-Reply-To: Robert's message of "Sun, 12 Dec 1999 08:30:42 +0100"
Message-ID: <m2wvqjpg4n.fsf@chameleon.localdomain>
Lines: 22
User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Arches)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Robert" == Robert <robert@robert.cz> writes:

Robert> netkof=> show client encoding;
Robert> ERROR: parser: parse error at or

Sorry, my mistake. The right name is 'client_encoding' (with underscore).

Example:

david=> set client_encoding to 'latin2';
SET VARIABLE

Robert> Hmm, what did you say I should write? Well, this is PG6.5.2
Robert> installed from RPM, should it be compiled with some special
Robert> option? Thanks.

Yes, postgres must be compiled with --enable-locale and --with-mb=LATIN2.
And, I'am not sure, but may want upgrade to 6.5.3.

--
* David Sauer, student of Czech Technical University
* electronic mail: davids@penguin.cz (mime compatible)

From bouncefilter Mon Dec 13 04:17:48 1999
Received: from arantxa.ii.uam.es (arantxa.ii.uam.es [150.244.56.15])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA21001
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 04:17:14 -0500 (EST)
(envelope-from Rosa.Carro@ii.uam.es)
From: Rosa.Carro@ii.uam.es
Received: from minerva.ii.uam.es (minerva [150.244.56.39])
by arantxa.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id KAA03721
for <pgsql-general@postgreSQL.org>; Mon, 13 Dec 1999 10:18:00 GMT
Received: from helena (helena [150.244.56.48])
by minerva.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id KAA07426
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 10:10:56 +0100 (MET)
Message-ID: <3854BACA.B3659139@ii.uam.es>
Date: Mon, 13 Dec 1999 10:22:18 +0100
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Embeded SQL
X-Priority: 3 (Normal)
References: <Pine.BSF.4.21.9912122301360.3883-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am writing a C program which includes embeded SQL.
When I compile it with gcc, I am told:

'EXEC' undeclared (first use in this function)

Must I include a special library to use embeded SQL?

Thank you very much,

Rosa M. Carro

--
Rosa Maria Carro Salas
Dpto. Ingenieria Informatica
Universidad Autonoma de Madrid
Cantoblanco 28049, Madrid (Spain)

From bouncefilter Mon Dec 13 05:57:49 1999
Received: from relay4.ftech.net (status.ftech.net [195.200.0.89])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA42154
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 05:56:54 -0500 (EST)
(envelope-from MarkA@idnltd.com)
Received: from ibm9.ftech.net ([212.32.16.79] helo=idnltd.com)
by relay4.ftech.net with smtp (Exim 3.11.ftech-p5 #1)
id 11xT9w-0006a0-00
for pgsql-general@postgresql.org; Mon, 13 Dec 1999 10:56:52 +0000
Message-ID: <008c01bf4555$db0c8230$841720d4@centauri>
From: "Mark Alliban" <MarkA@idnltd.com>
To: <pgsql-general@postgresql.org>
Subject: Problem in pg_hba.conf
Date: Mon, 13 Dec 1999 10:36:02 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0089_01BF4555.DA3FE360"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2110.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

This is a multi-part message in MIME format.

------=_NextPart_000_0089_01BF4555.DA3FE360
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I have just installed PostgreSQL on SCO OpenServer 5.05 but I am having =
problems creating a database. My pg_hba.conf file reads:

local all trust
host all 127.0.0.1 255.255.255.255 trust

When I try to create a database, I get:

Postgres$ createdb test
Connection to database 'template1' failed.
No pg_hba.conf entry for host localhost, user postgres, database =
template1
createdb: database creation failed on test.

Is there a problem with my pg_hba.conf file, or is it another problem?
Thanks,
Mark.

------=_NextPart_000_0089_01BF4555.DA3FE360
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>I have just installed =
PostgreSQL on=20
SCO OpenServer 5.05 but I am having problems creating a database. My =
pg_hba.conf=20
file reads:</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2><FONT=20
face=3D"Courier New">local       =20
all           &nbs=
p;           &nbsp=
;            =
    =20
trust<BR>host        =20
all        =20
127.0.0.1     255.255.255.255  =20
trust</FONT><BR></FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>When I try to create a =
database, I=20
get:</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2><FONT face=3D"Courier =
New">Postgres$=20
createdb test<BR>Connection to database 'template1' failed.<BR>No =
pg_hba.conf=20
entry for host localhost, user postgres, database template1<BR>createdb: =

database creation failed on test.</FONT></FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Is there a problem with my pg_hba.conf =
file, or is=20
it another problem?</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>Mark.</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial =
size=3D2></FONT> </DIV></BODY></HTML>

------=_NextPart_000_0089_01BF4555.DA3FE360--

From bouncefilter Mon Dec 13 06:38:49 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id GAA53358
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 06:38:26 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.3/8.9.2) with SMTP id MAA19815;
Mon, 13 Dec 1999 12:37:45 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Mon, 13 Dec 1999 12:37:45 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
To: Mark Alliban <MarkA@idnltd.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Problem in pg_hba.conf
In-Reply-To: <008c01bf4555$db0c8230$841720d4@centauri>
Message-ID: <Pine.BSF.3.96.991213123641.15200C-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 13 Dec 1999, Mark Alliban wrote:

Postgres$ createdb test
Connection to database 'template1' failed.

do
initdb
You just don't have "default" database.
mazek

From bouncefilter Mon Dec 13 07:27:50 1999
Received: from relay5.ftech.net (littleblue.ftech.net [195.200.12.27])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA61525
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 07:26:54 -0500 (EST)
(envelope-from MarkA@idnltd.com)
Received: from ibm9.ftech.net ([212.32.16.79] helo=idnltd.com)
by relay5.ftech.net with smtp (Exim 3.11.ftech-p5 #1)
id 11xUeG-00070L-00; Mon, 13 Dec 1999 12:32:16 +0000
Message-ID: <00aa01bf4563$33989620$841720d4@centauri>
From: "Mark Alliban" <MarkA@idnltd.com>
To: "Marcin Mazurek - Multinet SA - Poznan" <m.mazurek@multinet.pl>
Cc: <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Problem in pg_hba.conf
Date: Mon, 13 Dec 1999 12:11:34 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2110.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

I have already done this, and it completed successfully.
There is a /usr/local/pgsql/data/base/template1 directory with a lot of pg_
files in it.
Mark.

Postgres$ createdb test
Connection to database 'template1' failed.

do
initdb
You just don't have "default" database.
mazek

From bouncefilter Mon Dec 13 07:34:50 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id HAA64934
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 07:34:10 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.3/8.9.2) with SMTP id NAA26055;
Mon, 13 Dec 1999 13:33:49 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Mon, 13 Dec 1999 13:33:49 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
To: Mark Alliban <MarkA@idnltd.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Problem in pg_hba.conf
In-Reply-To: <00aa01bf4563$33989620$841720d4@centauri>
Message-ID: <Pine.BSF.3.96.991213133321.15200J-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 13 Dec 1999, Mark Alliban wrote:

I have already done this, and it completed successfully.
There is a /usr/local/pgsql/data/base/template1 directory with a lot of pg_
files in it.

You may chceck if postmaster is running...
mazek

From bouncefilter Mon Dec 13 07:47:51 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA67063
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 07:47:30 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id NAA15475;
Mon, 13 Dec 1999 13:47:25 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11xVoO-0000NZ-00; Mon, 13 Dec 1999 13:46:48 +0000
Message-ID: <3854EB45.A49B712C@sferacarta.com>
Date: Mon, 13 Dec 1999 13:49:09 +0100
From: Jose Soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
References: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
<Pine.LNX.4.20.9912090111190.389-100000@localhost.localdoma in>
<3.0.5.32.19991209092335.008f62c0@pop.mecomb.po.my>
<19991209102418.A6311@rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Ross J. Reedstrom" wrote:

Hmm, sounds like a vote for nested transactions. The JDBC driver developer
(Peter Mount) was musing that nested transaction would make large object
support easier for him, as well.

As to the other example of Oracle not forcing a rollback, I have a feeling
that this may be specific to syntax errors in an interactive session.
Implementing this sort of behavior has been discussed recently on the
hackers list, in the context of making it easier to work interactively
inside a transaction.

I would be surprised if Oracle allows non-syntax errors inside a
transaction to be ignored, or ignores anything in a non-interactive
session. How about testing an example like links, where you provide data
in a format the backend can't handle, (an out of range int or date or
something) and see how Oracle handles that.

here the test:

Connected to:
Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production

SQL> create table test(i numeric(12,3), d date);
Table created.

SQL> insert into TEST VALUES(999999999.999,'28-FEB-1999');
1 row created.

SQL> insert into TEST VALUES(111111111.999,'29-FEB-1999')
*
ERROR at line 1:
ORA-01830: date format picture ends before converting entire input
string

SQL> insert into TEST VALUES(999999999999.999,'28-FEB-1999')
*
ERROR at line 1:
ORA-01438: value larger than specified precision allows for this column
SQL> commit;
Commit complete.

select * from test;

I D
---------- ---------
1000000000 28-FEB-99

SQL> insert into TEST VALUES(1.999,'10-JAN-1999');
1 row created.

SQL> select * from test;

I D
---------- ---------
1000000000 28-FEB-99
1.999 10-JAN-99

SQL> rollback;
Rollback complete.

SQL> select * from test;
I D
---------- ---------
1000000000 28-FEB-99

Jose'

Who's right? Well, as Peter Eisentraut said, what Postgres implements is
the _definition_ of a transaction: all together, or nothing at all. This
isn't just an arbitrary rule: the validity of the relational calculus
depends on transactional semantics.

Ross

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Thu, Dec 09, 1999 at 09:23:35AM +0800, Lincoln Yeoh wrote:

At 01:18 AM 09-12-1999 +0100, Peter Eisentraut wrote:

Seriously, why do you use a transaction, when you don't want any errors
caught? Transactions are defined as everything succeeds or nothing goes.
If you want update to succeed anyhow, put it in it's own transaction
(i.e., commit before it).

I want errors caught, most errors abort everything but some errors I want
to try a different update instead, if that doesn't work then only rollback
everything.

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

The safest way would be to set a date format with SET DATESTYLE TO and use
that, possibly assisted by library formatting routines.

OK.

Link.

************

************

From bouncefilter Mon Dec 13 08:26:51 1999
Received: from relay5.ftech.net (littleblue.ftech.net [195.200.12.27])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA74497
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 08:26:48 -0500 (EST)
(envelope-from MarkA@idnltd.com)
Received: from ibm9.ftech.net ([212.32.16.79] helo=idnltd.com)
by relay5.ftech.net with smtp (Exim 3.11.ftech-p5 #1)
id 11xVaI-00087w-00; Mon, 13 Dec 1999 13:32:14 +0000
Message-ID: <00c501bf456a$e53ea0c0$841720d4@centauri>
From: "Mark Alliban" <MarkA@idnltd.com>
To: "Marcin Mazurek - Multinet SA - Poznan" <m.mazurek@multinet.pl>
Cc: <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Problem in pg_hba.conf
Date: Mon, 13 Dec 1999 13:06:39 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2110.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Yes the postmaster process is running.
nohup postmaster -i >pgserver.log 2>&1 &
The log file is empty until I try to create the database, then it gives the
error.

I have already done this, and it completed successfully.
There is a /usr/local/pgsql/data/base/template1 directory with a lot of

pg_

files in it.

You may chceck if postmaster is running...
mazek

From bouncefilter Mon Dec 13 08:48:51 1999
Received: from Cantor.suse.de (Cantor.suse.de [194.112.123.193])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA79388
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 08:48:30 -0500 (EST) (envelope-from ke@suse.de)
Received: from Galois.suse.de (Galois.suse.de [194.112.123.130])
by Cantor.suse.de (Postfix) with ESMTP
id 0B8FB32CD6; Mon, 13 Dec 1999 14:48:00 +0100 (MET)
Received: from Wotan.suse.de (Wotan.suse.de [10.10.0.1])
by Galois.suse.de (Postfix) with ESMTP
id 4571567AD; Mon, 13 Dec 1999 14:47:59 +0100 (MET)
Received: from Frechet.suse.de (Frechet.suse.de [10.10.0.123])
by Wotan.suse.de (Postfix) with ESMTP
id 1DA447F8B; Mon, 13 Dec 1999 14:47:59 +0100 (MET)
Received: (from ke@localhost)
by Frechet.suse.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id OAA31043;
Mon, 13 Dec 1999 14:47:57 +0100
Sender: ke@suse.de
To: Wim Ceulemans <wim.ceulemans@nice.be>
Cc: pgsql-general@postgreSQL.org
Subject: Re: Installation problem on Suse linux 6.3
References: <3852493A.5484BB07@nice.be>
From: Karl Eichwalder <ke@suse.de>
Date: 13 Dec 1999 14:47:57 +0100
In-Reply-To: Wim Ceulemans's message of "Sat, 11 Dec 1999 13:53:14 +0100"
Message-ID: <shwvqj9cky.fsf@Frechet.suse.de>
Lines: 20
User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Wim Ceulemans <wim.ceulemans@nice.be> writes:

| I can't seem to install the latest postgresql opn Suse linux 6.3 (kernel
| 2.2.13, glibc 2.1.2). I always get the following message when I run
| ./configure :
|
| checking for c++... c++
| checking wheather the C++ compiler (C++ ) works... no
| configure: error: installation or configuration problem': C++ compiler
| cannot create executables.

Please check, whether "libgpp" from serie "d" is installed:

rpm -q libgpp

Of cource, you'll also need the package "gpp".

--
work : ke@suse.de
Karl Eichwalder home : ke@gnu.franken.de

From bouncefilter Mon Dec 13 08:50:51 1999
Received: from arka.poznan.mtl.pl (IDENT:mazek@arka.poznan.mtl.pl
[195.116.164.132]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA79635
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 08:50:20 -0500 (EST)
(envelope-from m.mazurek@multinet.pl)
Received: from localhost (mazek@localhost)
by arka.poznan.mtl.pl (8.9.3/8.9.2) with SMTP id OAA04468;
Mon, 13 Dec 1999 14:49:37 +0100 (CET)
X-Authentication-Warning: arka.poznan.mtl.pl: mazek owned process doing -bs
Date: Mon, 13 Dec 1999 14:49:37 +0100 (CET)
From: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
X-Sender: mazek@arka
To: Mark Alliban <MarkA@idnltd.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Problem in pg_hba.conf
In-Reply-To: <00c501bf456a$e53ea0c0$841720d4@centauri>
Message-ID: <Pine.BSF.3.96.991213144832.15200Q-100000@arka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 13 Dec 1999, Mark Alliban wrote:

Yes the postmaster process is running.
nohup postmaster -i >pgserver.log 2>&1 &
The log file is empty until I try to create the database, then it gives the
error.

then the last thing I can think of, is location of data files:)
chceck enviromant variables PGDATA, PGLIB (as far as I remember:) )

mazk

From bouncefilter Mon Dec 13 09:16:52 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA86845
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 09:16:23 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
[193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id PAA00158;
Mon, 13 Dec 1999 15:16:18 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11xWox-0000PQ-00; Mon, 13 Dec 1999 14:51:27 +0000
Message-ID: <3854FA6C.D7CFD00C@sferacarta.com>
Date: Mon, 13 Dec 1999 14:53:48 +0100
From: Jose Soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to stop implicit rollback on certain errors?
References: <3.0.5.32.19991208172243.008d8b10@pop.mecomb.po.my>
<Pine.LNX.4.20.9912090111190.389-100000@localhost.localdoma in>
<3.0.5.32.19991209092335.008f62c0@pop.mecomb.po.my>
<19991209102418.A6311@rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Ross J. Reedstrom" wrote:

Hmm, sounds like a vote for nested transactions. The JDBC driver developer
(Peter Mount) was musing that nested transaction would make large object
support easier for him, as well.

As to the other example of Oracle not forcing a rollback, I have a feeling
that this may be specific to syntax errors in an interactive session.
Implementing this sort of behavior has been discussed recently on the
hackers list, in the context of making it easier to work interactively
inside a transaction.

I would be surprised if Oracle allows non-syntax errors inside a
transaction to be ignored, or ignores anything in a non-interactive
session. How about testing an example like links, where you provide data
in a format the backend can't handle, (an out of range int or date or
something) and see how Oracle handles that.

Here my test on Oracle:

Connected to:
Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production

SQL> create table test(id int primary key,i numeric(12,3), d date);
Table created.

SQL> insert into TEST VALUES(1,999999999.999,'28-FEB-1999');
1 row created.

SQL> insert into TEST VALUES(1,111111111.999,'29-FEB-1999')
ERROR at line 1:
ORA-01830: date format picture ends before converting entire input
string

SQL> insert into TEST VALUES(1,999999999999.999,'28-FEB-1999')
ERROR at line 1:
ORA-01438: value larger than specified precision allows for this column

SQL> commit;
Commit complete.

SQL> select * from test;
ID I D
---------- ---------- ---------
1 1000000000 28-FEB-99

SQL> insert into TEST VALUES(1,1.999,'10-JAN-1999')
*
ERROR at line 1:
ORA-00001: unique constraint (SCOTT.SYS_C001590) violated
SQL> insert into TEST VALUES(2,1.119,'10-MAR-1999');
1 row created.

SQL> select * from test;
ID I D
---------- ---------- ---------
1 1000000000 28-FEB-99
2 1.119 10-MAR-99
SQL> rollback;
Rollback complete.

SQL> select * from test;
ID I D
---------- ---------- ---------
1 1000000000 28-FEB-99

SQL> exit
Disconnected from Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production

Jose'

Who's right? Well, as Peter Eisentraut said, what Postgres implements is
the _definition_ of a transaction: all together, or nothing at all. This
isn't just an arbitrary rule: the validity of the relational calculus
depends on transactional semantics.

Ross

--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

On Thu, Dec 09, 1999 at 09:23:35AM +0800, Lincoln Yeoh wrote:

At 01:18 AM 09-12-1999 +0100, Peter Eisentraut wrote:

Seriously, why do you use a transaction, when you don't want any errors
caught? Transactions are defined as everything succeeds or nothing goes.
If you want update to succeed anyhow, put it in it's own transaction
(i.e., commit before it).

I want errors caught, most errors abort everything but some errors I want
to try a different update instead, if that doesn't work then only rollback
everything.

I guess that's expected, and I should insert big years using another less
ambiguous format. What is the recommended format?

The safest way would be to set a date format with SET DATESTYLE TO and use
that, possibly assisted by library formatting routines.

OK.

Link.

************

************

From bouncefilter Mon Dec 13 09:57:52 1999
Received: from relay4.ftech.net (status.ftech.net [195.200.0.89])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA94525
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 09:56:52 -0500 (EST)
(envelope-from MarkA@idnltd.com)
Received: from ibm9.ftech.net ([212.32.16.79] helo=idnltd.com)
by relay4.ftech.net with smtp (Exim 3.11.ftech-p5 #1)
id 11xWu7-0002Jy-00; Mon, 13 Dec 1999 14:56:47 +0000
Message-ID: <000c01bf4576$c147d130$841720d4@centauri>
From: "Mark Alliban" <MarkA@idnltd.com>
To: "Marcin Mazurek - Multinet SA - Poznan" <m.mazurek@multinet.pl>
Cc: <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Problem in pg_hba.conf
Date: Mon, 13 Dec 1999 14:31:32 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2110.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

The environment variables are set OK and export'd.

Yes the postmaster process is running.
nohup postmaster -i >pgserver.log 2>&1 &
The log file is empty until I try to create the database, then it gives

the

error.

then the last thing I can think of, is location of data files:)
chceck enviromant variables PGDATA, PGLIB (as far as I remember:) )

mazk

From bouncefilter Mon Dec 13 10:30:52 1999
Received: from k3.aeccom.com (IDENT:root@gate1.aeccom.com [193.158.11.51])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA02792
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 10:30:06 -0500 (EST)
(envelope-from lutzeb@aeccom.com)
Received: from ampato.aeccom.com (IDENT:root@ampato.aeccom.com [192.168.0.11])
by k3.aeccom.com (8.9.3/8.9.3) with ESMTP id QAA08764;
Mon, 13 Dec 1999 16:30:01 +0100
Received: (from lutzeb@localhost)
by ampato.aeccom.com (8.9.3/8.9.3) id QAA01840;
Mon, 13 Dec 1999 16:30:01 +0100
From: Dirk Lutzebaeck <lutzeb@aeccom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14421.4341.805191.194488@ampato.aeccom.com>
Date: Mon, 13 Dec 1999 16:29:57 +0100 (CET)
To: pgsql-general@postgreSQL.org
Subject: vacuum analyze: Tuple is too big (corrupts DB?)
X-Mailer: VM 6.71 under 21.1 (patch 4) "Arches" XEmacs Lucid

Hello,

when I vacuum analyze my db (6.5.3 on Linux) I cannot access
some data afterwards because the vacuum terminates with

ERROR: Tuple is too big: size 8596

I did pg_dump -o and read in back again, still the same error.

Eg. accessing data after vacuum results in

SELECT envpart_map.*,
envpart_map.oid AS recioid,
member.*,
member.oid AS memoid
WHERE envpart_map.member=member.oid
AND envpart_map.role > 0
AND envpart_map.envelope IN (1072343,1073358,1074472,1073722,14235
82)': pqReadData() -- backend closed the channel unexpectedly.

Where can I get on from here?

Dirk

From bouncefilter Mon Dec 13 13:52:54 1999
Received: from kant.uol.com.br (kant.uol.com.br [200.246.5.74])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA46141
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 13:51:59 -0500 (EST) (envelope-from mlemos@acm.org)
Received: from 200-191-37-216-as.acessonet.com.br
(200-191-37-216-as.acessonet.com.br [200.191.37.216])
by kant.uol.com.br (8.9.1/8.9.1) with SMTP id QAA29077
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 16:51:11 -0200 (BRST)
Date: 13 Dec 99 16:28:21 +0000
From: "Manuel Lemos" <mlemos@acm.org>
Subject: Can't I create indexes on BOOL columns?
To: pgsql-general@postgresql.org
Message-ID: <1020.16T1093T9884714mlemos@acm.org>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Mailer: THOR 2.6 (Amiga;TCP/IP)

Hello,

I am using PostgreSQL 6.4.2. and it seems I can't create indexes on BOOL
columns. I tried this:

$ psql template1
template1=> CREATE DATABASE test\g
CREATEDB
template1=> CREATE TABLE users (id INT DEFAULT 0 NOT NULL,name TEXT,preferred_name TEXT,email TEXT,alias VARCHAR (12) DEFAULT '0' NOT NULL,password TEXT,reminder TEXT,notify_any CHAR (1) DEFAULT 't' NOT NULL,notify_new CHAR(1) DEFAULT 't' NOT NULL,notify_changed CHAR(1) DEFAULT 't',edit_users CHAR(1) DEFAULT 'f')\g
CREATE
template1=> CREATE INDEX users_notify ON users (notify_any,notify_new)\g
ERROR: Can't find a default operator class for type 16

However, if I change the BOOL type to CHAR (1) it works.

Is this a bug? A configuration problem? What?

Regards,
Manuel Lemos

Web Programming Components using PHP Classes.
Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org
--
E-mail: mlemos@acm.org
URL: http://www.mlemos.e-na.net/
PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp
--

From bouncefilter Mon Dec 13 11:43:53 1999
Received: from aurora.rg.iupui.edu (aurora.rg.iupui.edu [134.68.31.122])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA19099
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 11:42:55 -0500 (EST)
(envelope-from gunther@aurora.rg.iupui.edu)
Received: from aurora.rg.iupui.edu (schadow_g.regenstrief.iupui.edu
[134.68.31.121])
by aurora.rg.iupui.edu (8.9.3/8.9.3) with ESMTP id LAA36652;
Mon, 13 Dec 1999 11:40:31 -0500 (EST)
(envelope-from gunther@aurora.rg.iupui.edu)
Message-ID: <38552195.43DA2CD9@aurora.rg.iupui.edu>
Date: Mon, 13 Dec 1999 11:40:53 -0500
From: Gunther Schadow <gunther@aurora.rg.iupui.edu>
Organization: Regenstrief Institute
X-Mailer: Mozilla 4.51 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Marcin Mazurek - Multinet SA - Poznan <m.mazurek@multinet.pl>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Large objects + JDBC
References: <Pine.BSF.3.96.991212182541.20684A-100000@arka>
Content-Type: multipart/mixed; boundary="------------B6F820358BA6A6C843DF65F9"

This is a multi-part message in MIME format.
--------------B6F820358BA6A6C843DF65F9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Marcin Mazurek - Multinet SA - Poznan wrote:

Hi,
I'm put several gifa into a table. I did as a exercise:) form psql using:
INSERT INTO images (id, data)
VALUES (3, lo_import('/usr/local/apache/servlets/images/a.gif'));

are you sure this lo_import(...) thing in the SQL will work? I have no
idea ...

but I have a problem with creating Java stream to read these data. Here
serveral lines of code I was using:
PreparedStatement ps=db.prepareStatement("select oid from imag where id=?");
ps.setInt(1,1);
ResultSet rs = ps.executeQuery();
rs.next();
InputStream is = rs.getBinaryStream(0);
and nothing happens:( Several messages from exceptions:
[13/12/1999 18:11:04:815 CET] ShowImageServlet1: 0
null
Fastpath: ERROR: lo_tell: large object descriptor (-1) out of range

I see two problems with your above Java code snippet:

#1: you SELECT oid FROM imag ... only the OID? Would you not have to select
the data? A SELECT that would match your insert above would be:

SELECT data FROM images WHERE id=?;

#2: your index in rs.getBinaryStream is zero, but if I recall correctly
the JDBC ResultSet.getXXX(int) functions start counting at 1, not at
0. So, you should have called:

PreparedStatement ps=db.prepareStatement(
"SELECT data FROM image WHERE id=?"); // select data instead of oid
ps.setInt(1,1);
ResultSet rs = ps.executeQuery();
if(rs.next()) {
InputStream is = rs.getBinaryStream(1); // start with one (1)

}

I have never done this BLOB stuff, but you might try whether this
fixes the problem. Also, with the JDBC driver comes a test that
does exactly image storing and retrieval. So you can look there
for a working example.

regards
-Gunther

--
Gunther_Schadow-------------------------------http://aurora.rg.iupui.edu
Regenstrief Institute for Health Care
1050 Wishard Blvd., Indianapolis IN 46202, Phone: (317) 630 7960
schadow@aurora.rg.iupui.edu------------------#include <usual/disclaimer>
--------------B6F820358BA6A6C843DF65F9
Content-Type: text/x-vcard; charset=us-ascii;
name="gunther.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Gunther Schadow
Content-Disposition: attachment;
filename="gunther.vcf"

begin:vcard
n:Schadow;Gunther
tel;fax:+1 317 630 6962
tel;home:+1 317 816 0516
tel;work:+1 317 630 7960
x-mozilla-html:FALSE
url:http://aurora.rg.iupui.edu
org:Regenstrief Institute
adr:;;1050 Wishard Blvd;Indianapolis;Indiana;46202;USA
version:2.1
email;internet:schadow_g@regenstrief.rg.iupui.edu
title:M.D.
fn:Gunther Schadow
end:vcard

--------------B6F820358BA6A6C843DF65F9--

From bouncefilter Mon Dec 13 13:36:54 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA44354;
Mon, 13 Dec 1999 13:36:38 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.250]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 12:28:20 -0600
Sender: ed
Message-ID: <38553CEA.8CFFD543@austin.rr.com>
Date: Mon, 13 Dec 1999 12:37:30 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org
Subject: [GENERAL/INTERFACES] Dynamically detecting need to vacuum?
References: <14421.4341.805191.194488@ampato.aeccom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm seeing a few intermittent show-stopper errors (some of which I've asked
about previously in these forums) which go away after vacuum is run. Pgsql
documentation recommends to vacuum nightly or after copying a large class
(not sure exactly what that means) or deleting a large number of records.
I'm tempted to run vaccum almost anytime I detect Pgsql errors (via perl
DBI) in order to try to salvage/retry the query at hand on the fly at the
cost of a much slower query from the user's perspective.

I'd like to learn how to programmatically calculate/detect when a vacuuming
is needed, and would like to hear any advice on how folks are successfully
doing this or think would best be done.

Any comments?

[Hackers: it'd be nice to have pgsql optionally take care of this...]

I'm using Pg 6.5.2 on RH Linux 6.0 2.2.5-15smp via perl DBI/DBD::Pg...

Thanks in advance,
Ed Loehr

From bouncefilter Mon Dec 13 14:19:55 1999
Received: from hermes.iol.cz (hermes.iol.cz [194.228.2.36])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA64340
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 14:19:26 -0500 (EST)
(envelope-from robert@robert.cz)
Received: from robert.cz ([194.228.143.10]) by hermes.iol.cz
(Post.Office MTA v3.5.3 release 223
ID# 631-64078U55000L55000S0V35) with ESMTP id cz;
Mon, 13 Dec 1999 20:18:49 +0100
Message-ID: <3855477C.11EF5AAF@robert.cz>
Date: Mon, 13 Dec 1999 20:22:36 +0100
From: Robert <robert@robert.cz>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
CC: lamar.owen@wgcr.org
Subject: With what options RPM was compiled? ( Was: Czech Win1250 sorting q)
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
<m2wvqjpg4n.fsf@chameleon.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I've upgraded to 6.5.3 from RPM but 'set client_encoding' still says
'unknow variable'. How can I know whether RPM was compiled
with --enable-locale and --with-mb=LATIN2? And if it wasn't,
could I humbly suggest it for next version?

If I knew it wasn't compiled with the right options, I could just
take a deep breath and try to recompile it myself. However, there's
no info about compile options used to prepare RPM and I'm not
sure I'm not doing some trivial mistake... I'd like to avoid recompiling
the whole thing if I can.

- Robert

P.S. David, thanks for your help so far. I forgot to send my last mail
to the list and sent it to your address only instead. Sorry.

David Sauer wrote:

"Robert" == Robert <robert@robert.cz> writes:

Robert> netkof=> show client encoding;
Robert> ERROR: parser: parse error at or

Sorry, my mistake. The right name is 'client_encoding' (with underscore).

Example:

david=> set client_encoding to 'latin2';
SET VARIABLE

Robert> Hmm, what did you say I should write? Well, this is PG6.5.2
Robert> installed from RPM, should it be compiled with some special
Robert> option? Thanks.

Yes, postgres must be compiled with --enable-locale and --with-mb=LATIN2.
And, I'am not sure, but may want upgrade to 6.5.3.

--
* David Sauer, student of Czech Technical University
* electronic mail: davids@penguin.cz (mime compatible)

************

From bouncefilter Mon Dec 13 14:41:55 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA69319
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 14:41:43 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id OAA27067;
Mon, 13 Dec 1999 14:41:34 -0500
Message-ID: <38554BE5.66A09278@wgcr.org>
Date: Mon, 13 Dec 1999 14:41:25 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert <robert@robert.cz>
CC: pgsql-general@postgreSQL.org
Subject: Re: With what options RPM was compiled? ( Was: Czech Win1250 sorting
q)
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
<m2wvqjpg4n.fsf@chameleon.localdomain>
<3855477C.11EF5AAF@robert.cz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert wrote:

I've upgraded to 6.5.3 from RPM but 'set client_encoding' still says
'unknow variable'. How can I know whether RPM was compiled
with --enable-locale and --with-mb=LATIN2? And if it wasn't,
could I humbly suggest it for next version?

The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
with --with-mb=LATIN2.

(NOTE: The following procedure tells how to rebuild the RPM set. Before
doing so, make sure you have a full development system -- C and C++
compilers, Tcl/Tk (and by extension X11), python-devel, perl, and the
latest rpm (rpm-3.0.2 or 3.0.3).)

To change that, get the postgresql-6.5.3-2.src.rpm from my site
(http://www.ramifordistat.net/postgres), and do the following (as root):

1.) rpm -i postgresql-6.5.3-2.src.rpm
2.) cd /usr/src/redhat/SPECS
3.) Open postgresql-6.5.3-2.spec in your favorite editor.
4.) Find the line with configure, but not the one inside the alpha
conditional.
5.) Change the options as you need.
6.) Change the line starting with Release: to be something other than
2 -- maybe '2cz' is good. This line is near the top.
7.) Save and close the spec file.
8.) Rename the spec file to be like the Release -- for a Release of
'2cz', make the file 'postgresql-6.5.3-2cz.spec -- this helps prevent
confusion.
9.) Execute 'rpm -ba postgresql-6.5.3-2cz.spec' -- this should, if
you have all the needed compilers and development libraries installed,
build the package, and create the binary rpms in the directory
/usr/src/redhat/RPMS/i386 (assuming you're compiling for i386).
10.) You can now install the binary RPMs that you have just built.

HTH

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Mon Dec 13 15:04:55 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA74357
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 15:03:59 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.58.250]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 13:55:44 -0600
Sender: ed
Message-ID: <38555166.32D789CA@austin.rr.com>
Date: Mon, 13 Dec 1999 14:04:54 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
References: <14421.4341.805191.194488@ampato.aeccom.com>
<38553CEA.8CFFD543@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Question: is it safe to insert/update/delete during VACUUM?

From bouncefilter Mon Dec 13 15:25:57 1999
Received: from geeks.linux.com (root@216.200.201.220.linux.com
[216.200.201.220] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id PAA76782
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 15:25:24 -0500 (EST)
(envelope-from chewie@wookimus.net)
Received: from geeks.linux.com (chewie@geeks.linux.com [216.200.201.220])
by geeks.linux.com (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id MAA02010;
Mon, 13 Dec 1999 12:25:15 -0800
Date: Mon, 13 Dec 1999 12:25:15 -0800 (PST)
From: ^chewie <chewie@wookimus.net>
X-Sender: chewie@geeks.linux.com
To: Manuel Lemos <mlemos@acm.org>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Can't I create indexes on BOOL columns?
In-Reply-To: <1020.16T1093T9884714mlemos@acm.org>
Message-ID: <Pine.LNX.4.10.9912131216180.1964-100000@geeks.linux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 13 Dec 1999, Manuel Lemos wrote:

Hello,

I am using PostgreSQL 6.4.2. and it seems I can't create indexes on
BOOL columns. I tried this:

...snip...

However, if I change the BOOL type to CHAR (1) it works.

I'm not a developer, so I don't know if it's a bug or a logic error
you're pointing out, or even if it's an error at all. However, I could
rationalize that it is not an error on the premise that BOOLEAN
identifiers can only have two values: true or false.

Obviously, you cannot use a UNIQUE index on such an column. A Clustered
index would not do much better, logically, since you're only splitting
up the data into two groups. Therefore, what is the point of indexing
on boolean columns, really? I suppose it would depend upon the data in
the table. If you see one value predominantly over the other, splitting
out the smaller group via the index *may* help your search. However, if
the values are fairly even in proportion, you won't gain much.

I'd say stick with your work-around, and post the question to the devel
team.

----------------------------------------------------------------
Chad Walstrom mailto:chewie@wookimus.net
a.k.a ^chewie, gunnarr http://wookimus.net/~chewie

Gnupg = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
----------------------------------------------------------------

From bouncefilter Mon Dec 13 17:44:57 1999
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
by hub.org (8.9.3/8.9.3) with SMTP id RAA07063
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 17:44:40 -0500 (EST)
(envelope-from charlesdotcom@yahoo.com)
Received: (qmail 10819 invoked by uid 60001); 13 Dec 1999 21:11:01 -0000
Message-ID: <19991213211101.10818.qmail@web1406.mail.yahoo.com>
Received: from [63.195.80.23] by web1406.mail.yahoo.com;
Mon, 13 Dec 1999 13:11:01 PST
Date: Mon, 13 Dec 1999 13:11:01 -0800 (PST)
From: Charles Martin <charlesdotcom@yahoo.com>
Subject: grinding to a halt?
To: pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

We are running a web/db site with PostgreSQL 6.5.2 under FreeBSD 3.3-STABLE
(other components of the system are Apache 1.3.9 and PHP 3.0.12). We are
trying to load in content via the web application, which involves a lot of db
selects, inserts, and updates, and find that the db grinds to a halt. I can
see a bunch of postgres processes chewing system resources, but the web pages
never return. Apache and the OS itself seem to be ok, just slow, but Postgres
is not responding.

The system in its current prototype state does not make use of transactions;
inserts into the database just occur as raw inserts. Could this be the cause
of my problem? Or is there some fundamental thing I need to do in setting up
Postgres so that it works efficiently?

I assume I have simply overlooked something obvious, because the db appears to
be unusuable and I know that is not the case.

What other information about my setup would help to debug my problem?

Thanks.

Charles

__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

From bouncefilter Mon Dec 13 15:37:56 1999
Received: from atlas.synflux.com.au (umar@atlas.synflux.com.au [203.63.24.8])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA80838
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 15:37:37 -0500 (EST)
(envelope-from umar@atlas.synflux.com.au)
Received: from localhost (umar@localhost)
by atlas.synflux.com.au (8.8.6/8.8.6) with SMTP id IAA04295
for <pgsql-general@postgreSQL.org>; Tue, 14 Dec 1999 08:25:18 +1100
Date: Tue, 14 Dec 1999 08:25:18 +1100 (EST)
From: Umar Goldeli <umar@atlas.synflux.com.au>
To: pgsql-general@postgreSQL.org
Subject: unsubscribe
In-Reply-To: <38555166.32D789CA@austin.rr.com>
Message-ID: <Pine.LNX.3.93.991214082449.4141B-100000@atlas.synflux.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

From bouncefilter Mon Dec 13 16:47:58 1999
Received: from sofa.c-c.de (line6.hamm.netsurf.de [195.180.80.6])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA94027
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 16:47:01 -0500 (EST)
(envelope-from t_antepoth@hamm.netsurf.de)
Received: from sofa.c-c.de (t_antepoth@sofa.c-c.de [192.168.100.254])
by sofa.c-c.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id
WAA07797; Mon, 13 Dec 1999 22:32:16 +0100
Date: Mon, 13 Dec 1999 22:32:16 +0100 (CET)
From: Thomas Antepoth <t_antepoth@hamm.netsurf.de>
X-Sender: t_antepoth@sofa.c-c.de
To: Wim Ceulemans <wim.ceulemans@nice.be>
cc: Postgresql Mailinglist <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Installation problem on Suse linux 6.3
In-Reply-To: <3852493A.5484BB07@nice.be>
Message-ID: <Pine.LNX.4.21.9912132215420.2861-100000@sofa.c-c.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.org id QAA94129

On Sat, 11 Dec 1999, Wim Ceulemans wrote:

I can't seem to install the latest postgresql opn Suse linux 6.3 (kernel
2.2.13, glibc 2.1.2). I always get the following message when I run
./configure :

checking for c++... c++
checking wheather the C++ compiler (C++ ) works... no
configure: error: installation or configuration problem': C++ compiler
cannot create executables.

Yeah right.

It means you have to install gpp and libgpp via yast (series d).

If you want to compile --with-tcl you�ll have to install the tcl/tk header
libs as well. (Series TCL, Packet tcld)

Remember to delete your config.cache as well if you ran into these
problems. I didn�t for the first time and i ran into a compiler error
(gettimeofday - too few arguments in postmaster.c) afterwards.

After these things postgres compiles just fine.

HTH, HAND

t++

--
This mail had been created using Linux. It is therefore free of all
Microsoft(tm) OS based virii, conforms with almost any widely recognized
open standards and is best read with *any* mailclient using fixed fonts.
Spam is processed at the modest price of $500 only at this site.

From bouncefilter Mon Dec 13 18:24:12 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA14116;
Mon, 13 Dec 1999 18:23:20 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:63672 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sJLzJ163911>; Tue, 14 Dec 1999 00:23:01 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11xetI-0001jh-00; Tue, 14 Dec 1999 00:28:28 +0100
Date: Tue, 14 Dec 1999 00:28:28 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Ed Loehr <ELOEHR@austin.rr.com>
cc: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org
Subject: Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to
vacuum?
In-Reply-To: <38553CEA.8CFFD543@austin.rr.com>
Message-ID: <Pine.LNX.4.20.9912132250040.361-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-13, Ed Loehr mentioned:

documentation recommends to vacuum nightly or after copying a large class
(not sure exactly what that means) or deleting a large number of records.

copying -- as invoked via the COPY command (in general this means
inserting, though)
large -- probably anything with triple-digit row counts
class -- table, relation; in general rows, records, data, stuff

[Hackers: it'd be nice to have pgsql optionally take care of this...]

There are some disabled code fragments that take into account a "vacuum
daemon". It's even on the TODO list, but vacuum itself needs to be sorted
out first.

Sorry, no free lunch here, probably.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Mon Dec 13 18:24:03 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA14118
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 18:23:28 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:63881 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sJLzQ178244>; Tue, 14 Dec 1999 00:23:08 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11xetO-0001jj-00; Tue, 14 Dec 1999 00:28:34 +0100
Date: Tue, 14 Dec 1999 00:28:34 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Lamar Owen <lamar.owen@wgcr.org>
cc: Robert <robert@robert.cz>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was: Czech
Win1250 sorting q)
In-Reply-To: <38554BE5.66A09278@wgcr.org>
Message-ID: <Pine.LNX.4.20.9912132245300.361-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-13, Lamar Owen mentioned:

The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
with --with-mb=LATIN2.

Perhaps the next set of RPMs could be compiled with --enable-locale and
--with-mb=SQL_ASCII. At least do it like now: the non-locale/non-multibyte
version for performance, and the locale/mb version for features. Please
note that SQL_ASCII doesn't mean that the db cannot support any other
encoding, it's just the default encoding initdb uses.

The questioner could then use this RPM and initialize with initdb -e
LATIN2, if he chooses.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Mon Dec 13 18:31:57 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA17402
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 18:31:11 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id SAA27481;
Mon, 13 Dec 1999 18:31:13 -0500
Message-ID: <385581B6.7660632B@wgcr.org>
Date: Mon, 13 Dec 1999 18:31:02 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: Robert <robert@robert.cz>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was:
CzechWin1250 sorting q)
References: <Pine.LNX.4.20.9912132245300.361-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Eisentraut wrote:

On 1999-12-13, Lamar Owen mentioned:

The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
with --with-mb=LATIN2.

Perhaps the next set of RPMs could be compiled with --enable-locale and
--with-mb=SQL_ASCII. At least do it like now: the non-locale/non-multibyte
version for performance, and the locale/mb version for features. Please
note that SQL_ASCII doesn't mean that the db cannot support any other
encoding, it's just the default encoding initdb uses.

That's a thought. On my TODO.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Mon Dec 13 18:35:58 1999
Received: from mail.rdc1.md.home.com (imail@ha1.rdc1.md.home.com [24.2.2.66])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA18659
for <pgsql-general@postgresql.org>;
Mon, 13 Dec 1999 18:35:23 -0500 (EST)
(envelope-from pgajer@chow.mat.jhu.edu)
Received: from math.jhu.edu ([24.5.88.152]) by mail.rdc1.md.home.com
(InterMail v4.01.01.00 201-229-111) with ESMTP
id <19991213233521.PTDF26939.mail.rdc1.md.home.com@math.jhu.edu>
for <pgsql-general@postgresql.org>; Mon, 13 Dec 1999 15:35:21 -0800
Sender: pawel
Message-ID: <385583B2.A836EB30@math.jhu.edu>
Date: Mon, 13 Dec 1999 18:39:30 -0500
From: pawel <pgajer@chow.mat.jhu.edu>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13-14mdk i586)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Precompilation error (ecpg)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
when trying to precompile the following code with

ecpg -I/usr/include/pgsql ecpg_test.pc

I am getting the following error message

ecpg_test.pc:27: invalid datatype 'zipcode_record'

this is probably something very simple, but I don't get this error,
when processing the code with Oracle.
I would appreciate any feedback.
thanks
pawel

-------- ecpg_test.pc file -------------
#include <stdio.h>
#include <string.h>

typedef struct {
int zip;
} zipcode_record;

EXEC SQL INCLUDE sqlca;
void add_customer();

void main() {
/* just a test */
}

void add_customer() {
EXEC SQL BEGIN DECLARE SECTION;
zipcode_record zrec; /* line 27 */
EXEC SQL END DECLARE SECTION;
}

From bouncefilter Mon Dec 13 19:21:59 1999
Received: from aventurine.sge.net (aventurine.sge.net [152.91.14.25])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA28820
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 19:21:40 -0500 (EST)
(envelope-from G.MacMinn@nca.gov.au)
Received: from cadmium.sge.net (cadmium.sge.net [152.91.9.5])
by aventurine.sge.net (8.9.3/8.9.3) with ESMTP id LAA56903
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:21:37 +1100 (EST)
Received: (from uucp@localhost) by cadmium.sge.net (8.9.3/8.9.3) id LAA11314
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:21:36 +1100 (EST)
Received: from nodnsquery(10.1.2.11) by cadmium.sge.net via smap (V5.0)
id xma011231; Tue, 14 Dec 99 11:21:28 +1100
Received: from amber (amber-int2.sge.net [10.1.2.254])
by kryptonite.sge.net (8.9.3/8.9.3) with SMTP id LAA44193
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:21:27 +1100 (EST)
Message-Id: <s85627d6.018@syd_aux.nca.gov.au>
X-Mailer: Novell GroupWise 5.2
Date: Tue, 14 Dec 1999 11:18:41 +1100
From: "Gary MacMinn" <G.MacMinn@nca.gov.au>
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] Clients in different Time Zones
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id TAA28890

Hi All,

I have written a small help desk database using pgsql, Linux, apache and PHP3 to generate HTML pages. The system in itself works well but I have staff from four different time zones using the system.

As it stands now, when a new job is entered, the date in and time in fields are primed with the current date and time using date("d-M-Y") and date("H:i:s", time()). This is fine but it inserts the details from the server time zone (fine for me but the others are up to two hours off).

Is there any way that these fields could be primed with a time and date, taking the client's local time zone or local system time into account so that they see their local time instead of my server time?

TIA,

Gary MacMinn

From bouncefilter Mon Dec 13 19:21:58 1999
Received: from web1302.mail.yahoo.com (web1302.mail.yahoo.com [128.11.23.152])
by hub.org (8.9.3/8.9.3) with SMTP id TAA28825
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 19:21:41 -0500 (EST)
(envelope-from marclinux@yahoo.com)
Received: (qmail 29788 invoked by uid 60001); 14 Dec 1999 00:21:12 -0000
Message-ID: <19991214002112.29787.qmail@web1302.mail.yahoo.com>
Received: from [148.233.214.168] by web1302.mail.yahoo.com;
Mon, 13 Dec 1999 16:21:12 PST
Date: Mon, 13 Dec 1999 16:21:12 -0800 (PST)
From: Marcos Hernandez <marclinux@yahoo.com>
Subject: subscribe
To: pgsql-general@postgreSQL.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

subscribe
end

__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

From bouncefilter Mon Dec 13 21:51:00 1999
Received: from news.tht.net (news.hub.org [216.126.91.242])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA61094;
Mon, 13 Dec 1999 21:50:19 -0500 (EST)
(envelope-from news@news.tht.net)
Received: (from news@localhost) by news.tht.net (8.9.3/8.9.3) id VAA95321;
Mon, 13 Dec 1999 21:31:29 GMT (envelope-from news)
X-Authentication-Warning: news.tht.net: news set sender to <news> using -f
Message-ID: <3855A863.C0D9FC29@prodigy.net>
Date: Mon, 13 Dec 1999 21:16:03 -0500
From: Andy Marsh <marsh@prodigy.net>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD compaq (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Memory bug
References: <Imh34.20953$Tp.847209@typ11.nn.bcandid.com>
<#JZwP7RQ$GA.299@cppssbbsa04>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsgroups: comp.databases.postgresql.patches,
comp.databases.postgresql.questions,
microsoft.public.sqlserver.misc, microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.programming,
microsoft.public.sqlserver.server
Lines: 37
To: pgsql-patches@postgresql.org.pgsql-questions@postgresql.org

Bob,

We have a SQL 7.0 database that frequently runs out of memory and crash's, the
system has a GIG of RAM and is set up with the default memory settings.

I'm seeing an increase in the amount of memory used by the process called
SQLSERVR.EXE and to date I haven't seen it release any, just playing around with
the Enterprise Manager increases the amount of memory in use by the process and
in the past hour it hasn't dropped.

We are adding a lot of data to the system currently through a front end app that
uses named pipes, have you run into this problem at all?

Bob Pfeiff wrote:

The SQL Server will cache data and query plans and maintain them in cache
for performance reasons. There are memory management processes in SQL
Server to decide when to clear items from cache based on aging and on other
memory requirements on the system. Unless you're processes are doing
operations like loading an entire large table in cache (e.g., select * from
somebigtable), I wouldn't expect it to dominate the server's memory.

There is a configuration option to set the maximum amount of system memory
that SQL Server will use, but you shouldn't have to set it unless the SQL
Server is regularly monopolizing memory resources at the expense of other
applications or the OS.
--
Bob Pfeiff
MCDBA, MCSD, MCSE, MCT, SQL Server MVP
Practice Leader, Data Management
CIBER, Washington, DC

From bouncefilter Mon Dec 13 23:09:01 1999
Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net
[207.217.121.31]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA77191
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 23:08:26 -0500 (EST)
(envelope-from regem@earthlink.net)
Received: from regem.penguinpowered.com
(pool0095.cvx31-bradley.dialup.earthlink.net [209.179.146.95])
by emu.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id UAA19326
for <pgsql-general@postgreSQL.org>;
Mon, 13 Dec 1999 20:08:24 -0800 (PST)
Received: from earthlink.net (regem [127.0.0.1])
by regem.penguinpowered.com (8.9.3/8.8.7) with ESMTP id UAA05749
for <pgsql-general@postgreSQL.org>; Mon, 13 Dec 1999 20:06:29 -0800
Sender: jared@regem.penguinpowered.com
Message-ID: <3855C245.906060F4@earthlink.net>
Date: Mon, 13 Dec 1999 20:06:29 -0800
From: Jared King <regem@earthlink.net>
Reply-To: jared_king@yahoo.com
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

subscribe
end

From bouncefilter Tue Dec 14 01:46:03 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA70155
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 01:45:07 -0500 (EST)
(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.8/MAPS) with
ESMTP id IAA15478; Tue, 14 Dec 1999 08:49:24 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
IAA00362; Tue, 14 Dec 1999 08:45:03 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <3855E76F.9F183684@albourne.com>
Date: Tue, 14 Dec 1999 08:45:03 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Loehr <ELOEHR@austin.rr.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
References: <14421.4341.805191.194488@ampato.aeccom.com>
<38553CEA.8CFFD543@austin.rr.com> <38555166.32D789CA@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ed Loehr wrote:

Question: is it safe to insert/update/delete during VACUUM?

It is supposed to be (MVCC should take care of it), but in practice I've
got bad experiences with it. The system should at least have a very low
load. You can get dead-lock errors, as the tables being vacuumed are
locked for a long time and then inaccessible to other queries (that's
unavoidable, but still annoying). And a couple of times something went
wrong and I ended up with duplicate tuples in my tables -- really
duplicate, including the oid's. That required a table
dump/sort/uniq/load to fix :-(.

Adriaan

From bouncefilter Tue Dec 14 02:32:03 1999
Received: from nereus.informatik.uni-bonn.de (nereus.informatik.uni-bonn.de
[131.220.4.20]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA80235
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 02:31:41 -0500 (EST)
(envelope-from Elmar.Haneke@gmx.de)
From: Elmar.Haneke@gmx.de
Received: from localhost (jod.informatik.uni-bonn.de [131.220.9.99])
by nereus.informatik.uni-bonn.de (8.8.8/8.8.8) with ESMTP id IAA10824
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 08:21:27 +0100 (MET)
Received: from Spooler by localhost (Mercury/32 v3.01a) ID MO004880;
14 Dec 99 08:31:40 -0000
Received: from spooler by haneke.de (Mercury/32 v3.01a);
14 Dec 99 08:31:05 -0000
To: pgsql-general@postgreSQL.org
Subject: Access rescrictions
Date: Tue, 14 Dec 1999 8:30:51 -0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Mailer: Mercury/32 v3.01a
Message-ID: <A97E85E30@haneke.de>

Hello,

I'm looking for an solution to restrict the access to show an part of an Table only:
In an customer-database it should be possible to list the bills of an certain customer,
but it should be restricted to generate/summarize a list of all bills.

"SELECT * FROM Bills" should be restricted
"SELECT * FROM Bills WHERE CustomerID=?" should be allowed for any CustomerID.

Is there an solution to this problem in PostgreSQL?

Elmar

From bouncefilter Tue Dec 14 04:27:04 1999
Received: from innocence.interface-business.de
(innocence.interface-business.de [193.101.57.202])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA01139
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 04:26:48 -0500 (EST)
(envelope-from gerald@mauz.interface-business.de)
Received: from mauz.interface-business.de (mauz.interface-business.de
[193.101.57.233])
by innocence.interface-business.de with ESMTP id KAA52943;
Tue, 14 Dec 1999 10:26:47 +0100 (CET)
Received: (from gerald@localhost)
by mauz.interface-business.de (8.8.8/8.8.8) id KAA22938;
Tue, 14 Dec 1999 10:26:47 +0100 (CET) (envelope-from gerald)
Message-ID: <XFMail.991214102647.postgres@taifun.interface-business.de>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <38555166.32D789CA@austin.rr.com>
Date: Tue, 14 Dec 1999 10:26:47 +0100 (CET)
Reply-To: gerald@interface-business.de
Organization: Interface Business
Sender: gerald@mauz.interface-business.de
From: postgres@taifun.interface-business.de
To: Ed Loehr <ELOEHR@austin.rr.com>
Subject: Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
Cc: pgsql-general@postgreSQL.org

Hi Ed,

Question: is it safe to insert/update/delete during VACUUM?

We have done a stress test on FreeBSD 2.2.7 with PG 6.4.3 and
6.5.2 with 2 processes in parallel: the first runs VACUUM VERBOSE
in a loop and the second does INSERT/UPDATE/DELETE's.
The database crashed after <5 mins, with different errors (not
only "duplicate tuples").

Howto VACUUM an online database?

Gerald

From bouncefilter Tue Dec 14 06:08:05 1999
Received: from office.knowledge.com (office.knowledge.com [195.40.167.196])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA22573
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 06:07:10 -0500 (EST)
(envelope-from Mark.Jewiss@knowledge.com)
Received: from mark (helo=localhost)
by office.knowledge.com with local-esmtp (Exim 2.10 #1)
id 11xpmx-0006CR-00; Tue, 14 Dec 1999 11:06:39 +0000
Date: Tue, 14 Dec 1999 11:06:39 +0000 (GMT)
From: Mark Jewiss <Mark.Jewiss@knowledge.com>
To: Gary MacMinn <G.MacMinn@nca.gov.au>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Clients in different Time Zones
In-Reply-To: <s85627d6.018@syd_aux.nca.gov.au>
Message-ID: <Pine.BSO.4.10.9912141103350.24474-100000@office.knowledge.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

On Tue, 14 Dec 1999, Gary MacMinn wrote:

As it stands now, when a new job is entered, the date in and time in
fields are primed with the current date and time using date("d-M-Y")
and date("H:i:s", time()). This is fine but it inserts the details
from the server time zone (fine for me but the others are up to two
hours off).

Do the different sites run the PHP application from a local server, and
connect to a remote database? If this is the case, one solution is to
change the code in the PHP script so that you set a variable relevant to
the time zone.

You then use this to alter time data you select from tables before
displaying it on screen. It could work by just being an offset in hours
from the database time server.

Or if everyone uses the same script then you could tell by the users login
which site they are in and then change the time accordingly.

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com

From bouncefilter Tue Dec 14 12:02:39 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA05529
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 12:01:40 -0500 (EST)
(envelope-from samelash@ix.netcom.com)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net
[207.69.200.246]) by trends.net (8.8.8/8.8.8) with ESMTP id LAA18637
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:23:37 -0500 (EST)
Received: from amd (nyc-ny74-40.ix.netcom.com [209.109.227.232])
by smtp10.atl.mindspring.net (8.9.3/8.8.5) with SMTP id LAA28028;
Tue, 14 Dec 1999 11:22:32 -0500 (EST)
Message-Id: <3.0.3.32.19991214111457.010f8fac@popd.ix.netcom.com>
X-Sender: samelash@popd.ix.netcom.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 14 Dec 1999 11:14:57 +0000
To: gerald@interface-business.de, pgsql-general@postgreSQL.org
From: Samy Elashmawy <samelash@ix.netcom.com>
Subject: Re: [GENERAL] Announce: Postgres Access Control Tool
In-Reply-To: <XFMail.991214162204.postgres@taifun.interface-business.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

What is paco ??

At 04:22 PM 12/14/1999 +0100, postgres@taifun.interface-business.de wrote:

Hi all,

a new version of PACO is available at ftp://ftp.sftech.de/pub/paco/

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

Gerald

************

From bouncefilter Tue Dec 14 10:22:08 1999
Received: from innocence.interface-business.de
(innocence.interface-business.de [193.101.57.202])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA78124
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 10:22:05 -0500 (EST)
(envelope-from gerald@mauz.interface-business.de)
Received: from mauz.interface-business.de (mauz.interface-business.de
[193.101.57.233])
by innocence.interface-business.de with ESMTP id QAA80003
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 16:22:04 +0100 (CET)
Received: (from gerald@localhost)
by mauz.interface-business.de (8.8.8/8.8.8) id QAA23536
for pgsql-general@postgreSQL.org; Tue, 14 Dec 1999 16:22:04 +0100 (CET)
(envelope-from gerald)
Message-ID: <XFMail.991214162204.postgres@taifun.interface-business.de>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Tue, 14 Dec 1999 16:22:04 +0100 (CET)
Reply-To: gerald@interface-business.de
Organization: Interface Business
Sender: gerald@mauz.interface-business.de
From: postgres@taifun.interface-business.de
To: pgsql-general@postgreSQL.org
Subject: Announce: Postgres Access Control Tool

Hi all,

a new version of PACO is available at ftp://ftp.sftech.de/pub/paco/

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

Gerald

From bouncefilter Tue Dec 14 10:29:08 1999
Received: from secure.cybernaut.com (secure.cybernaut.com [207.33.154.240])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA78833
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 10:29:00 -0500 (EST)
(envelope-from brian@cybernaut.com)
Received: from specter (gatekeeper.fresno.cybernaut.com [24.30.110.76])
by secure.cybernaut.com (8.9.1a/8.9.1) with SMTP id HAA09641;
Tue, 14 Dec 1999 07:27:15 -0800
X-Authentication-Warning: secure.cybernaut.com: Host
gatekeeper.fresno.cybernaut.com [24.30.110.76] claimed to be
specter
From: "Brian Haney" <brian@cybernaut.com>
To: "Mark Alliban" <MarkA@idnltd.com>,
"Marcin Mazurek - Multinet SA - Poznan" <m.mazurek@multinet.pl>
Cc: <pgsql-general@postgreSQL.org>
Subject: RE: [GENERAL] Problem in pg_hba.conf
Date: Tue, 14 Dec 1999 07:25:58 -0800
Message-ID: <001501bf4647$85aef000$8101a8c0@specter.fresno.cybernaut.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <000c01bf4576$c147d130$841720d4@centauri>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal

Are the permissions of the PGDATA directories and files owned by user
'postgres'?

-----Original Message-----
From: owner-pgsql-general@postgreSQL.org
[mailto:owner-pgsql-general@postgreSQL.org]On Behalf Of Mark Alliban
Sent: Monday, December 13, 1999 6:32 AM
To: Marcin Mazurek - Multinet SA - Poznan
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Problem in pg_hba.conf

The environment variables are set OK and export'd.

Yes the postmaster process is running.
nohup postmaster -i >pgserver.log 2>&1 &
The log file is empty until I try to create the database, then it gives

the

error.

then the last thing I can think of, is location of data files:)
chceck enviromant variables PGDATA, PGLIB (as far as I remember:) )

mazk

************

From bouncefilter Tue Dec 14 10:55:09 1999
Received: from hermes.iol.cz (hermes.iol.cz [194.228.2.36])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA86830
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 10:54:36 -0500 (EST)
(envelope-from robert@robert.cz)
Received: from robert.cz ([194.228.143.169]) by hermes.iol.cz
(Post.Office MTA v3.5.3 release 223
ID# 631-64078U55000L55000S0V35) with ESMTP id cz;
Tue, 14 Dec 1999 16:53:59 +0100
Message-ID: <385668FC.298231E6@robert.cz>
Date: Tue, 14 Dec 1999 16:57:48 +0100
From: Robert <robert@robert.cz>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Lamar Owen <lamar.owen@wgcr.org>, pgsql-general@postgreSQL.org
Subject: Re: With what options RPM was compiled? ( Was: Czech Win1250 sorting
q)
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
<m2wvqjpg4n.fsf@chameleon.localdomain>
<3855477C.11EF5AAF@robert.cz> <38554BE5.66A09278@wgcr.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks for everybody's help, I got it working now. An observation:
The steps Lamar described really created a binary RPM, however
the pg_encoding utility isn't included (it was built though). Similarly
'createdb -E LATIN2 xx' from README.mb doesn't work, while
create database with encoding = 'latin2' works OK.

- Robert

PS If anybody's is in urgent need, I can put those rpms online before
Lamar builts the new version with multibyte support enabled - just let
me know you're interested.

Lamar Owen wrote:

Robert wrote:

I've upgraded to 6.5.3 from RPM but 'set client_encoding' still says
'unknow variable'. How can I know whether RPM was compiled
with --enable-locale and --with-mb=LATIN2? And if it wasn't,
could I humbly suggest it for next version?

The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
with --with-mb=LATIN2.

(NOTE: The following procedure tells how to rebuild the RPM set. Before
doing so, make sure you have a full development system -- C and C++
compilers, Tcl/Tk (and by extension X11), python-devel, perl, and the
latest rpm (rpm-3.0.2 or 3.0.3).)
...

From bouncefilter Tue Dec 14 11:06:09 1999
Received: from jasper.southwind.net (ssaner@jasper.southwind.net
[206.53.103.7]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA91177
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 11:05:57 -0500 (EST)
(envelope-from ssaner@jasper.southwind.net)
Received: (from ssaner@localhost)
by jasper.southwind.net (8.9.3/8.9.3) id KAA06443
for pgsql-general@postgresql.org; Tue, 14 Dec 1999 10:05:55 -0600 (CST)
Date: Tue, 14 Dec 1999 10:05:55 -0600
From: Steven Saner <ssaner@southwind.net>
To: pgsql-general@postgresql.org
Subject: pg_psort files
Message-ID: <19991214100555.C771@jasper.southwind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.15i

I have a fairly simple database (two tables and a few indecies). In
the data/base/xxxx directory I find the following files:

-rw------- 1 postgres postgres 7734146 Dec 14 06:36 pg_psort.13268.0
-rw------- 1 postgres postgres 7707487 Dec 14 06:36 pg_psort.13268.1
-rw------- 1 postgres postgres 7776602 Dec 14 06:36 pg_psort.13268.2
-rw------- 1 postgres postgres 936026112 Dec 14 07:20 pg_psort.13268.3
-rw------- 1 postgres postgres 8208384 Dec 14 06:36 pg_psort.13268.4
-rw------- 1 postgres postgres 15699116 Dec 14 06:36 pg_psort.13268.5
-rw------- 1 postgres postgres 19002244 Dec 14 06:36 pg_psort.13268.6
-rw------- 1 postgres postgres 2097152 Dec 9 06:33 pg_psort.25350.0
-rw------- 1 postgres postgres 2146304 Dec 9 06:33 pg_psort.25350.1
-rw------- 1 postgres postgres 2277376 Dec 9 06:33 pg_psort.25350.2
-rw------- 1 postgres postgres 1597440 Dec 9 06:33 pg_psort.25350.3
-rw------- 1 postgres postgres 1064960 Dec 9 06:33 pg_psort.25350.4
-rw------- 1 postgres postgres 1327104 Dec 9 06:33 pg_psort.25350.5
-rw------- 1 postgres postgres 0 Dec 9 06:32 pg_psort.25350.6

I have another database that is almost identical on a different
machine. There are no pg_psort.xxxx files there. I am wondering:

1. What are these files?
2. Do I need them?
3. If I don't need them is it safe to remove them?

--
==================================================================
Steven Saner SouthWind Internet Access, Inc.
ssaner@southwind.net Systems/Network Administrator
http://www2.southwind.net/~ssaner http://www.southwind.net
263-7963 Wichita (800)525-7963

From bouncefilter Tue Dec 14 11:56:49 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA01789
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:56:03 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from www.wgcr.org (root@www.wgcr.org [206.74.232.194])
by trends.net (8.8.8/8.8.8) with ESMTP id LAA19057
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:28:45 -0500 (EST)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id LAA28619;
Tue, 14 Dec 1999 11:24:04 -0500
Message-ID: <38566F1E.7EFDAFF9@wgcr.org>
Date: Tue, 14 Dec 1999 11:23:58 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert <robert@robert.cz>
CC: pgsql-general@postgreSQL.org
Subject: Re: With what options RPM was compiled? ( Was: Czech Win1250 sorting
q)
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
<m2wvqjpg4n.fsf@chameleon.localdomain>
<3855477C.11EF5AAF@robert.cz> <38554BE5.66A09278@wgcr.org>
<385668FC.298231E6@robert.cz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert wrote:

Thanks for everybody's help, I got it working now. An observation:
The steps Lamar described really created a binary RPM, however
the pg_encoding utility isn't included (it was built though).

Can be added to the %files list easily enough. Will be included in next
release.

Similarly
'createdb -E LATIN2 xx' from README.mb doesn't work, while
create database with encoding = 'latin2' works OK.

Hmmm... Reading the createdb script shows that the pg_encoding utility
is used by createdb.... Hopefully will be fixed next release.

PS If anybody's is in urgent need, I can put those rpms online before
Lamar builts the new version with multibyte support enabled - just let
me know you're interested.

I can rebuild overnight tonight, if need be. I have a few other items
on the rebuild plate anyway. Prep for the release of 6.5.3-3.....coming
soon to an ftp server near you.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Tue Dec 14 11:57:39 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA01831
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:56:38 -0500 (EST)
(envelope-from rdavis@lillysoftware.com)
Received: from [12.6.225.3] ([12.6.225.3])
by trends.net (8.8.8/8.8.8) with SMTP id LAA19628
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:36:06 -0500 (EST)
Received: from lillysoftware.com by [12.6.225.3]
via smtpd (for clio.trends.ca [209.47.148.2]) with SMTP;
14 Dec 1999 16:35:51 UT
Received: from lillysoftware.com (BOBIBM333 [173.100.2.237]) by
ponyexpress.LillySoftware.com with SMTP (Microsoft Exchange
Internet Mail Service Version 5.5.2448.0)
id YR9L5QFN; Tue, 14 Dec 1999 11:31:15 -0500
Message-ID: <38567165.B04C532C@lillysoftware.com>
Date: Tue, 14 Dec 1999 11:33:41 -0500
From: Robert Davis <rdavis@lillysoftware.com>
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ^chewie <chewie@wookimus.net>
CC: Manuel Lemos <mlemos@acm.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Can't I create indexes on BOOL columns?
References: <Pine.LNX.4.10.9912131216180.1964-100000@geeks.linux.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi I have a similar problem. I cant create indexes on decimal columns.

CREATE TABLE REQUIREMENT_COST(
WORKORDER_TYPE CHAR(1) NOT NULL,
WORKORDER_BASE_ID VARCHAR(30) NOT NULL,
WORKORDER_LOT_ID VARCHAR(3) NOT NULL,
WORKORDER_SPLIT_ID VARCHAR(3) NOT NULL,
WORKORDER_SUB_ID VARCHAR(3) NOT NULL,
OPERATION_SEQ_NO SMALLINT NOT NULL,
REQ_PIECE_NO SMALLINT NOT NULL,
QTY DECIMAL(14,4) NOT NULL,
UNIT_COST DECIMAL(14,4) NOT NULL,
FIXED_COST DECIMAL(15,2) NOT NULL,
MINIMUM_COST DECIMAL(15,2),
PRIMARY KEY(WORKORDER_TYPE,WORKORDER_BASE_ID,WORKORDER_LOT_ID,WORKORDER_SPLIT_ID,WORKORDER_SUB_ID,OPERATION_SEQ_NO,REQ_PIECE_NO,QTY
))
;
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'requirement_cost_pkey' for table 'requirement_cost'
ERROR: Can't find a default operator class for type 1700.

If the field qty is deleted from the above primary key the create works.
I assume that there is an operator I can add to fix this?

bob

^chewie wrote:

On 13 Dec 1999, Manuel Lemos wrote:

Hello,

I am using PostgreSQL 6.4.2. and it seems I can't create indexes on
BOOL columns. I tried this:

...snip...

However, if I change the BOOL type to CHAR (1) it works.

I'm not a developer, so I don't know if it's a bug or a logic error
you're pointing out, or even if it's an error at all. However, I could
rationalize that it is not an error on the premise that BOOLEAN
identifiers can only have two values: true or false.

Obviously, you cannot use a UNIQUE index on such an column. A Clustered
index would not do much better, logically, since you're only splitting
up the data into two groups. Therefore, what is the point of indexing
on boolean columns, really? I suppose it would depend upon the data in
the table. If you see one value predominantly over the other, splitting
out the smaller group via the index *may* help your search. However, if
the values are fairly even in proportion, you won't gain much.

I'd say stick with your work-around, and post the question to the devel
team.

----------------------------------------------------------------
Chad Walstrom mailto:chewie@wookimus.net
a.k.a ^chewie, gunnarr http://wookimus.net/~chewie

Gnupg = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
----------------------------------------------------------------

************

--
rdavis@lillysoftware.com
rsdavis@mediaone.net
http://people.ne.mediaone.net/rsdavis

From bouncefilter Tue Dec 14 11:56:56 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA01820
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:56:34 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by trends.net (8.8.8/8.8.8) with ESMTP id LAA19778
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:38:12 -0500 (EST)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
LAA14903;
Tue, 14 Dec 1999 11:34:40 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912141634.LAA14903@candle.pha.pa.us>
Subject: Re: [GENERAL] pg_psort files
In-Reply-To: <19991214100555.C771@jasper.southwind.net> from Steven Saner at
"Dec 14, 1999 10:05:55 am"
To: Steven Saner <ssaner@southwind.net>
Date: Tue, 14 Dec 1999 11:34:40 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have a fairly simple database (two tables and a few indecies). In
the data/base/xxxx directory I find the following files:

-rw------- 1 postgres postgres 7734146 Dec 14 06:36 pg_psort.13268.0
-rw------- 1 postgres postgres 7707487 Dec 14 06:36 pg_psort.13268.1
-rw------- 1 postgres postgres 7776602 Dec 14 06:36 pg_psort.13268.2
-rw------- 1 postgres postgres 936026112 Dec 14 07:20 pg_psort.13268.3
-rw------- 1 postgres postgres 8208384 Dec 14 06:36 pg_psort.13268.4
-rw------- 1 postgres postgres 15699116 Dec 14 06:36 pg_psort.13268.5
-rw------- 1 postgres postgres 19002244 Dec 14 06:36 pg_psort.13268.6
-rw------- 1 postgres postgres 2097152 Dec 9 06:33 pg_psort.25350.0
-rw------- 1 postgres postgres 2146304 Dec 9 06:33 pg_psort.25350.1
-rw------- 1 postgres postgres 2277376 Dec 9 06:33 pg_psort.25350.2
-rw------- 1 postgres postgres 1597440 Dec 9 06:33 pg_psort.25350.3
-rw------- 1 postgres postgres 1064960 Dec 9 06:33 pg_psort.25350.4
-rw------- 1 postgres postgres 1327104 Dec 9 06:33 pg_psort.25350.5
-rw------- 1 postgres postgres 0 Dec 9 06:32 pg_psort.25350.6

I have another database that is almost identical on a different
machine. There are no pg_psort.xxxx files there. I am wondering:

1. What are these files?
2. Do I need them?
3. If I don't need them is it safe to remove them?

Stop postmaster, remove files, restart postmaster. They aren't needed.

I am surprised they are not automatically cleaned up. What version are
you using?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Dec 14 11:50:48 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA00910
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:50:42 -0500 (EST)
(envelope-from gerald@mauz.interface-business.de)
Received: from innocence.interface-business.de
(innocence.interface-business.de [193.101.57.202])
by trends.net (8.8.8/8.8.8) with ESMTP id LAA20263
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:44:42 -0500 (EST)
Received: from mauz.interface-business.de (mauz.interface-business.de
[193.101.57.233])
by innocence.interface-business.de with ESMTP id RAA84371;
Tue, 14 Dec 1999 17:42:12 +0100 (CET)
Received: (from gerald@localhost)
by mauz.interface-business.de (8.8.8/8.8.8) id RAA23662;
Tue, 14 Dec 1999 17:42:11 +0100 (CET) (envelope-from gerald)
Message-ID: <XFMail.991214174211.gerald@interface-business.de>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3.0.3.32.19991214111457.010f8fac@popd.ix.netcom.com>
Date: Tue, 14 Dec 1999 17:42:11 +0100 (CET)
Reply-To: gerald@interface-business.de
Organization: Interface Business
Sender: gerald@mauz.interface-business.de
From: Gerald Fiedler <gerald@interface-business.de>
To: Samy Elashmawy <samelash@ix.netcom.com>
Subject: Re: [GENERAL] Announce: Postgres Access Control Tool
Cc: pgsql-general@postgreSQL.org

Hi Samy,

What is paco ??

At 04:22 PM 12/14/1999 +0100, postgres@taifun.interface-business.de wrote:

Hi all,

a new version of PACO is available at ftp://ftp.sftech.de/pub/paco/

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

Cheers...

From bouncefilter Tue Dec 14 11:50:49 1999
Received: from trends.net (root@clio.trends.ca [209.47.148.2])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA00906
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 11:50:41 -0500 (EST)
(envelope-from Rosa.Carro@ii.uam.es)
From: Rosa.Carro@ii.uam.es
Received: from arantxa.ii.uam.es (arantxa.ii.uam.es [150.244.56.15])
by trends.net (8.8.8/8.8.8) with ESMTP id LAA20672
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 11:50:16 -0500 (EST)
Received: from minerva.ii.uam.es (minerva [150.244.56.39])
by arantxa.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id RAA20103;
Tue, 14 Dec 1999 17:50:18 GMT
Received: from helena (helena [150.244.56.48])
by minerva.ii.uam.es (8.8.8+Sun/8.8.8) with ESMTP id RAA02032;
Tue, 14 Dec 1999 17:43:14 +0100 (MET)
Message-ID: <3856765C.3C1BF30B@ii.uam.es>
Date: Tue, 14 Dec 1999 17:54:52 +0100
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
To: pgsql-general@postgresql.org, pgsql-novice@hub.org
Subject: Embedded SQL (II)
X-Priority: 3 (Normal)
References: <384D0350.4EBE1283@ii.uam.es>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello, colleages,

I have run a C program with embedded SQL, but the changes (insert sentences) don't keep data in the
database. When I connect to the database by writting "psql database" and I do the selects, nothing
appears.

If I write the same SQL sentences in psql, the changes keep done.
I wasn't using transactions, but now I have included them, although the same thing happens again.

Any idea about this?
The code is:

EXEC SQL BEGIN DECLARE SECTION;
...
...
EXEC SQL END DECLARE SECTION;

EXEC SQL CONNECT TO db USER username;

EXEC SQL BEGIN TRANSACTION;

EXEC SQL INSERT INTO table (...) VALUES (...);
EXEC SQL INSERT INTO table (...) VALUES (...);
EXEC SQL INSERT INTO table (...) VALUES (...);
...
EXEC SQL COMMIT TRANSACTION;

EXEC SQL DISCONNECT;

------------------------------------------
Rosa Maria Carro Salas
E.T.S.Informatica
Universidad Autonoma de Madrid
Cantoblanco 28049, Madrid (Spain)
phone: +34 1 348 2291

From bouncefilter Tue Dec 14 11:56:53 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA01809
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 11:56:23 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id MAA14064;
Tue, 14 Dec 1999 12:55:55 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 14 Dec 1999 12:55:46 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Steven Saner <ssaner@southwind.net>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] pg_psort files
In-Reply-To: <19991214100555.C771@jasper.southwind.net>
Message-ID: <Pine.BSF.4.21.9912141253580.34471-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 14 Dec 1999, Steven Saner wrote:

I have a fairly simple database (two tables and a few indecies). In
the data/base/xxxx directory I find the following files:

-rw------- 1 postgres postgres 7734146 Dec 14 06:36 pg_psort.13268.0
-rw------- 1 postgres postgres 7707487 Dec 14 06:36 pg_psort.13268.1
-rw------- 1 postgres postgres 7776602 Dec 14 06:36 pg_psort.13268.2
-rw------- 1 postgres postgres 936026112 Dec 14 07:20 pg_psort.13268.3
-rw------- 1 postgres postgres 8208384 Dec 14 06:36 pg_psort.13268.4
-rw------- 1 postgres postgres 15699116 Dec 14 06:36 pg_psort.13268.5
-rw------- 1 postgres postgres 19002244 Dec 14 06:36 pg_psort.13268.6
-rw------- 1 postgres postgres 2097152 Dec 9 06:33 pg_psort.25350.0
-rw------- 1 postgres postgres 2146304 Dec 9 06:33 pg_psort.25350.1
-rw------- 1 postgres postgres 2277376 Dec 9 06:33 pg_psort.25350.2
-rw------- 1 postgres postgres 1597440 Dec 9 06:33 pg_psort.25350.3
-rw------- 1 postgres postgres 1064960 Dec 9 06:33 pg_psort.25350.4
-rw------- 1 postgres postgres 1327104 Dec 9 06:33 pg_psort.25350.5
-rw------- 1 postgres postgres 0 Dec 9 06:32 pg_psort.25350.6

I have another database that is almost identical on a different
machine. There are no pg_psort.xxxx files there. I am wondering:

1. What are these files?

sort files for stuff like ORDER BY queries...

2. Do I need them?

as long as you aren't running a query, you can safely remove them...

3. If I don't need them is it safe to remove them?

yes...

Also, what version of PostgreSQL are you running? I swore that more
recent versions of PostgreSQL cleaned up better behind itself...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Tue Dec 14 12:14:39 1999
Received: from mail.netic.de (mail.s.netic.de [212.9.160.11])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA10722
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 12:13:40 -0500 (EST)
(envelope-from eschmid@s.netic.de)
Received: by mail.netic.de (Smail3.2.0.106/mail.s.netic.de)
via LF.net GmbH Internet Services via remoteip 194.97.245.21
via remotehost s.netic.de with esmtp for postgresql.org
id m11xvNu-001X0BC; Tue, 14 Dec 1999 18:05:10 +0100 (CET)
Sender: egon
Message-ID: <38567AAC.39C71F04@s.netic.de>
Date: Tue, 14 Dec 1999 18:13:16 +0100
From: Egon Schmid <eschmid@s.netic.de>
Organization: Six Offene Systeme GmbH
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9-2 i686)
X-Accept-Language: de-DE, en
MIME-Version: 1.0
To: Samy Elashmawy <samelash@ix.netcom.com>
CC: gerald@interface-business.de, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Announce: Postgres Access Control Tool
References: <3.0.3.32.19991214111457.010f8fac@popd.ix.netcom.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Samy Elashmawy wrote:

What is paco ??

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

At 04:22 PM 12/14/1999 +0100, postgres@taifun.interface-business.de wrote:

Hi all,

a new version of PACO is available at ftp://ftp.sftech.de/pub/paco/

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

-Egon

--
Six Offene Systeme GmbH � Sielminger Stra�e 63 � D-70771 L.-Echterdingen
Fon +49 711 9 90 91 64 � http://www.six.de/
Fax +49 711 9 90 91 99 � mailto:egon@six.de

From bouncefilter Tue Dec 14 12:56:40 1999
Received: from rage.hub.org (root@nat202.25.mpoweredpc.net [142.177.202.25])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA21337
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 12:56:31 -0500 (EST) (envelope-from jeff@hub.org)
Received: from localhost (jeff@localhost)
by rage.hub.org (8.9.3/8.9.3) with ESMTP id NAA20458
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 13:56:31 -0400 (AST) (envelope-from jeff@hub.org)
X-Authentication-Warning: rage.hub.org: jeff owned process doing -bs
Date: Tue, 14 Dec 1999 13:56:29 -0400 (AST)
From: Jeff MacDonald <jeff@hub.org>
Reply-To: Jeff MacDonald <jeff@hub.org>
To: pgsql-general@postgresql.org
Subject: Mailing Lists
Message-ID: <Pine.BSF.4.10.9912141236180.16188-100000@rage.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hey folks,

I'm working on the CD image for PostgreSQL again. It's now at
quite a healty size of 664 megs, and grows daily as the mailing
list archives grow.

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

Depending on the consensus, we will either remove the archives from
the cd distro all together, or find an alternate method of storing
them on it.

I'm also taking any suggestions to make the archives on the cd searchable.

Thanks

Jeff MacDonald
jeff@hub.org

From bouncefilter Tue Dec 14 12:58:40 1999
Received: from jasper.southwind.net (ssaner@jasper.southwind.net
[206.53.103.7]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA21524
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 12:58:29 -0500 (EST)
(envelope-from ssaner@jasper.southwind.net)
Received: (from ssaner@localhost)
by jasper.southwind.net (8.9.3/8.9.3) id LAA14816
for pgsql-general@postgreSQL.org; Tue, 14 Dec 1999 11:58:09 -0600 (CST)
Date: Tue, 14 Dec 1999 11:58:09 -0600
From: Steven Saner <ssaner@southwind.net>
To: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] pg_psort files
Message-ID: <19991214115808.D771@jasper.southwind.net>
References: <19991214100555.C771@jasper.southwind.net>
<199912141634.LAA14903@candle.pha.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.15i
In-Reply-To: <199912141634.LAA14903@candle.pha.pa.us>;
from Bruce Momjian on Tue, Dec 14, 1999 at 11:34:40AM -0500

I'm running 6.5.1. We've had a bit of trouble with the machine
crashing that this database is on (I don't think it is because of
postgres) so my guess is that it was unable to clean up after itself
sometimes. Today, the filesystem where postgres lives on filled up,
that may be why as well. Thanks for the response.

On Tue, Dec 14, 1999 at 11:34:40AM -0500, Bruce Momjian wrote:

1. What are these files?
2. Do I need them?
3. If I don't need them is it safe to remove them?

Stop postmaster, remove files, restart postmaster. They aren't needed.

I am surprised they are not automatically cleaned up. What version are
you using?
-- 
Bruce Momjian                        |  http://www.op.net/~candle
maillist@candle.pha.pa.us            |  (610) 853-3000
+  If your life is a hard drive,     |  830 Blythe Avenue
+  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Tue Dec 14 13:07:40 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA25010
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 13:06:52 -0500 (EST)
(envelope-from lamar.owen@wgcr.org)
Received: from wgcr.org ([206.74.232.197])
by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id NAA28834;
Tue, 14 Dec 1999 13:06:32 -0500
Message-ID: <38568722.3C50BACA@wgcr.org>
Date: Tue, 14 Dec 1999 13:06:26 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: WGCR Internet Radio
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: Robert <robert@robert.cz>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was:
CzechWin1250 sorting q)
References: <Pine.LNX.4.20.9912132245300.361-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Eisentraut wrote:

On 1999-12-13, Lamar Owen mentioned:

The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
with --with-mb=LATIN2.

Perhaps the next set of RPMs could be compiled with --enable-locale and
--with-mb=SQL_ASCII. At least do it like now: the non-locale/non-multibyte
version for performance, and the locale/mb version for features. Please
note that SQL_ASCII doesn't mean that the db cannot support any other
encoding, it's just the default encoding initdb uses.

With version 6.5.3, setting --with-mb=SQL_ASCII throws a configure
error. It then lists the valid encodings, which do not include
SQL_ASCII.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

From bouncefilter Wed Dec 15 14:23:40 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id OAA80313
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 14:23:19 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id 743541F75; Tue, 14 Dec 1999 18:09:14 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id 5B0121F79
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 18:09:14 +0000 (GMT)
Date: Tue, 14 Dec 1999 18:09:14 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: indices don't make much difference
In-Reply-To: <Pine.BSF.4.10.9912091610320.8952-100000@server.b0x.com>
Message-ID: <Pine.BSF.4.10.9912141756480.1350-200000@server.b0x.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-513781138-945194954=:1350"

This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.

--0-513781138-945194954=:1350
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am trying to optimise a query which looks like:
select prod_base.*, manu_base.name from prod_base, manu_base where
prod_base.mid=manu_base.mid;

manu_base is a table consisting of 3000 manufacturer with an id (not
unique to support synonyms) and a name (declared as varchar(32)).
prod_base is a table of products which each refer to the manufacturer id
(mid).

I have tried creating an index for manu_base using the following commands:
create index manu_mid_idx on "manu_base" using btree ("mid" "int2_ops");
drop index manu_mid_idx
create index manu_mid_idx on "manu_base" using hash ("mid" "int2_ops");
drop index manu_mid_idx

I have then run benchmarks without index, with btree and with hash, but
none seem to be faster than the other. My benchmark program is written in
c and is attached to this email. Here are the results I obtained using
time:

without index:
17.25 real 1.42 user 0.26 sys
with btree:
17.28 real 1.38 user 0.30 sys
with hash:
17.22 real 1.37 user 0.32 sys

If there is any way to make a query quicker when joining a product table
and a manufacturer table, please let me know. I've tried everything and
the results are quite fast enough.

Thanks,
Marc

--0-513781138-945194954=:1350
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="bench.c"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.BSF.4.10.9912141809140.1350@server.b0x.com>
Content-Description: pgsql benchmark
Content-Disposition: attachment; filename="bench.c"

I2luY2x1ZGUgPHN0ZGlvLmg+DQojaW5jbHVkZSA8c3RkbGliLmg+DQojaW5j
bHVkZSA8dW5pc3RkLmg+DQojaW5jbHVkZSAibGlicHEtZmUuaCINCg0Kc3Rh
dGljIHZvaWQgZXhpdF9uaWNlbHkoUEdjb25uICpjb25uKSB7DQogICAgUFFm
aW5pc2goY29ubik7DQogICAgZXhpdCgxKTsNCn0NCg0KaW50IG1haW4oKSB7
DQogICAgaW50IGksIGo7DQogICAgY2hhciAqZGJOYW1lID0gInd0Ynd0cyI7
DQoNCiAgICBQR2Nvbm4gKmNvbm47DQogICAgUEdyZXN1bHQgKnJlczsNCg0K
ICAgIGNvbm4gPSBQUXNldGRiKE5VTEwsIE5VTEwsIE5VTEwsIE5VTEwsIGRi
TmFtZSk7DQoNCiAgICBpZiAoUFFzdGF0dXMoY29ubikgPT0gQ09OTkVDVElP
Tl9CQUQpIHsNCiAgICAgICAgZnByaW50ZihzdGRlcnIsICJDb25uZWN0aW9u
IHRvIGRhdGFiYXNlICclcycgZmFpbGVkLlxuIiwgZGJOYW1lKTsNCiAgICAg
ICAgZnByaW50ZihzdGRlcnIsICIlcyIsIFBRZXJyb3JNZXNzYWdlKGNvbm4p
KTsNCiAgICAgICAgZXhpdF9uaWNlbHkoY29ubik7DQogICAgfQ0KDQogICAg
Zm9yIChpPTA7IGk8NTA7IGkrKykgew0KICAgICAgICByZXMgPSBQUWV4ZWMo
Y29ubiwgIlNFTEVDVCBwcm9kX2Jhc2UuKiwgbWFudV9iYXNlLm5hbWUgRlJP
TSBwcm9kX2Jhc2UsIG1hbnVfYmFzZSB3aGVyZSBwcm9kX2Jhc2UubWlkID0g
bWFudV9iYXNlLm1pZCIpOw0KICAgICAgICBpZiAoIXJlcyB8fCBQUXJlc3Vs
dFN0YXR1cyhyZXMpICE9IFBHUkVTX1RVUExFU19PSykgew0KICAgICAgICAg
ICAgZnByaW50ZihzdGRlcnIsICJTRUxFQ1QgZmFpbGVkXG4iKTsNCiAgICAg
ICAgICAgIFBRY2xlYXIocmVzKTsNCiAgICAgICAgICAgIGV4aXRfbmljZWx5
KGNvbm4pOw0KICAgICAgICB9DQogICAgICAgIGZvciAoaj0wOyBqPFBRbnR1
cGxlcyhyZXMpOyBqKyspIHsNCiAgICAgICAgICAgIFBRZ2V0dmFsdWUocmVz
LCBqLCAwKTsNCiAgICAgICAgfQ0KICAgICAgICBQUWNsZWFyKHJlcyk7DQog
ICAgfQ0KICAgIFBRZmluaXNoKGNvbm4pOw0KICAgIHJldHVybiAwOw0KfQ0K

--0-513781138-945194954=:1350--

From bouncefilter Tue Dec 14 13:31:40 1999
Received: from picasso.realtyideas.com (IDENT:kaiq@207-18-128-210.flex.net
[207.18.128.210]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA31050
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 13:30:53 -0500 (EST)
(envelope-from kaiq@picasso.realtyideas.com)
Received: from localhost (kaiq@localhost)
by picasso.realtyideas.com (8.9.3/8.9.3) with ESMTP id MAA23928;
Tue, 14 Dec 1999 12:30:26 -0600
Date: Tue, 14 Dec 1999 12:30:26 -0600 (CST)
From: <kaiq@realtyideas.com>
To: Jeff MacDonald <jeff@hub.org>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Mailing Lists
In-Reply-To: <Pine.BSF.4.10.9912141236180.16188-100000@rage.hub.org>
Message-ID: <Pine.LNX.4.10.9912141218050.22674-100000@picasso.realtyideas.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I said this before, hope not too annoying.
Is it possible to make the mailing lists downloadable text
files? of course, they need to be splited into several files
for each list. Seems that the time of each version-release is
a reasonable cut. most people will only need the more recent
ones.

The use of online search engine is slower than 'primitive'
vi -- not only because of the search engine itself but also
due to the web server and network.

Is there any commercial interest that conflict with this?

On Tue, 14 Dec 1999, Jeff MacDonald wrote:

Hey folks,

I'm working on the CD image for PostgreSQL again. It's now at
quite a healty size of 664 megs, and grows daily as the mailing
list archives grow.

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

Depending on the consensus, we will either remove the archives from
the cd distro all together, or find an alternate method of storing
them on it.

I'm also taking any suggestions to make the archives on the cd searchable.

Thanks

Jeff MacDonald
jeff@hub.org

===================================================================
So long as the Universe had a beginning, we can suppose it had a
creator, but if the Universe is completly self contained , having
no boundry or edge, it would neither be created nor destroyed
It would simply be.
===================================================================

************

From bouncefilter Tue Dec 14 13:48:40 1999
Received: from rage.hub.org (root@nat202.25.mpoweredpc.net [142.177.202.25])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA40761
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 13:47:53 -0500 (EST) (envelope-from jeff@hub.org)
Received: from localhost (jeff@localhost)
by rage.hub.org (8.9.3/8.9.3) with ESMTP id OAA20570;
Tue, 14 Dec 1999 14:47:34 -0400 (AST) (envelope-from jeff@hub.org)
X-Authentication-Warning: rage.hub.org: jeff owned process doing -bs
Date: Tue, 14 Dec 1999 14:47:33 -0400 (AST)
From: Jeff MacDonald <jeff@hub.org>
Reply-To: Jeff MacDonald <jeff@hub.org>
To: kaiq@realtyideas.com
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Mailing Lists
In-Reply-To:
<Pine.LNX.4.10.9912141218050.22674-100000@picasso.realtyideas.com>
Message-ID: <Pine.BSF.4.10.9912141446190.16188-100000@rage.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I said this before, hope not too annoying.
Is it possible to make the mailing lists downloadable text
files? of course, they need to be splited into several files

i could do this, with just the plain text files, not the html/
mhonarc stuff. i have no issues with this.

a reasonable cut. most people will only need the more recent
ones.

negative, we want all or nothing. past archives are very useful.
that's why their archived :)

Is there any commercial interest that conflict with this?

none at all, i'm open to any and all suggestions.

On Tue, 14 Dec 1999, Jeff MacDonald wrote:

Hey folks,

I'm working on the CD image for PostgreSQL again. It's now at
quite a healty size of 664 megs, and grows daily as the mailing
list archives grow.

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

Depending on the consensus, we will either remove the archives from
the cd distro all together, or find an alternate method of storing
them on it.

I'm also taking any suggestions to make the archives on the cd searchable.

Thanks

Jeff MacDonald
jeff@hub.org

===================================================================
So long as the Universe had a beginning, we can suppose it had a
creator, but if the Universe is completly self contained , having
no boundry or edge, it would neither be created nor destroyed
It would simply be.
===================================================================

************

Jeff MacDonald
jeff@hub.org

From bouncefilter Tue Dec 14 13:59:40 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA42380
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 13:59:36 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id OAA22518;
Tue, 14 Dec 1999 14:59:23 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 14 Dec 1999 14:59:22 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: kaiq@realtyideas.com
cc: Jeff MacDonald <jeff@hub.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Mailing Lists
In-Reply-To:
<Pine.LNX.4.10.9912141218050.22674-100000@picasso.realtyideas.com>
Message-ID: <Pine.BSF.4.21.9912141456320.34471-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 14 Dec 1999 kaiq@realtyideas.com wrote:

I said this before, hope not too annoying.
Is it possible to make the mailing lists downloadable text
files? of course, they need to be splited into several files
for each list. Seems that the time of each version-release is
a reasonable cut. most people will only need the more recent
ones.

The use of online search engine is slower than 'primitive'
vi -- not only because of the search engine itself but also
due to the web server and network.

Is there any commercial interest that conflict with this?

Ummm, there is a link off of each month on the web site to an mbox format
file, gzip'd...unfortunately, just looking at it now, it looks like there
is a bug with the script that generates that page...will look at it...

But, those links have been generated since we put up mhonarc many months
ago...

On Tue, 14 Dec 1999, Jeff MacDonald wrote:

Hey folks,

I'm working on the CD image for PostgreSQL again. It's now at
quite a healty size of 664 megs, and grows daily as the mailing
list archives grow.

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

Depending on the consensus, we will either remove the archives from
the cd distro all together, or find an alternate method of storing
them on it.

I'm also taking any suggestions to make the archives on the cd searchable.

Thanks

Jeff MacDonald
jeff@hub.org

===================================================================
So long as the Universe had a beginning, we can suppose it had a
creator, but if the Universe is completly self contained , having
no boundry or edge, it would neither be created nor destroyed
It would simply be.
===================================================================

************

************

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Tue Dec 14 14:12:40 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA47049
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 14:11:47 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.43.244]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 14 Dec 1999 13:11:43 -0600
Sender: ed
Message-ID: <38569691.94FE7924@austin.rr.com>
Date: Tue, 14 Dec 1999 13:12:17 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
CC: pgsql-general@postgresql.org
Subject: [GENERAL] How to verify integrity of pg DB?
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

In the event of a hardware failure or some other problem potentially
corrupting a postgres database, how does one verify the integrity of the
database with certainty before resuming operations?

From bouncefilter Tue Dec 14 14:28:41 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA49471
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 14:27:50 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61317 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sJdcM28740>; Tue, 14 Dec 1999 20:27:20 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11xxgp-0001Fi-00; Tue, 14 Dec 1999 20:32:51 +0100
Date: Tue, 14 Dec 1999 20:32:51 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Lamar Owen <lamar.owen@wgcr.org>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was:
CzechWin1250 sorting q)
In-Reply-To: <38568722.3C50BACA@wgcr.org>
Message-ID: <Pine.LNX.4.20.9912142031280.388-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-14, Lamar Owen mentioned:

With version 6.5.3, setting --with-mb=SQL_ASCII throws a configure
error. It then lists the valid encodings, which do not include
SQL_ASCII.

Thank you very much. This was one of the reasons I wanted this changed to
--enable-mb, but some people really wanted that default encoding
there. Complain to them. :) That will be fixed for the next release.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Dec 14 16:04:25 1999
Received: from web1402.mail.yahoo.com (web1402.mail.yahoo.com [128.11.23.166])
by hub.org (8.9.3/8.9.3) with SMTP id QAA73010
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 16:04:12 -0500 (EST)
(envelope-from charlesdotcom@yahoo.com)
Received: (qmail 19627 invoked by uid 60001); 14 Dec 1999 20:13:49 -0000
Message-ID: <19991214201349.19626.qmail@web1402.mail.yahoo.com>
Received: from [63.195.80.23] by web1402.mail.yahoo.com;
Tue, 14 Dec 1999 12:13:49 PST
Date: Tue, 14 Dec 1999 12:13:49 -0800 (PST)
From: Charles Martin <charlesdotcom@yahoo.com>
Subject: recurring problems requiring a vacuum
To: pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Our web/db application is to the state where we are using it to load in a lot
of content. The system seems to run fine for a while, and then bogs down with
postgres processes chewing up lots of CPU time and nothing happening.

When this happens I vacuum the database, and it seems to fix the problem. The
trouble is, it keeps recurring. This last time I vacuumed, I got the following
message (among others):

NOTICE: Rel pg_proc: TID 8/12: OID IS INVALID. TUPGONE 0.

This message keeps recurring, so I assume it is just continuing to warn me that
some tuple is gone. (From some internal table?)

My question is, why does the db keep grinding to a halt and requiring vacuums
in this way? The db structure is faily straightforward; each table is of the
form:

create table foo (foo_id serial primary key, ...);

and I have not created any indices other than these. There is not a lot of
content in the database; ie, things are still fairly small.

I am running Postgres 6.5.2 on FreeBSD 3.3-STABLE.
The web application uses PHP 3.0.12 on Apache 1.3.9.

Any hints or pointers appreciated. Thank you!

Charles

__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

From bouncefilter Tue Dec 14 16:29:25 1999
Received: from mail.pbpower.co.nz (mail.designpower.co.nz [203.97.56.178])
by hub.org (8.9.3/8.9.3) with ESMTP id QAA75425
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 16:28:40 -0500 (EST)
(envelope-from DerricuttM@pbworld.com)
Received: by mail.pbpower.co.nz with Internet Mail Service (5.5.2650.21)
id <Y508AXHW>; Wed, 15 Dec 1999 10:30:41 +1300
Message-ID: <93314B6256A5D211BE8B006097B95027179164@NZAM>
From: "Derricutt, Mark" <DerricuttM@pbworld.com>
To: "'gerald@interface-business.de'" <gerald@interface-business.de>,
pgsql-general@postgreSQL.org
Subject: RE: [GENERAL] Announce: Postgres Access Control Tool
Date: Wed, 15 Dec 1999 10:29:36 +1300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
charset="iso-8859-1"

PACO is a graphical remote administration tool for Postgres
written in Tcl/Tk. It allows database administrators to easily
administrate users, groups and hosts access to databases.

Is there anyway I can get this run under Tcl/Tk on Windows NT? I tried
simply loading ./paco into wish but it failed looking up /usr/....
references.

Mark

From bouncefilter Tue Dec 14 18:03:26 1999
Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net
[207.217.121.49]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA96838
for <pgsql-general@hub.org>; Tue, 14 Dec 1999 18:03:25 -0500 (EST)
(envelope-from dshenk@bigfoot.com)
Received: from [209.246.93.113] (dialup-209.246.72.67.NewYork2.Level3.net
[209.246.72.67])
by scaup.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA06875
for <pgsql-general@hub.org>; Tue, 14 Dec 1999 15:03:23 -0800 (PST)
X-Sender: davidshenk@mail.earthlink.net
Message-Id: <v03110756b47c7afb636d@[209.246.93.113]>
In-Reply-To: <199912120402.XAA65971@hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 14 Dec 1999 17:53:49 -0500
To: pgsql-general@hub.org
From: David Shenk <dshenk@bigfoot.com>
Subject: Re: pgsql-general-digest V1 #564

Because of a temporary glitch in domain hosting, emails sent to the kind.com over the last few days did not go through. Please resend your mail.

Thank you. Sorry for the inconvenience.

(Please do not reply to this email).

___________
David Shenk
http://www.bigfoot.com/~dshenk
718/783-2835

From bouncefilter Tue Dec 14 17:57:27 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA92948
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 17:56:49 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:63877 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sJggY153670>; Tue, 14 Dec 1999 23:56:36 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11y0xK-0001PX-00; Wed, 15 Dec 1999 00:02:06 +0100
Date: Wed, 15 Dec 1999 00:02:06 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Elmar.Haneke@gmx.de
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Access rescrictions
In-Reply-To: <A97E85E30@haneke.de>
Message-ID: <Pine.LNX.4.20.9912142358520.5253-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-14, Elmar.Haneke@gmx.de mentioned:

I'm looking for an solution to restrict the access to show an part of an Table only:
In an customer-database it should be possible to list the bills of an certain customer,
but it should be restricted to generate/summarize a list of all bills.

"SELECT * FROM Bills" should be restricted
"SELECT * FROM Bills WHERE CustomerID=?" should be allowed for any CustomerID.

Is there an solution to this problem in PostgreSQL?

No. I think hardly any database engine will be able to restrict access
according to query semantics. You will have to do this via your client
application.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Tue Dec 14 19:57:27 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA19733
for <pgsql-general@postgresql.org>;
Tue, 14 Dec 1999 19:56:35 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.43.244]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 14 Dec 1999 18:56:53 -0600
Sender: ed
Message-ID: <3856E77C.1ECAA152@austin.rr.com>
Date: Tue, 14 Dec 1999 18:57:32 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff MacDonald <jeff@hub.org>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Mailing Lists
References: <Pine.BSF.4.10.9912141236180.16188-100000@rage.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jeff MacDonald wrote:

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

CD archives would seem replaceable to me if the www.postgresql.org search
engine were a bit more reliable and useful (ie easier to navigate threads
found via search.

Cheers.
Ed Loehr

From bouncefilter Tue Dec 14 20:57:28 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA31719
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 20:57:24 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id VAA69349;
Tue, 14 Dec 1999 21:57:34 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 14 Dec 1999 21:57:33 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Ed Loehr <ELOEHR@austin.rr.com>
cc: Jeff MacDonald <jeff@hub.org>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Mailing Lists
In-Reply-To: <3856E77C.1ECAA152@austin.rr.com>
Message-ID: <Pine.BSF.4.21.9912142156440.57039-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 14 Dec 1999, Ed Loehr wrote:

Jeff MacDonald wrote:

The lists are taking up >50% of the cd. I'm curious about people's
opinions. The archives are a valuable resource. But out of those
who have ever bought a cd, or those that would,

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

CD archives would seem replaceable to me if the www.postgresql.org search
engine were a bit more reliable and useful (ie easier to navigate threads
found via search.

Okay, I'm confused...when ht/dig worked, if you clicked on a mesage you
wanted to read, that message had a 'thread' link that would list all
messages in that thread...

...or are you talking about something different?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Tue Dec 14 23:27:30 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA59931
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 23:27:25 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-182-138.bng.vsnl.net.in [203.197.182.138])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id JAA31482;
Wed, 15 Dec 1999 09:58:22 +0500 (GMT+0500)
Message-ID: <000101bf46b4$967b8c00$8ab6c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <pgsql-general@postgreSQL.org>
Cc: "Kimi" <kimi@intercept.co.in>
Subject: Postgres instability : AN APPEAL
Date: Wed, 15 Dec 1999 09:21:52 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

I have unfortunately programmed a mission critical application in postgres
without doing full load testing.
Now I'm getting lots of messages when I start stressing it.
Typical messages include --- Spinlock error, ReleaseLRU no files found etc.,
Last couple of days I'm battling by switching on the pgoptions. They don't
seem to help... because I can't correlate which message is coming from which
process or session or SQL.
I have posted a detailed message on this error last week. Nobody responded.

THIS IS AN APPEAL. If any of you has experience in handling postgres locking
and instabilities.... CAN YOU PLEASE WRITE TO ME. I'm desperate to talk to
somebody who can understand my problems and give me some intelligent
suggestions.

Thanks in Advance,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

From bouncefilter Tue Dec 14 23:27:32 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA59932
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 23:27:27 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-182-138.bng.vsnl.net.in [203.197.182.138])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id JAA14554
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 09:58:25 +0500 (GMT+0500)
Message-ID: <000201bf46b4$97a9abc0$8ab6c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <pgsql-general@postgreSQL.org>
Subject: Postgres restart problems
Date: Wed, 15 Dec 1999 09:26:02 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

We have a postgres db which has been crashing about 5 times a day. It must
be failrly apparent given my other messages to this mailing list.

Now we are faced with a new problem. After crash we were able to restart
postmaster. Now postgres is getting more temperamental. It refused to
restart saying that the data directory is not found.
When we posted this message last time... Somebody said... check out whether
hard disk mounted. This is hilarious. We are doing serious stuff and the
minimum we ensure that the directory exists.

Finally I have cracked the problem. ipcclean utility does nothing. Instead
you have to explicitly use ipcs and ipcrm and to clear all semaphore and
shared memory which is blocked. After which restarting postmaster goes
thru'.

Hope this helps somebody in a different state of distress than mine.

Bye,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

From bouncefilter Tue Dec 14 23:41:30 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id XAA64836
for <pgsql-general@postgreSQL.org>;
Tue, 14 Dec 1999 23:41:11 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA21239;
Wed, 15 Dec 1999 00:40:47 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 00:40:46 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
cc: pgsql-general@postgreSQL.org, Kimi <kimi@intercept.co.in>
Subject: Re: [GENERAL] Postgres instability : AN APPEAL
In-Reply-To: <000101bf46b4$967b8c00$8ab6c5cb@nagma>
Message-ID: <Pine.BSF.4.21.9912150039010.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Since you haven't provided much information, lets' start with:

what version of PostgreSQL?
what operating system?

and we can work from that... :)

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

I have unfortunately programmed a mission critical application in postgres
without doing full load testing.
Now I'm getting lots of messages when I start stressing it.
Typical messages include --- Spinlock error, ReleaseLRU no files found etc.,
Last couple of days I'm battling by switching on the pgoptions. They don't
seem to help... because I can't correlate which message is coming from which
process or session or SQL.
I have posted a detailed message on this error last week. Nobody responded.

THIS IS AN APPEAL. If any of you has experience in handling postgres locking
and instabilities.... CAN YOU PLEASE WRITE TO ME. I'm desperate to talk to
somebody who can understand my problems and give me some intelligent
suggestions.

Thanks in Advance,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

************

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 00:20:31 1999
Received: from news.tht.net (news.hub.org [216.126.91.242])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA88964;
Wed, 15 Dec 1999 00:20:23 -0500 (EST)
(envelope-from news@news.tht.net)
Received: (from news@localhost) by news.tht.net (8.9.3/8.9.3) id XAA04581;
Tue, 14 Dec 1999 23:54:04 -0500 (EST) (envelope-from news)
X-Authentication-Warning: news.tht.net: news set sender to <news> using -f
From: "Bob Pfeiff" <rpfeiff@erols.com>
References: <Imh34.20953$Tp.847209@typ11.nn.bcandid.com>
<#JZwP7RQ$GA.299@cppssbbsa04> <3855A863.C0D9FC29@prodigy.net>
Subject: Re: Memory bug
Date: Tue, 14 Dec 1999 23:44:02 -0500
Lines: 6
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <ug9O0grR$GA.255@cppssbbsa05>
X-Newsgroups: comp.databases.postgresql.patches,
comp.databases.postgresql.questions,
microsoft.public.sqlserver.misc, microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.programming,
microsoft.public.sqlserver.server
To: pgsql-patches@postgresql.org.pgsql-questions@postgresql.org

Can't say I've seen a problem like this and I've looked at a variety of
systems including a heavily used Peoplesoft system and a data warehouse that
we did daily loads on. A GB of RAM is a lot to use up, how much data is
coming in via the app that's loading data?

From bouncefilter Wed Dec 15 00:06:30 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA82702
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 00:05:32 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.43.244]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Tue, 14 Dec 1999 22:57:07 -0600
Sender: ed
Message-ID: <385721CD.623C83C3@austin.rr.com>
Date: Tue, 14 Dec 1999 23:06:21 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Mailing Lists
References: <Pine.BSF.4.21.9912142156440.57039-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The Hermit Hacker wrote:

Would you use the archives off the cd ?

Consider the point, that these archives are possibly outdated when
you receive the cd, and that the Live archives on www.postgresql.org
are searchable.

CD archives would seem replaceable to me if the www.postgresql.org search
engine were a bit more reliable and useful (ie easier to navigate threads
found via search.

Okay, I'm confused...when ht/dig worked, if you clicked on a mesage you
wanted to read, that message had a 'thread' link that would list all
messages in that thread...

...or are you talking about something different?

Yes, that is the general context to which I'm referring. If that thread link was
there, then I'm either thinking about some other context or I just missed it.
I'll try to provide more contextual details if the engine comes back online.

Cheers.
Ed Loehr

From bouncefilter Wed Dec 15 00:15:30 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA88118
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 00:14:28 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-182-138.bng.vsnl.net.in [203.197.182.138])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id KAA07837;
Wed, 15 Dec 1999 10:45:17 +0500 (GMT+0500)
Message-ID: <001601bf46bb$2387e340$8ab6c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <scrappy@hub.org>, <pgsql-general@postgresql.org>
Subject: Fw: Spin lock error
Date: Wed, 15 Dec 1999 10:43:18 +0530
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0013_01BF46E9.3311EBC0"

This is a multi-part message in MIME format.

------=_NextPart_000_0013_01BF46E9.3311EBC0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit

Hi,

Thanks for responding.
This is a copy of my message which has all details which I could think of to
start with.
I would be glad to receive any suggesstions.

Bye,

Murali
-----Original Message-----
From: Differentiated Software Solutions Pvt. Ltd. +ADw-diffs+AEA-vsnl.com+AD4-
To: pgsql-general+AEA-postgresql.org +ADw-pgsql-general+AEA-postgresql.org+AD4AOw-
vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw- pgsql-interfaces+AEA-postgresql.org
+ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
Date: 11 December 1999 12:33
Subject: Spin lock error

+AD4-Hi,
+AD4-
+AD4-We are getting spinlock errors under the following conditions
+AD4-
+AD4-Background :
+AD4-We have developed a high performance application using postgres database
 a
+AD4-3rd party application server).
+AD4-This application should be scalanble to server 50 requests a second.
+AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92 and Redhat
+AD4-linux 6.0
+AD4-A request consists of one singleton select on a table of 200,000 rows on
+AD4-it's primary key, a heavy duty cursor which is a 4 table join but which
+AD4-returns 100 rows from tables containing maximum of 250 rows, a light sql
+AD4-opening a cursor on a table containing 500 rows, 2 inserts into tables
which
+AD4-don't have primary key.
+AD4-
+AD4-We are connecting to the database with autoconnect off.
+AD4-
+AD4-Problem description :
+AD4-On a light load there are no problems. As we have increased the load on the
+AD4-application, the requests get piled up. We keep monitoring the requests
+AD4-getting piled up using ps ax +AHw- grep post.
+AD4-Somewhere when the requests crosses 20(ps returns more than 20 rows)....
+AD4-suddenly postmaster comes down +ACEAIQ- In the server log the following message
is
+AD4-written out.
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock. Aborting.
+AD4-After this postmaster shutdown.
+AD4-
+AD4-One observation If we try to recreate this in another linux machine...
+AD4-multiple postmasters run in the linux machine when the number of requests
+AD4-become more.
+AD4-I'm also attaching a file containing 'ps' at the instance postmaster
+AD4-crashed.
+AD4-
+AD4-Can anybody please help
+AD4-
+AD4-Thanks and regards,
+AD4-
+AD4-Murali
+AD4-
+AD4-Differentiated Software Solutions Pvt. Ltd.,
+AD4-176, Gr. Floor, 6th Main
+AD4-2nd Block RT Nagar
+AD4-Bangalore - 560 032
+AD4-India
+AD4-Ph: 91 80 3431470
+AD4-

------=_NextPart_000_0013_01BF46E9.3311EBC0
Content-Type: text/plain;
name="ps.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="ps.txt"

bash: /bin/ps: Too many open files in system=20

------=_NextPart_000_0013_01BF46E9.3311EBC0--

From bouncefilter Wed Dec 15 00:27:30 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA89917
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 00:26:50 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA50710;
Wed, 15 Dec 1999 01:26:49 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 01:26:48 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: Fw: Spin lock error
In-Reply-To: <001601bf46bb$2387e340$8ab6c5cb@nagma>
Message-ID: <Pine.BSF.4.21.9912150126290.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I seem to still be missing what version of PostgreSQL you are running...:(

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Thanks for responding.
This is a copy of my message which has all details which I could think of to
start with.
I would be glad to receive any suggesstions.

Bye,

Murali
-----Original Message-----
From: Differentiated Software Solutions Pvt. Ltd. +ADw-diffs+AEA-vsnl.com+AD4-
To: pgsql-general+AEA-postgresql.org +ADw-pgsql-general+AEA-postgresql.org+AD4AOw-
vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw- pgsql-interfaces+AEA-postgresql.org
+ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
Date: 11 December 1999 12:33
Subject: Spin lock error

+AD4-Hi,
+AD4-
+AD4-We are getting spinlock errors under the following conditions
+AD4-
+AD4-Background :
+AD4-We have developed a high performance application using postgres database
a
+AD4-3rd party application server).
+AD4-This application should be scalanble to server 50 requests a second.
+AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92 and Redhat
+AD4-linux 6.0
+AD4-A request consists of one singleton select on a table of 200,000 rows on
+AD4-it's primary key, a heavy duty cursor which is a 4 table join but which
+AD4-returns 100 rows from tables containing maximum of 250 rows, a light sql
+AD4-opening a cursor on a table containing 500 rows, 2 inserts into tables
which
+AD4-don't have primary key.
+AD4-
+AD4-We are connecting to the database with autoconnect off.
+AD4-
+AD4-Problem description :
+AD4-On a light load there are no problems. As we have increased the load on the
+AD4-application, the requests get piled up. We keep monitoring the requests
+AD4-getting piled up using ps ax +AHw- grep post.
+AD4-Somewhere when the requests crosses 20(ps returns more than 20 rows)....
+AD4-suddenly postmaster comes down +ACEAIQ- In the server log the following message
is
+AD4-written out.
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock. Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock. Aborting.
+AD4-After this postmaster shutdown.
+AD4-
+AD4-One observation If we try to recreate this in another linux machine...
+AD4-multiple postmasters run in the linux machine when the number of requests
+AD4-become more.
+AD4-I'm also attaching a file containing 'ps' at the instance postmaster
+AD4-crashed.
+AD4-
+AD4-Can anybody please help
+AD4-
+AD4-Thanks and regards,
+AD4-
+AD4-Murali
+AD4-
+AD4-Differentiated Software Solutions Pvt. Ltd.,
+AD4-176, Gr. Floor, 6th Main
+AD4-2nd Block RT Nagar
+AD4-Bangalore - 560 032
+AD4-India
+AD4-Ph: 91 80 3431470
+AD4-

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 01:27:31 1999
Received: from mail.rdc1.sfba.home.com (imail@ha1.rdc1.sfba.home.com
[24.0.0.66]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA01025
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 01:27:25 -0500 (EST)
(envelope-from vdiciero@home.com)
Received: from c451231a ([24.5.53.147]) by mail.rdc1.sfba.home.com
(InterMail v4.01.01.00 201-229-111) with SMTP
id <19991215062720.HHWM14222.mail.rdc1.sfba.home.com@c451231a>
for <pgsql-general@postgreSQL.org>; Tue, 14 Dec 1999 22:27:20 -0800
Reply-To: <vdiciero@home.com>
From: "Vince DiCiero" <vdiciero@home.com>
To: <pgsql-general@postgreSQL.org>
Subject: RE: [GENERAL] Access rescrictions
Date: Wed, 15 Dec 1999 00:29:13 -0600
Message-ID: <000401bf46c5$b5057a80$3600a8c0@home.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <Pine.LNX.4.20.9912142358520.5253-100000@localhost.localdomain>
Importance: Normal

Couldn't you restrict access to the table
and create views such as

CREATE VIEW BillsCustomerID001 AS
SELECT * FROM Bills WHERE CustomerID=001

CREATE VIEW BillsCustomerID002 AS
SELECT * FROM Bills WHERE CustomerID=002

etc.

and give Customer 001 access to BillsCustomerID001
give Customer 002 access to BillsCustomerID002
etc.

Would this solve your problem ?

Vince

-----Original Message-----
From: owner-pgsql-general@postgreSQL.org
[mailto:owner-pgsql-general@postgreSQL.org]On Behalf Of Peter
Eisentraut
Sent: Tuesday, December 14, 1999 5:02 PM
To: Elmar.Haneke@gmx.de
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Access rescrictions

On 1999-12-14, Elmar.Haneke@gmx.de mentioned:

I'm looking for an solution to restrict the access to show

an part of an Table only:

In an customer-database it should be possible to list the

bills of an certain customer,

but it should be restricted to generate/summarize a list of

all bills.

"SELECT * FROM Bills" should be restricted
"SELECT * FROM Bills WHERE CustomerID=?" should be allowed

for any CustomerID.

Is there an solution to this problem in PostgreSQL?

No. I think hardly any database engine will be able to restrict access
according to query semantics. You will have to do this via your client
application.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

************

From bouncefilter Wed Dec 15 02:38:32 1999
Received: from beta.dmz-eu.st.com (beta.st.com [164.129.1.35])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA15130
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 02:38:02 -0500 (EST)
(envelope-from lincoln.spiteri@st.com)
Received: from eux100.sgp.st.com (eux100.sgp.st.com [164.129.225.7])
by beta.dmz-eu.st.com (Postfix) with ESMTP id 783F625B1
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 07:37:20 +0000 (GMT)
Received: from voltaire.kir.st.com ([164.130.159.103] (may be forged))
by eux100.sgp.st.com (8.8.6 (PHNE_17190)/8.8.6) with SMTP id IAA22628;
Wed, 15 Dec 1999 08:37:19 +0100 (MET)
From: Lincoln Spiteri <lincoln.spiteri@st.com>
Organization: STMicroelectronics
To: diffs@vsnl.com, scrappy@hub.org, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Fw: Spin lock error
Date: Wed, 15 Dec 1999 09:31:37 +0100
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <001601bf46bb$2387e340$8ab6c5cb@nagma>
In-Reply-To: <001601bf46bb$2387e340$8ab6c5cb@nagma>
MIME-Version: 1.0
Message-Id: <99121509340300.03978@voltaire.kir.st.com>
Content-Transfer-Encoding: 8bit

On Wed, 15 Dec 1999, diffs@vsnl.com wrote:

6184 p2 R 0:00 /usr/local/bin/postgres localhost postgres adcept SELECT
20964 p6 S 0:00 su - postgres
23112 p4 S 0:00 su - postgres
27664 p2 R 0:03 /usr/local/bin/postmaster -i

bash: /bin/ps: Too many open files in system

I was getting this recently on a production server, I solved it by increasing
the number of file descriptors per process in the kernel. Do a ulimit -a to see
what your limits are.

Lincoln

--
------------------------------------------------------------------------------

Lincoln Spiteri

Manufacturing Systems
STMicroelectronics, Malta

e-mail: lincoln.spiteri@st.com

------------------------------------------------------------------------------

From bouncefilter Wed Dec 15 04:31:33 1999
Received: from banquise.gnulinux-jobs.org (banquise.ceic.com [194.98.185.244])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA39748
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 04:31:18 -0500 (EST)
(envelope-from rodolphe@ecila.fr)
Received: from ecila.fr (IDENT:rodo@localhost.localdomain [127.0.0.1])
by banquise.gnulinux-jobs.org (8.9.3/8.9.3) with ESMTP id KAA07719
for <pgsql-general@postgreSQL.org>; Wed, 15 Dec 1999 10:30:23 +0100
Sender: rodo@banquise.gnulinux-jobs.org
Message-ID: <38575FAE.D0BE3C8@ecila.fr>
Date: Wed, 15 Dec 1999 10:30:22 +0100
From: Rodolphe QUIEDEVILLE <rodolphe@ecila.fr>
Organization: Ecila
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-general@postgreSQL.org" <pgsql-general@postgreSQL.org>
Subject: ORDER BY Problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi see this :

test=> select ch from test order by ch ;
ch
----------
aa (1)
bb
cc
-- cc -- (2)
dd
-- vv --
www
{www} (3)
zz
(9 rows)

test=>

My problem is I want the line (2) appears in first and the line (3) in
last. I'm not found an answer to my problem in docs. So please help and
explain to me how to configure correctly the sort.

Thanks.

I'm using the 6.5.3 version of Pg on RH 6.1.
Thanks again

--
Rodolphe QUIEDEVILLE
ECILA : http://www.ecila.fr/
rodolphe@ecila.fr

From bouncefilter Wed Dec 15 05:56:34 1999
Received: from ns.webset.de (ns.webset.de [195.35.1.102])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA54796
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 05:56:32 -0500 (EST)
(envelope-from paulsen@hempels-ev.de)
Received: from hempels-ev.de (p150.n04.ham.access.is-europe.net
[195.179.179.150])
by ns.webset.de (8.9.3/8.9.3) with ESMTP id LAA25759
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 11:57:27 +0100
Message-ID: <38577439.BC5A3DC6@hempels-ev.de>
Date: Wed, 15 Dec 1999 11:58:01 +0100
From: Catharina Paulsen <paulsen@hempels-ev.de>
X-Mailer: Mozilla 4.7 [de] (Win98; I)
X-Accept-Language: de
MIME-Version: 1.0
To: pgsql-general@hub.org
Subject: Postgres with PHP
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id FAA54799

Hello,

I can�t get my local Postgres database work with PHP over TCP/IP
(Browser) connection.

PHP 3.12 is installed as Apache-module (Apache 1.3.9)
Postgres version 6.5., both came with my SuSE 6.3

The query script is running without problems at my provider�s machine
(apache 1.3.9, PHP 3.0.7 as CGI, Postgres 6.5).

On my local SuSE-box, psql monitor works fine. Access per telnet from
remote host (win98) is ok, there are no error messages or problems
with queries.

The problem occurs when connecting with
$conn = pg_Connect("192.168.0.1", "5432", "username" ,"***",
"name_db");
I get following error message:

Unable to connect to PostgresSQL server: pgReadData() -- backend
closed the channel unexpectedly. This probably means the backend
terminated abnormally before or while processing the request.

Log message:
Usage: /usr/lib/pgsql/bin/postgres [options] [dbname]
-A on enable/disable assert checking
[...]
-v version set protocol version being used by frontend

I searched all manuals and the archive, but I have no ideas.

Thanks,
Catharina

*******************************************************************
hba.conf file entry:
local all trust
host all 127.0.0.1 255.255.255.255 trust
host all 192.168.0.0 255.255.255.0 trust

catha@server:~ > ps aux |grep pgsql
postgres 1664 0.0 1.6 5180 1012 ? S Dec05 0:00
/usr/lib/pgsql/bin/postmaster -i -o -F -D/var/lib/pgsql/data

catha@server:~ > netstat -an |grep 5432
tcp 0 0 0.0.0.0:5432 0.0.0.0:*
LISTEN
unix 0 [ ACC ] STREAM LISTENING 166
/tmp/.s.PGSQL.5432

catha@server:~ > ipcs

------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00280267 772 root 644 1048576 0

------ Semaphore Arrays --------
key semid owner perms nsems status
0x00280269 514 root 666 14

------ Message Queues --------
key msqid owner perms used-bytes messages

--
Hempels Stra�enmagazin im Internet: http://www.hempels-ev.de

From bouncefilter Wed Dec 15 06:07:34 1999
Received: from hermes-1.bizonline.net (hermes-1.bizonline.net [212.95.128.5])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA58596
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 06:07:05 -0500 (EST)
(envelope-from apronakis@bizonline.net)
Received: from andreas (times.bizonline.net [212.95.128.253])
by hermes-1.bizonline.net (8.9.3/8.9.3) with SMTP id LAA07013
for <pgsql-general@postgresql.org>; Wed, 15 Dec 1999 11:12:17 GMT
Message-ID: <004e01bf46ec$84593c10$7200000a@andreas>
From: "Andreas Pronakis" <apronakis@bizonline.net>
To: <pgsql-general@postgresql.org>
Subject: Stable version
Date: Wed, 15 Dec 1999 11:07:03 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

I'm planning to use PostgreSQL for building our main system could you tell
me which version is the most stable one? Will it be able to cope with a
very large number of records (about 4 billion!!!)?

Kind Regards
Andreas Pronakis
Developer
------------- Business Online Group plc --------------
Business Online | Public Online
http://www.bizonline.net | http://www.publiconline.net
------------- Britain's Premier Free ISP --------------

From bouncefilter Wed Dec 15 05:24:34 1999
Received: from chekov.Belgium.EU.net (chekov.belgium.eu.net [193.74.208.161])
by hub.org (8.9.3/8.9.3) with ESMTP id FAA48818
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 05:24:22 -0500 (EST)
(envelope-from wim.ceulemans@nice.be)
Received: from (IDENT:0@idialup239.brussels2.eunet.be [193.121.143.239])
by chekov.Belgium.EU.net with ESMTP id LAA21349;
Wed, 15 Dec 1999 11:24:10 +0100 (MET)
Received: from nice.be ; Wed, 15 Dec 1999 11:19:25 +0100
Sender: Wim.Ceulemans@nice.be
Message-ID: <38577B03.A612ECAD@nice.be>
Date: Wed, 15 Dec 1999 12:26:59 +0100
From: Wim Ceulemans <wim.ceulemans@nice.be>
Organization: Nice bvba
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Karl Eichwalder <ke@suse.de>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Installation problem on Suse linux 6.3
References: <3852493A.5484BB07@nice.be> <shwvqj9cky.fsf@Frechet.suse.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Karl Eichwalder wrote:

Wim Ceulemans <wim.ceulemans@nice.be> writes:

| I can't seem to install the latest postgresql opn Suse linux 6.3 (kernel
| 2.2.13, glibc 2.1.2). I always get the following message when I run
| ./configure :
|
| checking for c++... c++
| checking wheather the C++ compiler (C++ ) works... no
| configure: error: installation or configuration problem': C++ compiler
| cannot create executables.

Please check, whether "libgpp" from serie "d" is installed:

rpm -q libgpp

Of cource, you'll also need the package "gpp".

rpm -q lib gpp reports:
libgpp-991012-3

And of course I had installed gpp and libgpp. I tried removing and
re-installing them but this doesn't help.

I can't find a libgpp under /lib or /usr/lib, I do find a libg++
library.
Is this normal, or has the library another name?

Regards
Wim

From bouncefilter Wed Dec 15 08:47:36 1999
Received: from platinumsolutions.com (dns-2.tricreations.com [216.205.16.111])
by hub.org (8.9.3/8.9.3) with SMTP id IAA87465
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 08:47:12 -0500 (EST)
(envelope-from adam.rossi@platinumsolutions.com)
Received: from rsdevelop ([24.28.195.170]) by platinumsolutions.com ;
Wed, 15 Dec 1999 08:38:32 -0500
Message-ID: <015c01bf4702$131ba9f0$0200a8c0@rsdevelop>
Reply-To: "Adam Rossi" <adam.rossi@platinumsolutions.com>
From: "Adam Rossi" <adam.rossi@platinumsolutions.com>
To: <pgsql-general@postgreSQL.org>
Subject: server hardware recommendations (the archives are dead)
Date: Wed, 15 Dec 1999 08:41:20 -0500
Organization: PlatinumSolutions Inc.
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

I know this question has been asked before. I have seen it in the archives.
Unfortunately the archives are dead right now (any search will yield "no
results") and I need to make some decisions.

Can anyone give some general recommendations on hardware for a server
running Linux (RH6 or 6.1) and PostgreSQL? I estimate that there will be
about 2 GIG of data stored in the database initially, but this could grow as
high as 5 GIG in the future.

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any
database server, a lot of ram will be required for fast operation. I was
thinking at a minimum 256 meg of ram. I also want to have the database run
on a RAID 5 array for speed and fault tolerance. Any suggestions here for
disk type, RAID scheme (software or hardware), controller type, etc.? Any
rule of thumb on the "extra" disk space needed above raw storage space for
PostgreSQL operations (temporary tables, vacuum issues, etc)?

Any past experiences, benchmarks, guesses, or hearsay gladly accepted.
Thanks for your help.

- Adam

-------------------
Adam Rossi
President, PlatinumSolutions, Inc.
adam.rossi@platinumsolutions.com
http://www.platinumsolutions.com
P.O. Box 31 Oakton, VA 22124
PH: 703.352.8576 FAX: 703.352.8577

From bouncefilter Wed Dec 15 09:03:36 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA91953
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 09:02:37 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA21153;
Wed, 15 Dec 1999 10:02:51 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 10:02:51 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Adam Rossi <adam.rossi@platinumsolutions.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives are dead)
In-Reply-To: <015c01bf4702$131ba9f0$0200a8c0@rsdevelop>
Message-ID: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Adam Rossi wrote:

I know this question has been asked before. I have seen it in the archives.
Unfortunately the archives are dead right now (any search will yield "no
results") and I need to make some decisions.

Can anyone give some general recommendations on hardware for a server
running Linux (RH6 or 6.1) and PostgreSQL? I estimate that there will be
about 2 GIG of data stored in the database initially, but this could grow as
high as 5 GIG in the future.

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any

actually, if you are going to have concurrent connections to the backend,
in some circumstances, PostgreSQL will handle multi-processors better then
others...process one runs on CPU0, process two runs on CPU1, etc...

database server, a lot of ram will be required for fast operation. I was
thinking at a minimum 256 meg of ram. I also want to have the database run
on a RAID 5 array for speed and fault tolerance. Any suggestions here for
disk type, RAID scheme (software or hardware), controller type, etc.? Any

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 09:31:37 1999
Received: from moon.mteege.de (ppps-nb03.MVnet.de [194.25.108.153])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA98090
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 09:31:27 -0500 (EST)
(envelope-from matthias@mteege.de)
Received: from moon.mteege.de (localhost [127.0.0.1])
by moon.mteege.de (8.8.8/8.8.8) with ESMTP id PAA08891
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 15:23:29 +0100 (MET)
(envelope-from matthias@moon.mteege.de)
Message-Id: <199912151423.PAA08891@moon.mteege.de>
From: Matthias Teege <matthias@mteege.de>
To: pgsql-general@postgresql.org
Subject: Connect from a new psql to an old 6.0 postmaster
Reply-To: Matthias Teege <matthias@mteege.de>
Date: Wed, 15 Dec 1999 15:23:28 +0100
Sender: matthias@mteege.de

Moin,

I have two database servers. One running postgresql 6.0
and the new one running 6.5.1.

If I run "psql -h oldone -d oldone -u" from the newer
server and input username and password psql says:

Connection to database 'oldone' failed.
Failed to authenticate client as Postgres user 'olduser'
using authentication scheme 131072.

What does it mean and how can I fix this.

Many thanks
Matthias

From bouncefilter Wed Dec 15 10:00:37 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA04326
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 10:00:01 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA37681
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 11:00:01 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 11:00:01 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-general@postgresql.org
Subject: Mailing List Archives off of Web Site ...
Message-ID: <Pine.BSF.4.21.9912151059160.8120-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just fixed the script that creates the links for the mailing list
archives off of each 'list' page (the 'mbox' link), so that it has the
proper name...

Any other problems, let us know...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 10:03:37 1999
Received: from propertykey.com (IDENT:root@propertykey.com [206.196.37.193])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA07317
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 10:03:09 -0500 (EST)
(envelope-from jeff@propertykey.com)
Received: from propertykey.com (gotojail.propertykey.com [206.196.37.197])
by propertykey.com (8.9.3/8.9.3) with ESMTP id KAA11511;
Wed, 15 Dec 1999 10:03:04 -0600
Message-ID: <3857ADA8.974ACD6C@propertykey.com>
Date: Wed, 15 Dec 1999 09:03:04 -0600
From: Jeff Hoffmann <jeff@propertykey.com>
Organization: PropertyKey.com
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: Adam Rossi <adam.rossi@platinumsolutions.com>,
pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The Hermit Hacker wrote:

On Wed, 15 Dec 1999, Adam Rossi wrote:

I know this question has been asked before. I have seen it in the archives.
Unfortunately the archives are dead right now (any search will yield "no
results") and I need to make some decisions.

Can anyone give some general recommendations on hardware for a server
running Linux (RH6 or 6.1) and PostgreSQL? I estimate that there will be
about 2 GIG of data stored in the database initially, but this could grow as
high as 5 GIG in the future.

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any

actually, if you are going to have concurrent connections to the backend,
in some circumstances, PostgreSQL will handle multi-processors better then
others...process one runs on CPU0, process two runs on CPU1, etc...

just to expand on this a little, it really depends on how the OS handles
threads. at worst case, a multithreaded process might be restricted to
running all its threads on a single CPU. i don't know of any OS's that
do that, though. the best case for a multithreaded process (DB) would
be that it could run threads on all processors simultaneously, which
should be nearly equivalent to a multiprocess DB which should (assign
the processes to the CPUs automatically), minus the overhead of each of
the processes. then again, my understanding is that in linux, a thread
is pretty much equivalent to a process anyway, so it would be a wash.
to sum up, SMP & postgres is a good idea.

database server, a lot of ram will be required for fast operation. I was
thinking at a minimum 256 meg of ram. I also want to have the database run
on a RAID 5 array for speed and fault tolerance. Any suggestions here for
disk type, RAID scheme (software or hardware), controller type, etc.? Any

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

i kind of question this, and here's why: i just set up a linux dual
P3/256MB with 4 software raid 5 volumes and even loading data into one
of the databases slows it to a crawl. i've been looking around because
it seems absurd that the machine should slow down so much. i haven't
really found any answers, but i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is. i am running kernel 2.2.12 & i'm
not having any problems with it other than it slowing down to a crawl &
that only happens when i'm loading data. right now i'm guessing the
reason for this is that the raid5 daemon is such a high priority that
it's sucking away all the CPU cycles from everything else to calculate
parity information. like i said, i haven't found a lot of information
about this, so if someone could confirm or explain what's happening, i'd
appreciate it. assuming this is the case, software raid wouldn't be a
big problem if you don't do a lot of heavy writing.

From bouncefilter Wed Dec 15 10:28:43 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA10567
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 10:27:44 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA37884;
Wed, 15 Dec 1999 11:27:37 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 11:27:36 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Jeff Hoffmann <jeff@propertykey.com>
cc: Adam Rossi <adam.rossi@platinumsolutions.com>,
pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
In-Reply-To: <3857ADA8.974ACD6C@propertykey.com>
Message-ID: <Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Jeff Hoffmann wrote:

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

i kind of question this, and here's why: i just set up a linux dual
P3/256MB with 4 software raid 5 volumes and even loading data into one
of the databases slows it to a crawl. i've been looking around because
it seems absurd that the machine should slow down so much. i haven't
really found any answers, but i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is.

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

appreciate it. assuming this is the case, software raid wouldn't be a
big problem if you don't do a lot of heavy writing.

Most of my RAID tests are on Solaris+Disksuite...with good drives
in the machine, my writes are something like 18MB/s to the drive, stripe'd
and mirrored...I think reads worked out to be 19MB/s...(bad drives, same
setup, same machine, same OS, were net'ng me something like 3MB/s...really
killed performance *grin*)

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 10:44:43 1999
Received: from tango.SoftHome.net (tango.SoftHome.net [204.144.231.49])
by hub.org (8.9.3/8.9.3) with SMTP id KAA15126
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 10:43:43 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 32502 invoked by uid 417); 15 Dec 1999 15:48:38 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtpa.softhome.net with SMTP; 15 Dec 1999 15:48:38 -0000
Message-ID: <00ce01bf4713$1b47bc20$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "pgsql-list" <pgsql-general@hub.org>
References: <Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
Date: Wed, 15 Dec 1999 16:43:15 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

What is the problem with ext2fs? Is it just performance? or is there a
serious chance for me losing data?

Joost Roeleveld

From bouncefilter Wed Dec 15 11:07:38 1999
Received: from [12.6.225.3] ([12.6.225.3])
by hub.org (8.9.3/8.9.3) with SMTP id LAA20891
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 11:06:40 -0500 (EST)
(envelope-from rdavis@lillysoftware.com)
Received: from lillysoftware.com by [12.6.225.3]
via smtpd (for postgresql.org [216.126.84.28]) with SMTP;
15 Dec 1999 16:06:21 UT
Received: from lillysoftware.com (BOBIBM333 [173.100.2.237]) by
ponyexpress.LillySoftware.com with SMTP (Microsoft Exchange
Internet Mail Service Version 5.5.2448.0)
id YR9L5SW6; Wed, 15 Dec 1999 11:04:23 -0500
Message-ID: <3857BC8C.B8629628@lillysoftware.com>
Date: Wed, 15 Dec 1999 11:06:36 -0500
From: Robert Davis <rdavis@lillysoftware.com>
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Postgres restart problems
References: <000201bf46b4$97a9abc0$8ab6c5cb@nagma>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I remember having to do the same thing on a aix oracle installation.
I wrote a little shell script that did it for me.

bob

"Differentiated Software Solutions Pvt. Ltd." wrote:

Hi,

We have a postgres db which has been crashing about 5 times a day. It must
be failrly apparent given my other messages to this mailing list.

Now we are faced with a new problem. After crash we were able to restart
postmaster. Now postgres is getting more temperamental. It refused to
restart saying that the data directory is not found.
When we posted this message last time... Somebody said... check out whether
hard disk mounted. This is hilarious. We are doing serious stuff and the
minimum we ensure that the directory exists.

Finally I have cracked the problem. ipcclean utility does nothing. Instead
you have to explicitly use ipcs and ipcrm and to clear all semaphore and
shared memory which is blocked. After which restarting postmaster goes
thru'.

Hope this helps somebody in a different state of distress than mine.

Bye,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

+ACoAKgAqACoAKgAqACoAKgAqACoAKgAq-

--
rdavis@lillysoftware.com
rsdavis@mediaone.net
http://people.ne.mediaone.net/rsdavis

From bouncefilter Wed Dec 15 15:14:43 1999
Received: from camino.pa.tibcofinance.com ([216.101.119.58])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA96277
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 15:14:05 -0500 (EST)
(envelope-from maarten.boekhold@tibcofinance.com)
Received: from tekbspa.tibcofinance.com (tekbspa.tibcofinance.com
[160.101.12.31])
by camino.pa.tibcofinance.com (8.9.3/8.9.3) with SMTP id MAA01030;
Wed, 15 Dec 1999 12:07:32 -0800 (PST)
Received: from tibcofinance.com ([160.101.149.37]) by tekbspa.tibcofinance.com
(4.1/SMI-4.1) id AA08217; Wed, 15 Dec 99 12:09:52 PST
Message-Id: <3857C031.2BD26E88@tibcofinance.com>
Date: Wed, 15 Dec 1999 17:22:09 +0100
From: Maarten Boekhold <maarten.boekhold@tibcofinance.com>
Organization: TIBCO Finance Technology Inc.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
Mime-Version: 1.0
To: Adam Rossi <adam.rossi@platinumsolutions.com>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives are dead)
References: <015c01bf4702$131ba9f0$0200a8c0@rsdevelop>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any

If your disk subsystem can take the load, it does make sense. For every
connection to PostgreSQL, a seperate backend is started, which is really a
seperate process which so can run on a different processor.

Maarten

From bouncefilter Wed Dec 15 11:28:38 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA23848
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 11:27:45 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id MAA38356;
Wed, 15 Dec 1999 12:27:44 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 12:27:44 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "J. Roeleveld" <j.roeleveld@softhome.net>
cc: pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
In-Reply-To: <00ce01bf4713$1b47bc20$8402a8c0@sentec.demon.nl>
Message-ID: <Pine.BSF.4.21.9912151226560.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, J. Roeleveld wrote:

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

What is the problem with ext2fs? Is it just performance? or is there a
serious chance for me losing data?

That, I do not know...this is just something I recall from previous
discussions...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 11:48:38 1999
Received: from mx20.rmci.net (halcyon.rmci.net [205.162.184.63])
by hub.org (8.9.3/8.9.3) with SMTP id LAA30185
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 11:48:36 -0500 (EST)
(envelope-from webweaver@rmci.net)
Received: (qmail 17148 invoked from network); 15 Dec 1999 16:48:33 -0000
Received: from usr-boi-307.rmci.net (HELO chilly-willy) (206.159.113.183)
by halcyon.rmci.net with SMTP; 15 Dec 1999 16:48:33 -0000
Message-Id: <3.0.6.32.19991215095107.01331100@rmci.net>
X-Sender: webweaver@rmci.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 15 Dec 1999 09:51:07 -0700
To: "Adam Rossi" <adam.rossi@platinumsolutions.com>,
<pgsql-general@postgreSQL.org>
From: Ken Gunderson <webweaver@rmci.net>
Subject: Re: [GENERAL] server hardware recommendations (the archives are dead)
In-Reply-To: <015c01bf4702$131ba9f0$0200a8c0@rsdevelop>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:41 AM 12/15/99 -0500, Adam Rossi wrote:

I know this question has been asked before. I have seen it in the archives.
Unfortunately the archives are dead right now (any search will yield "no
results") and I need to make some decisions.

Can anyone give some general recommendations on hardware for a server
running Linux (RH6 or 6.1) and PostgreSQL? I estimate that there will be
about 2 GIG of data stored in the database initially, but this could grow as
high as 5 GIG in the future.

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any
database server, a lot of ram will be required for fast operation. I was
thinking at a minimum 256 meg of ram. I also want to have the database run
on a RAID 5 array for speed and fault tolerance. Any suggestions here for
disk type, RAID scheme (software or hardware), controller type, etc.? Any
rule of thumb on the "extra" disk space needed above raw storage space for
PostgreSQL operations (temporary tables, vacuum issues, etc)?

Any past experiences, benchmarks, guesses, or hearsay gladly accepted.
Thanks for your help.

I think you may want to consider a software based volume manager (e.g.
Veritas) and run a stripped mirror (RAID 10) rather than RAID 5. This will
help out on writes. I'm not into RH, but surely they must offer something
comparable to FreeBSD's Vinum. If not, I know Debian has one available.

Ciao-- Ken
http://www.y2know.org/safari

Failure is not an option. It comes bundled with your
Microsoft product.

From bouncefilter Wed Dec 15 12:00:38 1999
Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu
[128.42.12.154])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA44697
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 11:59:54 -0500 (EST)
(envelope-from reedstrm@wallace.ece.rice.edu)
Received: by wallace.ece.rice.edu via sendmail from stdin
id <m11yHmK-000LEEC@wallace.ece.rice.edu> (Debian Smail3.2.0.102)
for pgsql-general@postgresql.org; Wed, 15 Dec 1999 10:59:52 -0600 (CST)
Date: Wed, 15 Dec 1999 10:59:52 -0600
From: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
Message-ID: <19991215105952.A14702@rice.edu>
References: <3857ADA8.974ACD6C@propertykey.com>
<Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>;
from scrappy@hub.org on Wed, Dec 15, 1999 at 11:27:36AM -0400

On Wed, Dec 15, 1999 at 11:27:36AM -0400, The Hermit Hacker wrote:

On Wed, 15 Dec 1999, Jeff Hoffmann wrote:

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

i kind of question this, and here's why: i just set up a linux dual
P3/256MB with 4 software raid 5 volumes and even loading data into one
of the databases slows it to a crawl. i've been looking around because

<snip>

Most of my RAID tests are on Solaris+Disksuite...with good drives
in the machine, my writes are something like 18MB/s to the drive, stripe'd
and mirrored...I think reads worked out to be 19MB/s...(bad drives, same

Ah, this would be a RAID 0+1 setup, then? Very different from Jeff's RAID
5 configuration. I'd be willing to believe that software RAID 0+1 _could_
be faster than most hardware (it's just shuffling and dupping blocks
around to different drives, which could be done with clever pointer
twiddling) but calculating parity bits in hardware for RAID 5 had got
to be a win, doesn't it?

As it turns out, I'm speccing a similar machine right now, myself,
and I've been running into statements like yours re: software RAID that
surprised me.

setup, same machine, same OS, were net'ng me something like 3MB/s...really
killed performance *grin*)

Hmm, bad drives as in broken, or slow?

Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005

From bouncefilter Wed Dec 15 12:16:38 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA49928
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 12:16:17 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id NAA38808;
Wed, 15 Dec 1999 13:16:15 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 13:16:10 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
In-Reply-To: <19991215105952.A14702@rice.edu>
Message-ID: <Pine.BSF.4.21.9912151314470.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Ross J. Reedstrom wrote:

Ah, this would be a RAID 0+1 setup, then? Very different from Jeff's RAID
5 configuration. I'd be willing to believe that software RAID 0+1 _could_
be faster than most hardware (it's just shuffling and dupping blocks
around to different drives, which could be done with clever pointer
twiddling) but calculating parity bits in hardware for RAID 5 had got
to be a win, doesn't it?

Oops, overlooked the RAID5 issue...sorry about that...

setup, same machine, same OS, were net'ng me something like 3MB/s...really
killed performance *grin*)

Hmm, bad drives as in broken, or slow?

Slow...they were bought brand new a year ago...Fujitsu's...even a single,
non-stripe'd drive, was performing atrociously...replaced them with
Seagates and the machine flies ...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 12:50:39 1999
Received: from news.tht.net (news.hub.org [216.126.91.242])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA58460
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 12:50:25 -0500 (EST)
(envelope-from news@news.tht.net)
Received: (from news@localhost) by news.tht.net (8.9.3/8.9.3) id MAA66353
for pgsql-general@postgresql.org; Wed, 15 Dec 1999 12:30:34 -0500 (EST)
(envelope-from news)
X-Authentication-Warning: news.tht.net: news set sender to <news> using -f
Message-ID: <3857D026.DA31E9AE@ironhilltech.com>
Date: Wed, 15 Dec 1999 12:30:14 -0500
From: Dan Linderman <linderdm@ironhilltech.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
X-Newsgroups: comp.databases.postgresql.questions
Subject: "Delete" table
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: 15 Dec 1999 12:30:27 +0500, stargate.sterlingdi.com
Organization: DCANet http://www.dca.net/
Lines: 4
To: pgsql-questions@postgresql.org

I was wondering if PostgreSQL has the system tables similar to Sybase
system tables 'Deleted' and 'Updated' which are used to store the last
deleted or updated records for Rolback purposes.

From bouncefilter Wed Dec 15 12:44:39 1999
Received: from keeper.siac.com (firewall-user@gate.siac.com [162.69.5.193])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA57270
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 12:44:10 -0500 (EST)
(envelope-from rwagner@siac.com)
Received: by keeper.siac.com; id MAA18803;
Wed, 15 Dec 1999 12:44:08 -0500 (EST)
Received: from bigmouth.siac.com(162.69.5.8) by keeper.siac.com via smap
(V4.2)
id xma017916; Wed, 15 Dec 99 12:43:21 -0500
Received: by SIAC_NOTES_001.wisdom.siac.com(Lotus SMTP MTA v1.2 (600.1
3-26-1998)) id 85256848.00611B2A ; Wed, 15 Dec 1999 12:40:39 -0500
X-Lotus-FromDomain: SIAC_01
From: "Robert Wagner" <rwagner@siac.com>
To: pgsql-general@postgreSQL.org
Message-ID: <85256848.005E8A52.00@SIAC_NOTES_001.wisdom.siac.com>
Date: Wed, 15 Dec 1999 12:34:18 -0500
Subject: How do I change port for the postmaster?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

I'm attempting to run two different postmasters on two different HP-UX
servers, servicing two different apps. The only commonality is that I'm on
one terminal.

The first starts up OK. When I attempt to start the postmaster on the
other server, I get the error,

FATAL: StreamServerPort: bind() failed: errno=226 Is another postmaster
already running on that port? If not, remove socket node
(/tmp/.s.PGSQL.5432) and retry./usr/local/pgsql/bin/postmaster: cannot
create UNIX stream port

Tried deleting the file, /tmp/.s.PGSQL.5432 but this had no effect.

Do I need to use a different port number, to run postmaster on two
different servers? If so, does anybody know how I can change the port
number? Is there something else, that I'm doing wrong?

I'm looking through the docs but can't find anything. I'd like to keep
postgres in the organization and avoid switching to (and learning) some big
commercial product like oracle!

Thanks!
Rob Wagner
Lowly Consultant,
SIAC

From bouncefilter Wed Dec 15 12:35:39 1999
Received: from propertykey.com (IDENT:root@propertykey.com [206.196.37.193])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA55519
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 12:35:23 -0500 (EST)
(envelope-from jeff@propertykey.com)
Received: from propertykey.com (gotojail.propertykey.com [206.196.37.197])
by propertykey.com (8.9.3/8.9.3) with ESMTP id MAA11805;
Wed, 15 Dec 1999 12:35:20 -0600
Message-ID: <3857D158.EA0FD4D9@propertykey.com>
Date: Wed, 15 Dec 1999 11:35:20 -0600
From: Jeff Hoffmann <jeff@propertykey.com>
Organization: PropertyKey.com
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <3857ADA8.974ACD6C@propertykey.com>
<Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
<19991215105952.A14702@rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Ross J. Reedstrom" wrote:

On Wed, Dec 15, 1999 at 11:27:36AM -0400, The Hermit Hacker wrote:

On Wed, 15 Dec 1999, Jeff Hoffmann wrote:

Most of my RAID tests are on Solaris+Disksuite...with good drives
in the machine, my writes are something like 18MB/s to the drive, stripe'd
and mirrored...I think reads worked out to be 19MB/s...(bad drives, same

Ah, this would be a RAID 0+1 setup, then? Very different from Jeff's RAID
5 configuration. I'd be willing to believe that software RAID 0+1 _could_
be faster than most hardware (it's just shuffling and dupping blocks
around to different drives, which could be done with clever pointer
twiddling) but calculating parity bits in hardware for RAID 5 had got
to be a win, doesn't it?

i would assume that this would be the case. for anybody who is going to
spec a new machine for a database as small as 3-5G, RAID 0+1 has got to
be the choice. i don't have a doubt that it'd be reasonably fast with
software raid. anymore, it'd be hard to buy new disks that small to
build a 0+1 for < 8G (4x4G will give you 8G). when you're on a budget
with a backup server that needs 20+ drives (n+1 for raid5) vs. 40+
drives (2N for 0+1), though, raid 5 is a good solution. doing it again,
i'd go with a hardware controller since no one seems to be refuting my
assumption that the raid5 daemon can suck up a lot of CPU when
calculating parity, even with 2 fairly fast processors.

From bouncefilter Wed Dec 15 13:18:40 1999
Received: from hermes.iol.cz (hermes.iol.cz [194.228.2.36])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA65450
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 13:18:26 -0500 (EST)
(envelope-from robert@robert.cz)
Received: from robert.cz ([194.228.143.185]) by hermes.iol.cz
(Post.Office MTA v3.5.3 release 223
ID# 631-64078U55000L55000S0V35) with ESMTP id cz
for <pgsql-general@postgreSQL.org>; Wed, 15 Dec 1999 19:17:49 +0100
Message-ID: <3857DC35.93AB4675@robert.cz>
Date: Wed, 15 Dec 1999 19:21:41 +0100
From: Robert <robert@robert.cz>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: Czech2ASCII with --mb=Latin2
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

Hi,

I have a database in Latin2 encoding (Czech stuff) and Latin2/Win1250
on-the-fly recoding with 'set client_encoding' works smoothly. Now, when
I set client encoding to SQL_ASCII, accented characters are converted to
(hexa) codes. Is there any (simple) way to make this recoding convert
accented characters to just the chars themselves but without accents?
Thanks in advance.

- Robert

P.S. Moreover, the non-Czech speakers tend to search the database with
words without accents, it would be usefull to make this conversion works
in the other direction: name LIKE 'ceske%' would return also names
starting with accented version.

P.S.2 I could do this quite easily in Perl on the application level, but
don't want to start programming before I'm sure there's no standard
postgres solution.

From bouncefilter Wed Dec 15 13:50:39 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id NAA72533
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 13:50:36 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.30]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 15 Dec 1999 12:50:55 -0600
Sender: ed
Message-ID: <3857E337.24F7FD69@austin.rr.com>
Date: Wed, 15 Dec 1999 12:51:35 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Wagner <rwagner@siac.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How do I change port for the postmaster?
References: <85256848.005E8A52.00@SIAC_NOTES_001.wisdom.siac.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Syntax:
postmaster -p <port>

Examples:
postmaster -p 5432
postmaster -p 5433

Cheers,
Ed

Robert Wagner wrote:

I'm attempting to run two different postmasters on two different HP-UX
servers, servicing two different apps. The only commonality is that I'm on
one terminal.

The first starts up OK. When I attempt to start the postmaster on the
other server, I get the error,

FATAL: StreamServerPort: bind() failed: errno=226 Is another postmaster
already running on that port? If not, remove socket node
(/tmp/.s.PGSQL.5432) and retry./usr/local/pgsql/bin/postmaster: cannot
create UNIX stream port

Tried deleting the file, /tmp/.s.PGSQL.5432 but this had no effect.

Do I need to use a different port number, to run postmaster on two
different servers? If so, does anybody know how I can change the port
number? Is there something else, that I'm doing wrong?

I'm looking through the docs but can't find anything. I'd like to keep
postgres in the organization and avoid switching to (and learning) some big
commercial product like oracle!

From bouncefilter Wed Dec 15 14:36:41 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA85103
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 14:36:29 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.30]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 15 Dec 1999 13:36:41 -0600
Sender: ed
Message-ID: <3857EDF0.FDC14546@austin.rr.com>
Date: Wed, 15 Dec 1999 13:37:20 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Hoffmann <jeff@propertykey.com>
CC: The Hermit Hacker <scrappy@hub.org>,
Adam Rossi <adam.rossi@platinumsolutions.com>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org>
<3857ADA8.974ACD6C@propertykey.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

database server, a lot of ram will be required for fast operation. I was
thinking at a minimum 256 meg of ram. I also want to have the database run
on a RAID 5 array for speed and fault tolerance. Any suggestions here for
disk type, RAID scheme (software or hardware), controller type, etc.? Any

Obviously, memory needs vary according to what apps are running. On my linux
RH6.0 system, I'm finding that pgsql backends take ~4Mb each. Seems like I need
something near ~100Mb for overhead (X server-20Mb, netscape-40Mb, xterms-10@4Mb
each). For apache with 30 child processes @ 25Mb each (mod_perl with lots of
cached data and lots of modules), that quickly adds up to a gig of ram to avoid
performance-killing swapping.

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

Jeff Hoffman wrote:

...i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is.

Would you mind clarifying your understanding on which versions of linux are unsafe
for software raid and how? Browsing deja, RH 6.1 (2.2.12-20smp) reportedly handles
software raid without known problems (other than less than glowing documentation
reviews), and I'm setting up pgsql/apache on such a system with software raid (no
clear showstopping problems yet).

Thanks,
Ed Loehr

From bouncefilter Wed Dec 15 14:43:41 1999
Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
by hub.org (8.9.3/8.9.3) with ESMTP id OAA86502
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 14:43:12 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.93.40.30]) by mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Wed, 15 Dec 1999 13:43:30 -0600
Sender: ed
Message-ID: <3857EF8A.D247A1C6@austin.rr.com>
Date: Wed, 15 Dec 1999 13:44:10 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: admin <admin@wtbwts.com>
CC: pgsql-general@postgresql.org
Subject: Re: [GENERAL] indices don't make much difference
References: <Pine.BSF.4.10.9912141756480.1350-200000@server.b0x.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Without thinking too much about your problem description, I'd just add that I
have found it useful to use the pgsql EXPLAIN mechanism to show where a query
is using sequential scans (i.e., non-indexed lookups). Generally, you can
then add appropriate indices and verify the seq scan is gone with EXPLAIN.

Cheers.
Ed

admin wrote:

I am trying to optimise a query which looks like:
select prod_base.*, manu_base.name from prod_base, manu_base where
prod_base.mid=manu_base.mid;

manu_base is a table consisting of 3000 manufacturer with an id (not
unique to support synonyms) and a name (declared as varchar(32)).
prod_base is a table of products which each refer to the manufacturer id
(mid).

I have tried creating an index for manu_base using the following commands:
create index manu_mid_idx on "manu_base" using btree ("mid" "int2_ops");
drop index manu_mid_idx
create index manu_mid_idx on "manu_base" using hash ("mid" "int2_ops");
drop index manu_mid_idx

I have then run benchmarks without index, with btree and with hash, but
none seem to be faster than the other. My benchmark program is written in
c and is attached to this email. Here are the results I obtained using
time:

without index:
17.25 real 1.42 user 0.26 sys
with btree:
17.28 real 1.38 user 0.30 sys
with hash:
17.22 real 1.37 user 0.32 sys

If there is any way to make a query quicker when joining a product table
and a manufacturer table, please let me know. I've tried everything and
the results are quite fast enough.

Thanks,
Marc

----------------------------------------------------------------------
Name: bench.c
bench.c Type: Plain Text (TEXT/PLAIN)
Encoding: BASE64
Description: pgsql benchmark

From bouncefilter Wed Dec 15 15:20:40 1999
Received: from ara.zf.jcu.cz (zakkr@ara.zf.jcu.cz [160.217.161.4])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA97277
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 15:20:28 -0500 (EST) (envelope-from zakkr@zf.jcu.cz)
Received: from localhost (zakkr@localhost)
by ara.zf.jcu.cz (8.9.3/8.9.3/Debian/GNU) with SMTP id VAA09142;
Wed, 15 Dec 1999 21:06:23 +0100
Date: Wed, 15 Dec 1999 21:06:23 +0100 (CET)
From: Karel Zak - Zakkr <zakkr@zf.jcu.cz>
To: Robert <robert@robert.cz>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Czech2ASCII with --mb=Latin2
In-Reply-To: <3857DC35.93AB4675@robert.cz>
Message-ID: <Pine.LNX.3.96.991215205746.15100I-100000@ara.zf.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Robert wrote:

Hi,

I have a database in Latin2 encoding (Czech stuff) and Latin2/Win1250
on-the-fly recoding with 'set client_encoding' works smoothly. Now, when
I set client encoding to SQL_ASCII, accented characters are converted to
(hexa) codes. Is there any (simple) way to make this recoding convert
accented characters to just the chars themselves but without accents?
Thanks in advance.

- Robert

Ahoj :-)

if I good remember, in PgSQL is not any routine for this (IMHO is it
lang-specific and make any generally (for all langs and encodings..etc)
routine is problem). But you can easy write this in C or Tcl.

Karel

From bouncefilter Wed Dec 15 15:17:41 1999
Received: from propertykey.com (IDENT:root@propertykey.com [206.196.37.193])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA96773
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 15:16:45 -0500 (EST)
(envelope-from jeff@propertykey.com)
Received: from propertykey.com (gotojail.propertykey.com [206.196.37.197])
by propertykey.com (8.9.3/8.9.3) with ESMTP id PAA12054;
Wed, 15 Dec 1999 15:16:42 -0600
Message-ID: <3857F72A.C95FD63F@propertykey.com>
Date: Wed, 15 Dec 1999 14:16:42 -0600
From: Jeff Hoffmann <jeff@propertykey.com>
Organization: PropertyKey.com
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Loehr <ELOEHR@austin.rr.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org>
<3857ADA8.974ACD6C@propertykey.com>
<3857EDF0.FDC14546@austin.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ed Loehr wrote:

Jeff Hoffman wrote:

...i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is.

Would you mind clarifying your understanding on which versions of linux are unsafe
for software raid and how? Browsing deja, RH 6.1 (2.2.12-20smp) reportedly handles
software raid without known problems (other than less than glowing documentation
reviews), and I'm setting up pgsql/apache on such a system with software raid (no
clear showstopping problems yet).

i'm not running RH6.1, but i am using a 2.2.12 kernel (compiled myself)
and like i said, no catastrophic problems. the problems, i believe,
came up with a conversation about an earlier 2.2 version of the kernel
and it may have included problems with adaptec SCSI controllers in
conjunction with software raid on SMP systems. i don't remember where i
found the references, though. i believe the adaptec 7880 driver was
fixed by 2.2.10, and there were a bunch of SMP fixes between 2.2.6 -
2.2.10, so 2.2.12 is probably as safe as anything. you never hear about
things that work, just about things that don't.

From bouncefilter Wed Dec 15 15:51:41 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA04469
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 15:51:18 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id LAA02594;
Wed, 15 Dec 1999 11:50:59 -0500
Message-ID: <3857FEED.ED9EFCFC@mascari.com>
Date: Wed, 15 Dec 1999 15:49:50 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Hoffmann <jeff@propertykey.com>
CC: "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>,
pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <3857ADA8.974ACD6C@propertykey.com>
<Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
<19991215105952.A14702@rice.edu>
<3857D158.EA0FD4D9@propertykey.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jeff Hoffmann wrote:

"Ross J. Reedstrom" wrote:

On Wed, Dec 15, 1999 at 11:27:36AM -0400, The Hermit Hacker wrote:

On Wed, 15 Dec 1999, Jeff Hoffmann wrote:

Most of my RAID tests are on Solaris+Disksuite...with good drives
in the machine, my writes are something like 18MB/s to the drive, stripe'd
and mirrored...I think reads worked out to be 19MB/s...(bad drives, same

Ah, this would be a RAID 0+1 setup, then? Very different from Jeff's RAID
5 configuration. I'd be willing to believe that software RAID 0+1 _could_
be faster than most hardware (it's just shuffling and dupping blocks
around to different drives, which could be done with clever pointer
twiddling) but calculating parity bits in hardware for RAID 5 had got
to be a win, doesn't it?

i would assume that this would be the case. for anybody who is going to
spec a new machine for a database as small as 3-5G, RAID 0+1 has got to
be the choice. i don't have a doubt that it'd be reasonably fast with
software raid. anymore, it'd be hard to buy new disks that small to
build a 0+1 for < 8G (4x4G will give you 8G). when you're on a budget
with a backup server that needs 20+ drives (n+1 for raid5) vs. 40+
drives (2N for 0+1), though, raid 5 is a good solution. doing it again,
i'd go with a hardware controller since no one seems to be refuting my
assumption that the raid5 daemon can suck up a lot of CPU when
calculating parity, even with 2 fairly fast processors.

Of course, that's the real trick, isn't it? Hard drives are becoming so large, so
fast, it's difficult to determine the proper RAID solution with the supplied
budget. We wanted speed, not volume. So we wanted to build a software RAID 0+1
configuration as cheaply as possible with the fastest disks/controllers. We went
with a multi-channel Ultra-2 Fast Wide Differential contoller (80MB/s) and 80MB/s
LVD Cheetah drivers - the problem in building RAID 0+1 is that none of the drives
come smaller these days then 9G ($450US), so a minimal RAID 0+1 configuration
would be 4 drivers = 18G (2 for the stripe, 2 mirroring the stripe). That seems
like major overkill for a database that NEEDS SPEED, but may only grow to a couple
gig in size...It's too bad we couldn't buy 8 or 16 4G/2G 80MB/s at the
proportional prices.

Also, for what its worth, we've been running PostgreSQL on a dual 450Mhz SMP
running just RAID 1 for about a year now without problems under RedHat 5.2
(2.0.36), although in those earlier kernel versions you have to rebuild the kernel
with _SMP_ defined. It's pretty quick though...

Mike Mascari

From bouncefilter Wed Dec 15 15:57:41 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA05392
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 15:57:18 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id LAA02606;
Wed, 15 Dec 1999 11:57:17 -0500
Message-ID: <38580068.E7BC3DCB@mascari.com>
Date: Wed, 15 Dec 1999 15:56:08 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Hoffmann <jeff@propertykey.com>
CC: Ed Loehr <ELOEHR@austin.rr.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org>
<3857ADA8.974ACD6C@propertykey.com>
<3857EDF0.FDC14546@austin.rr.com>
<3857F72A.C95FD63F@propertykey.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jeff Hoffmann wrote:

Ed Loehr wrote:

Jeff Hoffman wrote:

...i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is.

Would you mind clarifying your understanding on which versions of linux are unsafe
for software raid and how? Browsing deja, RH 6.1 (2.2.12-20smp) reportedly handles
software raid without known problems (other than less than glowing documentation
reviews), and I'm setting up pgsql/apache on such a system with software raid (no
clear showstopping problems yet).

i'm not running RH6.1, but i am using a 2.2.12 kernel (compiled myself)
and like i said, no catastrophic problems. the problems, i believe,
came up with a conversation about an earlier 2.2 version of the kernel
and it may have included problems with adaptec SCSI controllers in
conjunction with software raid on SMP systems. i don't remember where i
found the references, though. i believe the adaptec 7880 driver was
fixed by 2.2.10, and there were a bunch of SMP fixes between 2.2.6 -
2.2.10, so 2.2.12 is probably as safe as anything. you never hear about
things that work, just about things that don't.

I can confirm the problems with the Adaptec controller on kernels such as 2.2.5 (RedHat
6.0) - regardless of whether or not you're running SMP. We lost data on a non-SMP box
using the Adaptec 2940U2W LVD controller with 2.2.5. Our first move was to shut off RAID
1. I sent Doug Ledford a note on the issue (as I'm sure thousands have...), and have
since upgraded to 2.2.9 and have run without problems....so far. The Adaptec controllers
appear to be the controllers to avoid.

Mike Mascari

From bouncefilter Wed Dec 15 17:56:42 1999
Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130])
by hub.org (8.9.3/8.9.3) with ESMTP id RAA29487
for <pgsql-general@postgresql.org>;
Wed, 15 Dec 1999 17:56:08 -0500 (EST)
(envelope-from prlw1@newn.cam.ac.uk)
Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk)
by henry.newn.cam.ac.uk with esmtp (Exim 2.12 #1) id 11yNLN-0005UH-00
for pgsql-general@postgresql.org; Wed, 15 Dec 1999 22:56:25 +0000
Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 2.12 #1)
id 11yNL8-0002NE-00
for pgsql-general@postgresql.org; Wed, 15 Dec 1999 22:56:10 +0000
Subject: Foreign key
To: pgsql-general@postgresql.org
Date: Wed, 15 Dec 1999 22:56:10 +0000 (GMT)
From: "Patrick Welche" <prlw1@newn.cam.ac.uk>
Reply-To: prlw1@cam.ac.uk
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E11yNL8-0002NE-00@quartz.newn.cam.ac.uk>

How do they work?

Date: Wed, 6 Oct 1999 15:25:27 +0000 (GMT)
Subject: Re: [GENERAL] Foreign Key
Message-ID: <Pine.LNX.3.96.991006152248.8877H-100000@rabies.toodarkpark.org>

I had a look at the above message which involved the refint contrib code. I
thought the equivalent might be:

CREATE TABLE employee
(
emp_id serial primary key,
emp_name varchar(30) NOT NULL
);

CREATE TABLE emp_expense
(
expense_id serial primary key,
emp_id int4 references employee match full on update cascade,
descr varchar(100) NOT NULL,
ondate date not null
);

insert into employee values (2,'Myself');
insert into emp_expense values (1,2,'Test','10-06-1999');
insert into emp_expense values (2,2,'Test #2','10-06-1999');
select * from employee;
select * from emp_expense;
update employee set emp_id=5;
select * from emp_expense; -- hope emp_id magically changes to 5

but obviously it can't be, as if I update employee, there is nothing in table
employee to say "take a look at emp_expense and update emp_id over there".
There only is something in emp_expense to say "check employee to see that
emp_id here is valid".

Anyone know of a tutorial/give me a hint?

Cheers,

Patrick

From bouncefilter Wed Dec 15 18:47:43 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA41102
for <pgsql-general@postgreSQL.org>;
Wed, 15 Dec 1999 18:47:34 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
SAA08962;
Wed, 15 Dec 1999 18:46:53 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912152346.SAA08962@candle.pha.pa.us>
Subject: Re: [GENERAL] server hardware recommendations (the archives are dead)
In-Reply-To: <Pine.BSF.4.21.9912151000280.8120-100000@thelab.hub.org> from The
Hermit Hacker at "Dec 15, 1999 10:02:51 am"
To: The Hermit Hacker <scrappy@hub.org>
Date: Wed, 15 Dec 1999 18:46:53 -0500 (EST)
CC: Adam Rossi <adam.rossi@platinumsolutions.com>,
pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 15 Dec 1999, Adam Rossi wrote:

I know this question has been asked before. I have seen it in the archives.
Unfortunately the archives are dead right now (any search will yield "no
results") and I need to make some decisions.

Can anyone give some general recommendations on hardware for a server
running Linux (RH6 or 6.1) and PostgreSQL? I estimate that there will be
about 2 GIG of data stored in the database initially, but this could grow as
high as 5 GIG in the future.

Since the db is not multithreaded, I assume that buying a dual processor
board and two processors would not be helpful to performance. Like any

actually, if you are going to have concurrent connections to the backend,
in some circumstances, PostgreSQL will handle multi-processors better then
others...process one runs on CPU0, process two runs on CPU1, etc...

I have removed multi-threaded from our comparison web page. It confused
too many people.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Wed Dec 15 18:52:43 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id SAA42024
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 18:52:01 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
SAA09027;
Wed, 15 Dec 1999 18:51:35 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912152351.SAA09027@candle.pha.pa.us>
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
In-Reply-To: <00ce01bf4713$1b47bc20$8402a8c0@sentec.demon.nl> from "J.
Roeleveld" at "Dec 15, 1999 04:43:15 pm"
To: "J. Roeleveld" <j.roeleveld@softhome.net>
Date: Wed, 15 Dec 1999 18:51:35 -0500 (EST)
CC: pgsql-list <pgsql-general@hub.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

[Charset iso-8859-1 unsupported, filtering to ASCII...]

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

What is the problem with ext2fs? Is it just performance? or is there a
serious chance for me losing data?

The only comment made was something I said about raw devices on Linux.
Someone said there is a raw device option for Linux and whether we
wanted to try using it. I said most modern filesystems can move data at
the speed of the disk, so raw devices really don't buy much. I
mentioned that ext2 is not a modern file system. The *BSD filesystems
are an example of a modern file system. This may be what Marc is
remembering.

Unfortunately, this does not relate to the user's question.

(Raw devices do have advantages because of read-ahead control and disk
flush control. However, we seem to be doing fine without these marginal
improvements, and raw devices have a host of complex problems when
implemented.)

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Thu Dec 16 07:41:51 1999
Received: from smtp.access1.net (smtp.access1.net [206.13.101.40])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA96727
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 07:41:24 -0500 (EST)
(envelope-from ccthomas@access1.net)
Received: from bsdone.SAMBA [205.253.113.21] by smtp.access1.net
(SMTPD32-5.01) id AD66804A0134; Thu, 16 Dec 1999 04:39:02 PDT
Sender: mysql
Message-ID: <385835D0.41C67EA6@access1.net>
Date: Wed, 15 Dec 1999 19:44:00 -0500
From: Courtney Thomas <ccthomas@access1.net>
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386)
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: Jeff Hoffmann <jeff@propertykey.com>,
Adam Rossi <adam.rossi@platinumsolutions.com>, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
References: <Pine.BSF.4.21.9912151122570.8120-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings !

I'd appreciate hearing more about the difference between the "good" and
the "bad" drives, so that I can avoid the latter.

Thanks,

Courtney

------------------------------------------------------------------------

The Hermit Hacker wrote:

On Wed, 15 Dec 1999, Jeff Hoffmann wrote:

my preference tends to be software raid...whatever I've ever seen as far
as hardware raid is concerned has been quite slower then software
raid...and this is with high-end servers...

i kind of question this, and here's why: i just set up a linux dual
P3/256MB with 4 software raid 5 volumes and even loading data into one
of the databases slows it to a crawl. i've been looking around because
it seems absurd that the machine should slow down so much. i haven't
really found any answers, but i have seen several places which told me
that software raid under linux _isn't_ safe for multiprocessors & no
place has told me for sure that it is.

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

appreciate it. assuming this is the case, software raid wouldn't be a
big problem if you don't do a lot of heavy writing.

Most of my RAID tests are on Solaris+Disksuite...with good drives
in the machine, my writes are something like 18MB/s to the drive, stripe'd
and mirrored...I think reads worked out to be 19MB/s...(bad drives, same
setup, same machine, same OS, were net'ng me something like 3MB/s...really
killed performance *grin*)

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

************

From bouncefilter Wed Dec 15 21:11:44 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA71797
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 21:10:47 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id WAA68193;
Wed, 15 Dec 1999 22:10:19 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 15 Dec 1999 22:10:13 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: "J. Roeleveld" <j.roeleveld@softhome.net>,
pgsql-list <pgsql-general@hub.org>
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
In-Reply-To: <199912152351.SAA09027@candle.pha.pa.us>
Message-ID: <Pine.BSF.4.21.9912152209160.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Bruce Momjian wrote:

[Charset iso-8859-1 unsupported, filtering to ASCII...]

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running with
fsync() on or off?

What is the problem with ext2fs? Is it just performance? or is there a
serious chance for me losing data?

The only comment made was something I said about raw devices on Linux.

Didn't Thomas make some comment,at one point, about not using PostgreSQL
over ext2fs...I know he does use Linux, I just figured he was using a
different fs then ext2s...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Wed Dec 15 21:59:47 1999
Received: from backup.mwk.co.nz (IDENT:root@cb.mwk.co.nz [203.98.41.195])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA78512
for <pgsql-general@hub.org>; Wed, 15 Dec 1999 21:59:13 -0500 (EST)
(envelope-from john@mwk.co.nz)
Received: from MrCreosote (mr-creosote.mwk.co.nz [192.168.1.20])
by backup.mwk.co.nz (8.9.3/8.9.3) with SMTP id PAA07363
for <pgsql-general@hub.org>; Thu, 16 Dec 1999 15:58:56 +1300
Message-ID: <002d01bf4771$78988040$1401a8c0@MWK.co.nz>
From: "John Huttley" <john@mwk.co.nz>
To: "pgsql-list" <pgsql-general@hub.org>
References: <Pine.BSF.4.21.9912152209160.651-100000@thelab.hub.org>
Subject: Re: [GENERAL] server hardware recommendations (the archives aredead)
Date: Thu, 16 Dec 1999 15:58:45 +1300
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

----- Original Message -----
From: The Hermit Hacker <scrappy@hub.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: J. Roeleveld <j.roeleveld@softhome.net>; pgsql-list
<pgsql-general@hub.org>
Sent: Thursday, 16 December 1999 15:10
Subject: Re: [GENERAL] server hardware recommendations (the archives
aredead)

On Wed, 15 Dec 1999, Bruce Momjian wrote:

[Charset iso-8859-1 unsupported, filtering to ASCII...]

What filesystem? I know (thank god) very little about Linux, but
there have been comments here by some Linux folks (Thomas, wasn't it
you?) that indicated that ext2fs sucks for this? Are you running

with

fsync() on or off?

What is the problem with ext2fs? Is it just performance? or is there a
serious chance for me losing data?

The only comment made was something I said about raw devices on Linux.

Didn't Thomas make some comment,at one point, about not using PostgreSQL
over ext2fs...I know he does use Linux, I just figured he was using a
different fs then ext2s...

Ok, to stick my oar in this.

ext2 is very fast and efficient. but it does not have journalling and is not
extent based.
Therefore it is not 'modern'. Irrelevant.

Problem with postgresql and linux relate to the fsync() system call.
On 2.2 and earlier this is surprisingly inefficient. This is related to the
structuring of the buffer-cache and VFS
layers in linux. This was rectified in 2.3.10 and later, with potential
order-of-magnitude increases in performance,
particularly with SMP systems.

Raw devices have been a contentious issue in linux. Linus's position has
been that the OS io should be so
perfect that no application layer io system can hope to surpass it. Any
situation otherwise is a flaw in linux.
It seems that this position is justified.

Generally though, switching off fsync() when starting postmaster solves
most performance problems.

If you wish to use raw io to get beyond the 32bit file limit of intel
linux.... well maybe you should be using 64bit linux.
Sparc, alpha, MIPS.

If you want a radical filesystem, checkout the reisferfs. I'm sure we would
all be interested to hear the results.

regards

John

From bouncefilter Thu Dec 16 00:10:47 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA06745
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 00:09:52 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-181-205.bng.vsnl.net.in [203.197.181.205])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id KAA09179;
Thu, 16 Dec 1999 10:40:33 +0500 (GMT+0500)
Message-ID: <002a01bf4783$a4860e40$cdb5c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: "The Hermit Hacker" <scrappy@hub.org>, <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: Fw: Spin lock error
Date: Thu, 16 Dec 1999 10:27:18 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

Thanks for your reply....

I have 2 problems
a) Too many files open which is coming from Linux,where your point is well
taken about not using Linux
b) Spinlock error. In my opinion I don't think Linux has anything to do with
it directly at least.

I did look at the bug fixes of the newer version couldn't find any directly
connected with this problem.
I know I can fix too many open files problem... but am not sure how to fix
spin lock problem.

Aside from all this.... I presume you are in some way actively contributing
to postgres development. It being a free db and shareware and all that.....
I think majority of postgres users will be on Linux and some of them using
it for Server application.
I'm very tempted to start a vote campaign to prove to you how many people
are using Postgres on Linux as a server application.

Thanks again for your help. If you have any more thots on this problem I'll
be very glad

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Date: 16 December 1999 00:03
Subject: Re: [GENERAL] Re: Fw: Spin lock error

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Oops.... I'm sorry. Don't know why I missed it out
It is postgres 6.5.1.

Okay, I don't have any love for Linux, or trust in it, so I can't be of
much help (you couldn't pay me to use Linux for a server application
*shrug*)

The other question is what is your hardware like? RAM? Drives? etc...

So, you should send this out to the list to help on that front, and
looking at the release notes for 6.5.2, nothing *appears* to jump out,
which isn't to say that something fixed below doesn't indirectly affect
you. My only/first suggestion is to upgrade to v6.5.3 and see if that
helps any, then go from there...

subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren

Sefcik)

Fixes for CASE in WHERE join clauses(Tom)
Fix BTScan abort(Tom)
Repair the check for redundant UNIQUE and PRIMARY KEY indices(Thomas)
Improve it so that it checks for multi-column constraints(Thomas)
Fix for Win32 making problem with MB enabled(Hiroki Kataoka)
Allow BSD yacc and bison to compile pl code(Bruce)
Fix SET NAMES working
int8 fixes(Thomas)
Fix vacuum's memory consumption(Hiroshi,Tatsuo)
Reduce the total memory consumption of vacuum(Tom)
Fix for timestamp(datetime)
Rule deparsing bugfixes(Tom)
Fix quoting problems in mkMakefile.tcldefs.sh.in and

mkMakefile.tkdefs.sh.in(Tom)

This is to re-use space on index pages freed by vacuum(Vadim)
document -x for pg_dump(Bruce)
Fix for unary operators in rule deparser(Tom)
Comment out FileUnlink of excess segments during mdtruncate()(Tom)
Irix linking fix from Yu Cao yucao@falcon.kla-tencor.com
Repair logic error in LIKE: should not return LIKE_ABORT
when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction

abort(Tom)

Updated version of pgaccess 0.98

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: 15 December 1999 11:11
Subject: [GENERAL] Re: Fw: Spin lock error

I seem to still be missing what version of PostgreSQL you are

..:(

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Thanks for responding.
This is a copy of my message which has all details which I could think of to
start with.
I would be glad to receive any suggesstions.

Bye,

Murali
-----Original Message-----
From: Differentiated Software Solutions Pvt. Ltd. +ADw-diffs+AEA-vsnl.com+AD4-
To: pgsql-general+AEA-postgresql.org +ADw-pgsql-general+AEA-postgresql.org+AD4AOw-

vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw-

pgsql-interfaces+AEA-postgresql.org

+ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
Date: 11 December 1999 12:33
Subject: Spin lock error
+AD4-Hi,
+AD4-
+AD4-We are getting spinlock errors under the following conditions
+AD4-
+AD4-Background :
+AD4-We have developed a high performance application using postgres

database

a
+AD4-3rd party application server).
+AD4-This application should be scalanble to server 50 requests a

second.

+AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92

and Redhat

+AD4-linux 6.0
+AD4-A request consists of one singleton select on a table of 200,000

rows on

+AD4-it's primary key, a heavy duty cursor which is a 4 table join but

which

+AD4-returns 100 rows from tables containing maximum of 250 rows, a

light sql

+AD4-opening a cursor on a table containing 500 rows, 2 inserts into

tables

which
+AD4-don't have primary key.
+AD4-
+AD4-We are connecting

to the database with autoconnect off.

+AD4-
+AD4-Problem description :
+AD4-On a light load there are no problems. As we have increased the

load

on the

+AD4-application, the requests get piled up. We keep monitoring the

requests
+AD4-getting piled up using ps ax +AHw- grep post.
+AD4-Somewhere when the requests crosses 20(ps returns more than 20
rows)....

+AD4-suddenly postmaster comes down +ACEAIQ- In the server log the

following message
is
+AD4-written out.
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.

Aborting.

+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.

Aborting.

+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.

Aborting.

+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.

Aborting.

+AD4-
+AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock.

Aborting.

+AD4-After this postmaster shutdown.
+AD4-
+AD4-One observation If we try to recreate this in another linux

machine...

+AD4-multiple postmasters run in the linux machine when the number of

requests

+AD4-become more.
+AD4-I'm also attaching a file containing 'ps' at the instance

postmaster

+AD4-crashed.
+AD4-
+AD4-Can anybody please help
+AD4-
+AD4-Thanks and regards,
+AD4-
+AD4-Murali
+AD4-
+AD4-Differentiated Software Solutions Pvt. Ltd.,
+AD4-176, Gr. Floor, 6th Main
+AD4-2nd Block RT Nagar
+AD4-Bangalore - 560 032
+AD4-India
+AD4-Ph: 91 80 3431470
+AD4-
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

************
Marc G. Fournier ICQ#7615664 IRC Nick:

Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

From bouncefilter Thu Dec 16 00:10:46 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id AAA06807
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 00:10:06 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-181-205.bng.vsnl.net.in [203.197.181.205])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id KAA16772;
Thu, 16 Dec 1999 10:40:49 +0500 (GMT+0500)
Message-ID: <002d01bf4783$b05f80c0$cdb5c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: "Robert Wagner" <rwagner@siac.com>, <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] How do I change port for the postmaster?
Date: Thu, 16 Dec 1999 10:33:39 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

Please look at man postmaster. There's a -p option where you can specify
portnumber.

While starting psql again there's a -p option.

Hope this helps.

Murali
-----Original Message-----
From: Robert Wagner <rwagner@siac.com>
To: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: 15 December 1999 23:21
Subject: [GENERAL] How do I change port for the postmaster?

I'm attempting to run two different postmasters on two different HP-UX
servers, servicing two different apps. The only commonality is that I'm on
one terminal.

The first starts up OK. When I attempt to start the postmaster on the
other server, I get the error,

FATAL: StreamServerPort: bind() failed: errno=226 Is another postmaster
already running on that port? If not, remove socket node
(/tmp/.s.PGSQL.5432) and retry./usr/local/pgsql/bin/postmaster: cannot
create UNIX stream port

Tried deleting the file, /tmp/.s.PGSQL.5432 but this had no effect.

Do I need to use a different port number, to run postmaster on two
different servers? If so, does anybody know how I can change the port
number? Is there something else, that I'm doing wrong?

I'm looking through the docs but can't find anything. I'd like to keep
postgres in the organization and avoid switching to (and learning) some big
commercial product like oracle!

Thanks!
Rob Wagner
Lowly Consultant,
SIAC

************

From bouncefilter Thu Dec 16 01:32:50 1999
Received: from rabies.toodarkpark.org (root@rabies.toodarkpark.org
[207.176.94.148]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA20145
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 01:32:41 -0500 (EST)
(envelope-from caffeine@toodarkpark.org)
Received: from localhost (caffeine@localhost)
by rabies.toodarkpark.org (8.8.8/8.8.8/Debian/GNU) with SMTP id
AAA25838; Thu, 16 Dec 1999 00:30:27 -0500
Date: Thu, 16 Dec 1999 05:30:27 +0000 (GMT)
From: Howie <caffeine@toodarkpark.org>
Reply-To: Howie <caffeine@toodarkpark.org>
To: prlw1@cam.ac.uk
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Foreign key
In-Reply-To: <E11yNL8-0002NE-00@quartz.newn.cam.ac.uk>
Message-ID: <Pine.LNX.3.96.991216050625.25654C-100000@rabies.toodarkpark.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Dec 1999, Patrick Welche wrote:

How do they work?
[SNIP]
Anyone know of a tutorial/give me a hint?

refint works by adding two triggers, one to the parent table and the other
to the child table. refint does have a bug that stems from saveplan() (
or something similar, i forget the function name ) -- if you update/delete
a cascading fk, then attempt to update/delete ANOTHER cascading fk, refint
will attempt to reuse the first query plan ( ie: delete from employee
where emp_id=2, delete from employee where emp_id=3. refint uses the plan
from '.. where emp_id=2', which causes it to fail ).

( note that $PGSQL_SRC_ROOT/contrib/spi/refint.example has detailed
documentation. )

create sequence employee_seq;
create table employee
(
emp_id int4 not null default nextval('employee_seq'),
emp_name varchar(30) not null,
primary key (emp_id)
);

create sequence emp_expense_seq;
create table emp_expense
(
expense_id int4 not null default nextval('emp_expense_seq'),
emp_id int4 not null,
descr varchar(100) not null,
ondate date not null,
primary key (expense_id)
);

-- parent trigger
create trigger employee_empid_pfk
before delete or update on employee
for each row
execute procedure check_foreign_key( '1', 'cascade', 'emp_id',
'emp_expense', 'emp_id' );

-- child trigger
create trigger emp_expense_empid_fk
before insert or update on emp_expense
for each row
execute procedure check_primary_key ('emp_id', 'employee', 'emp_id' );

-- data inserts
insert into employee (emp_id,emp_name) values(
NEXTVAL('employee_seq'), 'Myself');

insert into emp_expense (expense_id,emp_id,descr,ondate) values(
NEXTVAL('emp_expense_seq'), currval('employee_seq'), 'Test',
CURRENT_DATE);

insert into emp_expense (expense_id,emp_id,descr,ondate) values(
NEXTVAL('emp_expense_seq'), currval('employee_seq'), 'Test #2',
CURRENT_DATE);

-- selects
caffeine=> select * from employee;
emp_id|emp_name
------+--------
1|Myself
(1 row)

-- updates
caffeine=> update employee set emp_id=2;
UPDATE 1
caffeine=> select * from employee;
emp_id|emp_name
------+--------
2|Myself
(1 row)

( exit psql session due to previously mentioned bug )

-- deletes
caffeine=> delete from employee where emp_id=2;
DELETE 1
caffeine=> select * from employee;
emp_id|emp_name
------+--------
(0 rows)

caffeine=> select * from emp_expense;
expense_id|emp_id|descr|ondate
----------+------+-----+------
(0 rows)

so it works, besides that one bug. of course, pgsql 7.0 will have full
foreign key support ( including REFERENCES syntax ).

---
Howie <caffeine@toodarkpark.org> URL: http://www.toodarkpark.org
"Tell a man that there are 400 billion stars and he'll believe you.
Tell him a bench has wet paint and he has to touch it."

From bouncefilter Thu Dec 16 01:32:47 1999
Received: from rabies.toodarkpark.org (root@rabies.toodarkpark.org
[207.176.94.148]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA20154
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 01:32:44 -0500 (EST)
(envelope-from caffeine@toodarkpark.org)
Received: from localhost (caffeine@localhost)
by rabies.toodarkpark.org (8.8.8/8.8.8/Debian/GNU) with SMTP id
AAA25842; Thu, 16 Dec 1999 00:31:54 -0500
Date: Thu, 16 Dec 1999 05:31:54 +0000 (GMT)
From: Howie <caffeine@toodarkpark.org>
To: admin <admin@wtbwts.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] indices don't make much difference
In-Reply-To: <Pine.BSF.4.10.9912141756480.1350-200000@server.b0x.com>
Message-ID: <Pine.LNX.3.96.991216053128.25654D-100000@rabies.toodarkpark.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 14 Dec 1999, admin wrote:

[SNIP]
I have then run benchmarks without index, with btree and with hash, but
none seem to be faster than the other. My benchmark program is written in
c and is attached to this email. Here are the results I obtained using
time:

without index:
17.25 real 1.42 user 0.26 sys
with btree:
17.28 real 1.38 user 0.30 sys
with hash:
17.22 real 1.37 user 0.32 sys

If there is any way to make a query quicker when joining a product table
and a manufacturer table, please let me know. I've tried everything and
the results are quite fast enough.

did you VACUUM ANALYZE the table after creating the index ?

---
Howie <caffeine@toodarkpark.org> URL: http://www.toodarkpark.org
"Tell a man that there are 400 billion stars and he'll believe you.
Tell him a bench has wet paint and he has to touch it."

From bouncefilter Thu Dec 16 02:39:48 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA35690
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 02:39:35 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA92288;
Thu, 16 Dec 1999 02:07:12 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 16 Dec 1999 02:07:12 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Re: Fw: Spin lock error
In-Reply-To: <002a01bf4783$a4860e40$cdb5c5cb@nagma>
Message-ID: <Pine.BSF.4.21.9912160202470.651-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Altho its very tempting to get into an OS-war here, its not worth the time
it would take...its the reason why I sent my comments to Murali privately,
too bad he deemed that it was something to comment on publicly ;(

On Thu, 16 Dec 1999, Differentiated Software Solutions
Pvt. Ltd. wrote:

Hi,

Thanks for your reply....

I have 2 problems
a) Too many files open which is coming from Linux,where your point is well
taken about not using Linux
b) Spinlock error. In my opinion I don't think Linux has anything to do with
it directly at least.

I did look at the bug fixes of the newer version couldn't find any directly
connected with this problem.
I know I can fix too many open files problem... but am not sure how to fix
spin lock problem.

Aside from all this.... I presume you are in some way actively contributing
to postgres development. It being a free db and shareware and all that.....
I think majority of postgres users will be on Linux and some of them using
it for Server application.
I'm very tempted to start a vote campaign to prove to you how many people
are using Postgres on Linux as a server application.

Thanks again for your help. If you have any more thots on this problem I'll
be very glad

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Date: 16 December 1999 00:03
Subject: Re: [GENERAL] Re: Fw: Spin lock error

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Oops.... I'm sorry. Don't know why I missed it out
It is postgres 6.5.1.

Okay, I don't have any love for Linux, or trust in it, so I can't be of
much help (you couldn't pay me to use Linux for a server application
*shrug*)

The other question is what is your hardware like? RAM? Drives? etc...

So, you should send this out to the list to help on that front, and
looking at the release notes for 6.5.2, nothing *appears* to jump out,
which isn't to say that something fixed below doesn't indirectly affect
you. My only/first suggestion is to upgrade to v6.5.3 and see if that
helps any, then go from there...

subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren

Sefcik)

Fixes for CASE in WHERE join clauses(Tom)
Fix BTScan abort(Tom)
Repair the check for redundant UNIQUE and PRIMARY KEY indices(Thomas)
Improve it so that it checks for multi-column constraints(Thomas)
Fix for Win32 making problem with MB enabled(Hiroki Kataoka)
Allow BSD yacc and bison to compile pl code(Bruce)
Fix SET NAMES working
int8 fixes(Thomas)
Fix vacuum's memory consumption(Hiroshi,Tatsuo)
Reduce the total memory consumption of vacuum(Tom)
Fix for timestamp(datetime)
Rule deparsing bugfixes(Tom)
Fix quoting problems in mkMakefile.tcldefs.sh.in and

mkMakefile.tkdefs.sh.in(Tom)

This is to re-use space on index pages freed by vacuum(Vadim)
document -x for pg_dump(Bruce)
Fix for unary operators in rule deparser(Tom)
Comment out FileUnlink of excess segments during mdtruncate()(Tom)
Irix linking fix from Yu Cao yucao@falcon.kla-tencor.com
Repair logic error in LIKE: should not return LIKE_ABORT
when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction

abort(Tom)

Updated version of pgaccess 0.98

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: 15 December 1999 11:11
Subject: [GENERAL] Re: Fw: Spin lock error

I seem to still be missing what version of PostgreSQL you are

..:(

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Thanks for responding.
This is a copy of my message which has all details which I could think of to
start with.
I would be glad to receive any suggesstions.

Bye,

Murali
-----Original Message-----
From: Differentiated Software Solutions Pvt. Ltd. +ADw-diffs+AEA-vsnl.com+AD4-
To: pgsql-general+AEA-postgresql.org +ADw-pgsql-general+AEA-postgresql.org+AD4AOw-

vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw-

pgsql-interfaces+AEA-postgresql.org
+ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
Date: 11 December 1999 12:33
Subject: Spin lock error
+AD4-Hi,
+AD4-
+AD4-We are getting spinlock errors under the following conditions
+AD4-
+AD4-Background :
+AD4-We have developed a high performance application using postgres
database
a
+AD4-3rd party application server).
+AD4-This application should be scalanble to server 50 requests a
second.

+AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92

and Redhat
+AD4-linux 6.0
+AD4-A request consists of one singleton select on a table of 200,000
rows on

+AD4-it's primary key, a heavy duty cursor which is a 4 table join but

which

+AD4-returns 100 rows from tables containing maximum of 250 rows, a

light sql

+AD4-opening a cursor on a table containing 500 rows, 2 inserts into

tables
which
+AD4-don't have primary key.
+AD4-
+AD4-We are connecting
to the database with autoconnect off.
+AD4-
+AD4-Problem description :
+AD4-On a light load there are no problems. As we have increased the
load
on the

+AD4-application, the requests get piled up. We keep monitoring the

requests
+AD4-getting piled up using ps ax +AHw- grep post.
+AD4-Somewhere when the requests crosses 20(ps returns more than 20
rows)....

+AD4-suddenly postmaster comes down +ACEAIQ- In the server log the

following message
is
+AD4-written out.
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock.
Aborting.
+AD4-After this postmaster shutdown.
+AD4-
+AD4-One observation If we try to recreate this in another linux
machine...

+AD4-multiple postmasters run in the linux machine when the number of

requests
+AD4-become more.
+AD4-I'm also attaching a file containing 'ps' at the instance
postmaster
+AD4-crashed.
+AD4-
+AD4-Can anybody please help
+AD4-
+AD4-Thanks and regards,
+AD4-
+AD4-Murali
+AD4-
+AD4-Differentiated Software Solutions Pvt. Ltd.,
+AD4-176, Gr. Floor, 6th Main
+AD4-2nd Block RT Nagar
+AD4-Bangalore - 560 032
+AD4-India
+AD4-Ph: 91 80 3431470
+AD4-
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

************
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Thu Dec 16 01:38:47 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id BAA20883
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 01:38:18 -0500 (EST) (envelope-from diffs@vsnl.com)
Received: from nagma (PPP-190-201.bng.vsnl.net.in [203.197.190.201])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id MAA23045;
Thu, 16 Dec 1999 12:09:00 +0500 (GMT+0500)
Message-ID: <000801bf478f$feb2f660$c9bec5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: "The Hermit Hacker" <scrappy@hub.org>
Cc: <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] Re: Fw: Spin lock error
Date: Thu, 16 Dec 1999 12:06:14 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

Sorry.... I didn't notice who the message was sent to.
No OS War here please.

Murali

-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: 16 December 1999 11:34
Subject: Re: [GENERAL] Re: Fw: Spin lock error

Altho its very tempting to get into an OS-war here, its not worth the time
it would take...its the reason why I sent my comments to Murali privately,
too bad he deemed that it was something to comment on publicly ;(

On Thu, 16 Dec 1999, Differentiated Software Solutions
Pvt. Ltd. wrote:

Hi,

Thanks for your reply....

I have 2 problems
a) Too many files open which is coming from Linux,where your point is

well

taken about not using Linux
b) Spinlock error. In my opinion I don't think Linux has anything to do

with

it directly at least.

I did look at the bug fixes of the newer version couldn't find any

directly

connected with this problem.
I know I can fix too many open files problem... but am not sure how to

fix

spin lock problem.

Aside from all this.... I presume you are in some way actively

contributing

to postgres development. It being a free db and shareware and all

that.....

I think majority of postgres users will be on Linux and some of them

using

it for Server application.
I'm very tempted to start a vote campaign to prove to you how many people
are using Postgres on Linux as a server application.

Thanks again for your help. If you have any more thots on this problem

I'll

be very glad

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Date: 16 December 1999 00:03
Subject: Re: [GENERAL] Re: Fw: Spin lock error

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

Oops.... I'm sorry. Don't know why I missed it out
It is postgres 6.5.1.

Okay, I don't have any love for Linux, or trust in it, so I can't be of
much help (you couldn't pay me to use Linux for a server application
*shrug*)

The other question is what is your hardware like? RAM? Drives? etc...

So, you should send this out to the list to help on that front, and
looking at the release notes for 6.5.2, nothing *appears* to jump out,
which isn't to say that something fixed below doesn't indirectly affect
you. My only/first suggestion is to upgrade to v6.5.3 and see if that
helps any, then go from there...

subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren

Sefcik)

Fixes for CASE in WHERE join clauses(Tom)
Fix BTScan abort(Tom)
Repair the check for redundant UNIQUE and PRIMARY KEY indices(Thomas)
Improve it so that it checks for multi-column constraints(Thomas)
Fix for Win32 making problem with MB enabled(Hiroki Kataoka)
Allow BSD yacc and bison to compile pl code(Bruce)
Fix SET NAMES working
int8 fixes(Thomas)
Fix vacuum's memory consumption(Hiroshi,Tatsuo)
Reduce the total memory consumption of vacuum(Tom)
Fix for timestamp(datetime)
Rule deparsing bugfixes(Tom)
Fix quoting problems in mkMakefile.tcldefs.sh.in and

mkMakefile.tkdefs.sh.in(Tom)

This is to re-use space on index pages freed by vacuum(Vadim)
document -x for pg_dump(Bruce)
Fix for unary operators in rule deparser(Tom)
Comment out FileUnlink of excess segments during mdtruncate()(Tom)
Irix linking fix from Yu Cao yucao@falcon.kla-tencor.com
Repair logic error in LIKE: should not return LIKE_ABORT
when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction

abort(Tom)

Updated version of pgaccess 0.98

Murali
-----Original Message-----
From: The Hermit Hacker <scrappy@hub.org>
To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: 15 December 1999 11:11
Subject: [GENERAL] Re: Fw: Spin lock error

I seem to still be missing what version of PostgreSQL you are

On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd.

wrote:

Hi,

Thanks for responding.
This is a copy of my message which has all details which I could

think of to

start with.
I would be glad to receive any suggesstions.

Bye,

Murali
-----Original Message-----
From: Differentiated Software Solutions Pvt. Ltd.

+ADw-diffs+AEA-vsnl.com+AD4-

To: pgsql-general+AEA-postgresql.org

+ADw-pgsql-general+AEA-postgresql.org+AD4AOw-

vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw-

pgsql-interfaces+AEA-postgresql.org
+ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
Date: 11 December 1999 12:33
Subject: Spin lock error
+AD4-Hi,
+AD4-
+AD4-We are getting spinlock errors under the following conditions
+AD4-
+AD4-Background :
+AD4-We have developed a high performance application using

postgres

database
a
+AD4-3rd party application server).
+AD4-This application should be scalanble to server 50 requests a
second.

+AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg

0.92

and Redhat

+AD4-linux 6.0
+AD4-A request consists of one singleton select on a table of

200,000

rows on

+AD4-it's primary key, a heavy duty cursor which is a 4 table join

but

which

+AD4-returns 100 rows from tables containing maximum of 250 rows, a

light sql

+AD4-opening a cursor on a table containing 500 rows, 2 inserts

into

tables

which
+AD4-don't have primary key.
+AD4-
+AD4-We are connecting

to the database with autoconnect off.

+AD4-
+AD4-Problem description :
+AD4-On a light load there are no problems. As we have increased

the

load
on the

+AD4-application, the requests get piled up. We keep monitoring the

requests
+AD4-getting piled up using ps ax +AHw- grep post.
+AD4-Somewhere when the requests crosses 20(ps returns more than 20
rows)....

+AD4-suddenly postmaster comes down +ACEAIQ- In the server log the

following message
is
+AD4-written out.
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
Aborting.
+AD4-
+AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock.
Aborting.
+AD4-After this postmaster shutdown.
+AD4-
+AD4-One observation If we try to recreate this in another linux
machine...

+AD4-multiple postmasters run in the linux machine when the number

requests

+AD4-become more.
+AD4-I'm also attaching a file containing 'ps' at the instance

postmaster

+AD4-crashed.
+AD4-
+AD4-Can anybody please help
+AD4-
+AD4-Thanks and regards,
+AD4-
+AD4-Murali
+AD4-
+AD4-Differentiated Software Solutions Pvt. Ltd.,
+AD4-176, Gr. Floor, 6th Main
+AD4-2nd Block RT Nagar
+AD4-Bangalore - 560 032
+AD4-India
+AD4-Ph: 91 80 3431470
+AD4-

Marc G. Fournier ICQ#7615664 IRC

Nick:

Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

************

Marc G. Fournier ICQ#7615664 IRC Nick:

Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

Marc G. Fournier ICQ#7615664 IRC Nick:

Scrappy

Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:

scrappy@{freebsd|postgresql}.org

From bouncefilter Thu Dec 16 03:01:48 1999
Received: from astra.sif.it (root@astra.sif.it [131.154.110.1])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA44583;
Thu, 16 Dec 1999 03:01:36 -0500 (EST) (envelope-from pluigi@sif.it)
Received: from kaima.sif.it (IDENT:pluigi@kaima.sif.it [131.154.110.2])
by astra.sif.it (8.9.1a/8.9.0) with ESMTP id JAA09370;
Thu, 16 Dec 1999 09:33:26 +0100
Date: Thu, 16 Dec 1999 09:01:07 +0100 (CET)
From: Pierluigi Mangani <pluigi@sif.it>
To: pgsql-general@postgresql.org
cc: pgsql-novice@postgresql.org
Subject: Recompile source RH 6.1 ?
Message-ID: <Pine.LNX.4.10.9912160858150.7181-100000@kaima.sif.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I do i recompile under RH6.1 ??

I have the postgresql-6.5.3.tar.gz file.

There is a special configuration flag like --layout=redhat ?

Thanks in advance

Alex

p.s: I'm not able to download RPM due to low band internet connection
9600bps.

From bouncefilter Thu Dec 16 04:18:49 1999
Received: from mail.mik.net (root@mail.mik.net [195.122.129.49])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA57356
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 04:17:49 -0500 (EST) (envelope-from elmar@haneke.de)
Received: from localhost (dialup-212.162.15.144.frankfurt1.mik.net
[212.162.15.144])
by mail.mik.net (8.9.0/8.9.0/miknet) with ESMTP id KAA20991;
Thu, 16 Dec 1999 10:17:41 +0100
Received: from Spooler by localhost (Mercury/32 v3.01a) ID MO000089;
16 Dec 99 10:17:38 -0000
Received: from spooler by haneke.de (Mercury/32 v3.01a);
16 Dec 99 08:56:31 -0000
Received: from haneke.de (127.0.0.1) by Haneke Elektronik (Mercury/32 v3.01a)
with ESMTP ID MG000088; 16 Dec 99 08:56:27 -0000
Message-ID: <3858A93B.46453120@haneke.de>
Date: Thu, 16 Dec 1999 08:56:27 +0000
From: Elmar Haneke <elmar@haneke.de>
Organization: Haneke
X-Mailer: Mozilla 4.6 [de] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: admin <admin@wtbwts.com>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] indices don't make much difference
References: <Pine.BSF.4.10.9912141756480.1350-200000@server.b0x.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have tried creating an index for manu_base using the following commands:
create index manu_mid_idx on "manu_base" using btree ("mid" "int2_ops");
drop index manu_mid_idx
create index manu_mid_idx on "manu_base" using hash ("mid" "int2_ops");
drop index manu_mid_idx

You should also try out defining indices on prod_base.

The most efficient way for joining is an "merge join" this requires an
BTREE-index on both fields to be joined.

If EXPLAIN does not show index-usage you should do a VACUUM on both
tables to update statistics.

Elmar

From bouncefilter Thu Dec 16 06:08:55 1999
Received: from ns.prov-liege.be (ns.prov-liege.be [193.190.122.12])
by hub.org (8.9.3/8.9.3) with ESMTP id GAA78502
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 06:08:16 -0500 (EST)
(envelope-from Fabian.Frederick@prov-liege.be)
From: Fabian.Frederick@prov-liege.be
Received: by ns.prov-liege.be; (8.8.8/1.3/10May95) id MAA15489;
Thu, 16 Dec 1999 12:02:03 +0100 (GMT+0100)
Received: by mesepl.epl.prov-liege.be with Internet Mail Service (5.5.1960.3)
id <YSH1W7PA>; Thu, 16 Dec 1999 12:05:50 +0100
Message-ID: <17AB709C82E5D111ACF20000F805F4532B42D4@mesadm.epl.prov-liege.be>
To: wim.ceulemans@nice.be, pgsql-general@postgreSQL.org
Subject: RE: [GENERAL] Installation problem on Suse linux 6.3
Date: Thu, 16 Dec 1999 12:05:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id GAA78552

-----Message d'origine-----
De : Wim Ceulemans [mailto:wim.ceulemans@nice.be]
Envoy� : samedi 11 d�cembre 1999 13:53
� : pgsql-general@postgreSQL.org
Objet : [GENERAL] Installation problem on Suse linux 6.3

Hi

I can't seem to install the latest postgresql opn Suse linux
6.3 (kernel
2.2.13, glibc 2.1.2). I always get the following message when I run
./configure :

No configure required there ... simply include packages
pgdatab, pg, pgaccess.All is done _automagically_.btw, check
which gcc's fronted (GNU or EGCS), maybe one could cause
some troubles.

From bouncefilter Thu Dec 16 11:37:54 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id LAA61481
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 11:37:00 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id 8CD4B1F4C; Thu, 16 Dec 1999 11:35:48 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id 808851F43
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 11:35:48 +0000 (GMT)
Date: Thu, 16 Dec 1999 11:35:48 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: multiple key indices vs single key
Message-ID: <Pine.BSF.4.10.9912161132060.3479-100000@server.b0x.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

When using a btree index, the manual says I can specify up to 7 keys in a
single multi-column index. Is there any difference between calling a
single index with 7 keys and calling 7 indices with 1 key each, btree in
both cases? In which instances should a btree index use only a single key?
Where could I have found this information in the online manual (read
chapter 7. Indices and Keys of the User's Guide).

Thanks again,
Marc

From bouncefilter Thu Dec 16 07:04:56 1999
Received: from moon.mteege.de (ppps-nb03.MVnet.de [194.25.108.153])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA88449
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 07:04:24 -0500 (EST)
(envelope-from matthias@mteege.de)
Received: from moon.mteege.de (localhost [127.0.0.1])
by moon.mteege.de (8.8.8/8.8.8) with ESMTP id MAA13174
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 12:58:21 +0100 (MET)
(envelope-from matthias@moon.mteege.de)
Message-Id: <199912161158.MAA13174@moon.mteege.de>
From: Matthias Teege <matthias@mteege.de>
To: pgsql-general@postgresql.org
Subject: Long pg_log and pg_time
Reply-To: Matthias Teege <matthias@mteege.de>
Date: Thu, 16 Dec 1999 12:58:21 +0100
Sender: matthias@mteege.de

Moin,

we have a small postgreSQL 6.0 database running for a
while and now the pg_log and pg_time are very large.

Can I delete our rotate this files? A vacuum has no
effekt.

Many thanks
Matthias

From bouncefilter Thu Dec 16 09:55:53 1999
Received: from photon.skillbrokers.bg (root@photon.skillbrokers.bg
[195.24.42.194]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA35756
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 09:55:08 -0500 (EST) (envelope-from nmmm@nmmm.nu)
Received: from niki (proton.skillbrokers.bg [195.24.42.206])
by photon.skillbrokers.bg (8.9.0/8.9.0) with SMTP id QAA14495
for <pgsql-general@postgreSQL.org>; Thu, 16 Dec 1999 16:47:30 +0200
Message-ID: <002801bf47d5$6aebaee0$ce2a18c3@skillbrokers.bg>
From: "Nikolay Mijaylov" <nmmm@nmmm.nu>
To: "pgsql-general" <pgsql-general@postgreSQL.org>
Subject: char(xx) problem
Date: Thu, 16 Dec 1999 16:54:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Hi
we have two servers with installed Linux and PostGreSQL. They are quite
same. One is for development (Linux 2.2.9; 128 MB RAM; very overloaded with
processes), another for real HTTP serving in Internet (Linux 2.2.9; 64 MB
RAM; only http and pgsql)

In one of projects we had two tables:

create table a(
x char(2)
);

create table b(
y char(3)
);

When we try to execute SQL like this:

select * from a, b
where a.x = b.y;

one of servers selects 5-6 records (e.g. all mached records)
another selects empty table.

The database is one and same.

Why happen this?

PgSQL version 6.4, do i need to reinstall PgSQL, reinstall `db space' , or
how to fix it???

(I fix them with making chars with one and same length, and this is right
solution, but i want to have an idea why this difference exists)

--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

From bouncefilter Thu Dec 16 10:11:54 1999
Received: from [12.6.225.3] ([12.6.225.3])
by hub.org (8.9.3/8.9.3) with SMTP id KAA41838
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 10:11:44 -0500 (EST)
(envelope-from rdavis@lillysoftware.com)
Received: from lillysoftware.com by [12.6.225.3]
via smtpd (for postgresql.org [216.126.84.28]) with SMTP;
16 Dec 1999 15:11:24 UT
Received: from lillysoftware.com (BOBIBM333 [173.100.2.237]) by
ponyexpress.LillySoftware.com with SMTP (Microsoft Exchange
Internet Mail Service Version 5.5.2448.0)
id YR9L5VNF; Thu, 16 Dec 1999 10:09:37 -0500
Message-ID: <3859012C.3C6FAC7A@lillysoftware.com>
Date: Thu, 16 Dec 1999 10:11:40 -0500
From: Robert Davis <rdavis@lillysoftware.com>
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgreSQL.org
Subject: cant create index on decimal column
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi I have a problem. I cant create indexes on decimal columns.

CREATE TABLE REQUIREMENT_COST(
WORKORDER_TYPE CHAR(1) NOT NULL,
WORKORDER_BASE_ID VARCHAR(30) NOT NULL,
WORKORDER_LOT_ID VARCHAR(3) NOT NULL,
WORKORDER_SPLIT_ID VARCHAR(3) NOT NULL,
WORKORDER_SUB_ID VARCHAR(3) NOT NULL,
OPERATION_SEQ_NO SMALLINT NOT NULL,
REQ_PIECE_NO SMALLINT NOT NULL,
QTY DECIMAL(14,4) NOT NULL,
UNIT_COST DECIMAL(14,4) NOT NULL,
FIXED_COST DECIMAL(15,2) NOT NULL,
MINIMUM_COST DECIMAL(15,2),
PRIMARY
KEY(WORKORDER_TYPE,WORKORDER_BASE_ID,WORKORDER_LOT_ID,WORKORDER_SPLIT_ID,WORKORDER_SUB_ID,OPERATION_SEQ_NO,REQ_PIECE_NO,QTY
))
;
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'requirement_cost_pkey'
for table 'requirement_cost'
ERROR: Can't find a default operator class for type 1700.

If the field qty is deleted from the above primary key the create works.
I assume that there is an operator I can add to fix this?

bob

--
rdavis@lillysoftware.com
rsdavis@mediaone.net
http://people.ne.mediaone.net/rsdavis

From bouncefilter Thu Dec 16 10:27:53 1999
Received: from tango.SoftHome.net (tango.SoftHome.net [204.144.231.49])
by hub.org (8.9.3/8.9.3) with SMTP id KAA44103
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 10:27:19 -0500 (EST)
(envelope-from j.roeleveld@softhome.net)
Received: (qmail 27943 invoked by uid 417); 16 Dec 1999 15:32:20 -0000
Received: from sentec.demon.nl (HELO joost) (212.238.106.25)
by smtpb.softhome.net with SMTP; 16 Dec 1999 15:32:20 -0000
Message-ID: <004a01bf47d9$f9fac5e0$8402a8c0@sentec.demon.nl>
From: "J. Roeleveld" <j.roeleveld@softhome.net>
To: "Robert Davis" <rdavis@lillysoftware.com>, <pgsql-general@postgreSQL.org>
References: <3859012C.3C6FAC7A@lillysoftware.com>
Subject: Re: [GENERAL] cant create index on decimal column
Date: Thu, 16 Dec 1999 16:26:48 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Hi,

try to delete the comma ( , ) behind
MINIMUM_COST DECIMAL(15,2),

because the way you have it atm. is that PostgreSQL thinks you want to
create a Primary Key, without a name or datatype.

Hope this helps,

Joost Roeleveld

Hi I have a problem. I cant create indexes on decimal columns.

CREATE TABLE REQUIREMENT_COST(
WORKORDER_TYPE CHAR(1) NOT NULL,
WORKORDER_BASE_ID VARCHAR(30) NOT NULL,
WORKORDER_LOT_ID VARCHAR(3) NOT NULL,
WORKORDER_SPLIT_ID VARCHAR(3) NOT NULL,
WORKORDER_SUB_ID VARCHAR(3) NOT NULL,
OPERATION_SEQ_NO SMALLINT NOT NULL,
REQ_PIECE_NO SMALLINT NOT NULL,
QTY DECIMAL(14,4) NOT NULL,
UNIT_COST DECIMAL(14,4) NOT NULL,
FIXED_COST DECIMAL(15,2) NOT NULL,
MINIMUM_COST DECIMAL(15,2),
PRIMARY

KEY(WORKORDER_TYPE,WORKORDER_BASE_ID,WORKORDER_LOT_ID,WORKORDER_SPLIT_ID,WOR
KORDER_SUB_ID,OPERATION_SEQ_NO,REQ_PIECE_NO,QTY

))
;
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index

'requirement_cost_pkey'

for table 'requirement_cost'
ERROR: Can't find a default operator class for type 1700.

If the field qty is deleted from the above primary key the create works.
I assume that there is an operator I can add to fix this?

From bouncefilter Thu Dec 16 10:41:53 1999
Received: from mailhost.iitb.ac.in (mailhost.iitb.ac.in [202.54.44.115])
by hub.org (8.9.3/8.9.3) with SMTP id KAA49388
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 10:41:28 -0500 (EST)
(envelope-from rrahul@cse.iitb.ernet.in)
Received: (qmail 5930 invoked from network); 16 Dec 1999 16:02:08 -0000
Received: from surya.cse.iitb.ernet.in (144.16.111.14)
by mailhost.iitb.ac.in with SMTP; 16 Dec 1999 16:02:08 -0000
Received: from everest.cse.iitb.ernet.in (everest [144.16.111.4])
by surya.cse.iitb.ernet.in (8.8.8/8.8.8) with ESMTP id VAA24150
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 21:11:03 +0530 (IST)
Received: (from rrahul@localhost)
by everest.cse.iitb.ernet.in (8.9.2/8.9.2) id VAA13916
for pgsql-general@postgresql.org; Thu, 16 Dec 1999 21:10:59 +0530 (IST)
Date: Thu, 16 Dec 1999 21:10:59 +0530
From: Rahul Ravindrudu <rrahul@cse.iitb.ernet.in>
To: pgsql-general@postgresql.org
Subject: REF function
Message-ID: <19991216211059.A13792@cse.iitb.ernet.in>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i

Hi,
Is there a feature in postgres similar to the REF or DEREF function
of oracle or illustra

thanks,

R. Rahul

4th BTech,
Comp Sc and Eng,
IIT-Bombay.

From bouncefilter Thu Dec 16 10:48:54 1999
Received: from [12.6.225.3] ([12.6.225.3])
by hub.org (8.9.3/8.9.3) with SMTP id KAA50296
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 10:48:25 -0500 (EST)
(envelope-from rdavis@lillysoftware.com)
Received: from lillysoftware.com by [12.6.225.3]
via smtpd (for postgresql.org [216.126.84.28]) with SMTP;
16 Dec 1999 15:48:04 UT
Received: from lillysoftware.com (BOBIBM333 [173.100.2.237]) by
ponyexpress.LillySoftware.com with SMTP (Microsoft Exchange
Internet Mail Service Version 5.5.2448.0)
id YR9L5V4R; Thu, 16 Dec 1999 10:46:18 -0500
Message-ID: <385909C5.146770D3@lillysoftware.com>
Date: Thu, 16 Dec 1999 10:48:21 -0500
From: Robert Davis <rdavis@lillysoftware.com>
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "J. Roeleveld" <j.roeleveld@softhome.net>
CC: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] cant create index on decimal column
References: <3859012C.3C6FAC7A@lillysoftware.com>
<004a01bf47d9$f9fac5e0$8402a8c0@sentec.demon.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tried it.

Here is the error message:

CREATE TABLE REQUIREMENT_COST(
WORKORDER_TYPE CHAR(1) NOT NULL,
WORKORDER_BASE_ID VARCHAR(30) NOT NULL,
WORKORDER_LOT_ID VARCHAR(3) NOT NULL,
WORKORDER_SPLIT_ID VARCHAR(3) NOT NULL,
WORKORDER_SUB_ID VARCHAR(3) NOT NULL,
OPERATION_SEQ_NO SMALLINT NOT NULL,
REQ_PIECE_NO SMALLINT NOT NULL,
QTY DECIMAL(14,4) NOT NULL,
UNIT_COST DECIMAL(14,4) NOT NULL,
FIXED_COST DECIMAL(15,2) NOT NULL,
MINIMUM_COST DECIMAL(15,2)
PRIMARY KEY(WORKORDER_TYPE,WORKORDER_BASE_ID,WORKORDER_LOT_ID,WORKORDER_SPLIT_ID,WORKORDER_SUB_ID,OPERATION_SEQ_NO,REQ_PIECE_NO,QTY))

Error: PostgreSQL:1Error while executing the query;
ERROR: parser: parse error at or near "("

Also note that I said this can be made to work by deleting the field "qty" from the primary key clause.
Of course this is not what the application demands.

TIA
bob

"J. Roeleveld" wrote:

Hi,

try to delete the comma ( , ) behind
MINIMUM_COST DECIMAL(15,2),

because the way you have it atm. is that PostgreSQL thinks you want to
create a Primary Key, without a name or datatype.

Hope this helps,

Joost Roeleveld

Hi I have a problem. I cant create indexes on decimal columns.

CREATE TABLE REQUIREMENT_COST(
WORKORDER_TYPE CHAR(1) NOT NULL,
WORKORDER_BASE_ID VARCHAR(30) NOT NULL,
WORKORDER_LOT_ID VARCHAR(3) NOT NULL,
WORKORDER_SPLIT_ID VARCHAR(3) NOT NULL,
WORKORDER_SUB_ID VARCHAR(3) NOT NULL,
OPERATION_SEQ_NO SMALLINT NOT NULL,
REQ_PIECE_NO SMALLINT NOT NULL,
QTY DECIMAL(14,4) NOT NULL,
UNIT_COST DECIMAL(14,4) NOT NULL,
FIXED_COST DECIMAL(15,2) NOT NULL,
MINIMUM_COST DECIMAL(15,2),
PRIMARY

KEY(WORKORDER_TYPE,WORKORDER_BASE_ID,WORKORDER_LOT_ID,WORKORDER_SPLIT_ID,WOR
KORDER_SUB_ID,OPERATION_SEQ_NO,REQ_PIECE_NO,QTY

))
;
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index

'requirement_cost_pkey'

for table 'requirement_cost'
ERROR: Can't find a default operator class for type 1700.

If the field qty is deleted from the above primary key the create works.
I assume that there is an operator I can add to fix this?

--
rdavis@lillysoftware.com
rsdavis@mediaone.net
http://people.ne.mediaone.net/rsdavis

From bouncefilter Thu Dec 16 11:26:54 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id LAA57124;
Thu, 16 Dec 1999 11:26:24 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (sfcabop1.nettuno.it [193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id RAA25936;
Thu, 16 Dec 1999 17:26:22 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11yeeV-0002EF-00; Thu, 16 Dec 1999 17:25:19 +0000
Message-ID: <385912F6.88CC2E7F@sferacarta.com>
Date: Thu, 16 Dec 1999 17:27:34 +0100
From: Jose Soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: general <pgsql-general@postgresql.org>,
hackers <pgsql-hackers@postgresql.org>
Subject: \copy problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

I have a problem using \copy to load data into tables.

I have to load data into a table that contains data type fields with
NULL values.
I tried using \N but it doesn't work.
What can I do to insert a null into a data field?

To arrive this conclusion I had to try many solutions because I cannot
understand
the \copy error messages..

What about to have the row number and the error type instead of that...
hygea=> \copy movimentazioni from 4;
pqReadData() -- read() failed: errno=32
Broken pipe
PQendcopy: resetting connection
Copy failed.

Comments!

Jose'

From bouncefilter Thu Dec 16 19:27:05 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA69132
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 19:26:08 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61401 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sKMA4108622>; Fri, 17 Dec 1999 01:25:42 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11ylIZ-0001mm-00; Fri, 17 Dec 1999 01:31:07 +0100
Date: Fri, 17 Dec 1999 01:31:07 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Robert <robert@robert.cz>
cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Czech2ASCII with --mb=Latin2
In-Reply-To: <3857DC35.93AB4675@robert.cz>
Message-ID: <Pine.LNX.4.21.9912161929560.5199-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-15, Robert mentioned:

I have a database in Latin2 encoding (Czech stuff) and Latin2/Win1250
on-the-fly recoding with 'set client_encoding' works smoothly. Now, when
I set client encoding to SQL_ASCII, accented characters are converted to
(hexa) codes. Is there any (simple) way to make this recoding convert
accented characters to just the chars themselves but without accents?

I think this sort of thing has been the dream of many folks using
internationalized software, but it's not that easy. Perhaps one could
write a function that does this sort of conversion, which would have to
keep a gigantic table internally.

However, perhaps in your language it's customary to just leave off the
diacritic marks if they're not available, but in other languages such as
Swedish or German there are rules about converting those to sequences of
other letters. And if you start encoding rules of natural languages into
software, oh boy ...

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Thu Dec 16 19:28:03 1999
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
by hub.org (8.9.3/8.9.3) with ESMTP id TAA69302;
Thu, 16 Dec 1999 19:27:17 -0500 (EST)
(envelope-from peter@localhost.its.uu.se)
Received: from regulus.its.uu.se ([130.238.7.19]:61848 "EHLO
regulus.its.uu.se") by merganser.its.uu.se with ESMTP id
<S.sKMBG102476>; Fri, 17 Dec 1999 01:26:58 +0100
Received: from peter (helo=localhost)
by regulus.its.uu.se with local-esmtp (Exim 3.02 #2)
id 11ylJj-0001oQ-00; Fri, 17 Dec 1999 01:32:19 +0100
Date: Fri, 17 Dec 1999 01:32:19 +0100 (CET)
From: Peter Eisentraut <peter_e@gmx.net>
To: Jose Soares <jose@sferacarta.com>
cc: general <pgsql-general@postgresql.org>,
hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] \copy problem
In-Reply-To: <385912F6.88CC2E7F@sferacarta.com>
Message-ID: <Pine.LNX.4.21.9912162038270.5199-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: Peter Eisentraut <peter@hub.org>

On 1999-12-16, Jose Soares mentioned:

I have a problem using \copy to load data into tables.

I have to load data into a table that contains data type fields with
NULL values.
I tried using \N but it doesn't work.
What can I do to insert a null into a data field?

Works for me. I also just messed with that part in the devel sources the
other day and I don't see a reason why it wouldn't. Perhaps you could run
the COPY command instead (and make sure the file is accessible to the
server process) or simply run a COPY FROM STDIN; and enter a few things by
hand and see what you get.

the \copy error messages..

What about to have the row number and the error type instead of that...
hygea=> \copy movimentazioni from 4;
pqReadData() -- read() failed: errno=32
Broken pipe
PQendcopy: resetting connection
Copy failed.

When the backend sends garbage it cannot possibly send the error
message. The error was that the read from the connection failed. Of course
one could argue why that is ... Hmm.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

From bouncefilter Thu Dec 16 20:20:06 1999
Received: from mail.olp.net (olp.net [208.134.142.6])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA82606
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 20:19:41 -0500 (EST) (envelope-from jimhnet@olp.net)
Received: from jim ([208.137.187.8]) by mail.olp.net
(post.office MTA v2.0 0813 ID# 0-18126) with SMTP id AAD299
for <pgsql-general@postgresql.org>; Thu, 16 Dec 1999 19:16:39 -0600
From: "Jim Freeman" <jimhnet@olp.net>
To: <pgsql-general@postgresql.org>
Subject:
Date: Thu, 16 Dec 1999 19:15:52 -0600
Message-ID: <000301bf482c$42ec3340$08bb89d0@jim>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal

subscribe pgsql-general

jimhnet@olp.net

From bouncefilter Thu Dec 16 20:01:00 1999
Received: from mail.xnet.com (quake.xnet.com [198.147.221.67])
by hub.org (8.9.3/8.9.3) with ESMTP id UAA78726
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 20:00:31 -0500 (EST)
(envelope-from selkovjr@selkovjr.xnet.com)
Received: from selkovjr.xnet.com ([204.248.57.203]) by mail.xnet.com
(8.9.3+Sun/XNet-3.0R) with ESMTP id TAA11338;
Thu, 16 Dec 1999 19:00:20 -0600 (CST)
Message-Id: <199912170100.TAA11338@mail.xnet.com>
To: "Nikolay Mijaylov" <nmmm@nmmm.nu>
From: "Gene Selkov, Jr." <selkovjr@mcs.anl.gov>
cc: "pgsql-general" <pgsql-general@postgreSQL.org>
Subject: Re: [GENERAL] char(xx) problem
In-Reply-To: Your message of "Thu, 16 Dec 1999 16:54:07 +0200."
<002801bf47d5$6aebaee0$ce2a18c3@skillbrokers.bg>
Date: Thu, 16 Dec 1999 20:02:45 -0600
Sender: selkovjr@selkovjr.xnet.com

Hi
we have two servers with installed Linux and PostGreSQL. They are quite
same. One is for development (Linux 2.2.9; 128 MB RAM; very overloaded with
processes), another for real HTTP serving in Internet (Linux 2.2.9; 64 MB
RAM; only http and pgsql)

In one of projects we had two tables:

create table a(
x char(2)
);

create table b(
y char(3)
);

When we try to execute SQL like this:

select * from a, b
where a.x = b.y;

one of servers selects 5-6 records (e.g. all mached records)
another selects empty table.

The database is one and same.

What are the versions of pg?

I have similar experience. I used to routinely join on char() and
text, or on char() attributes of different length. Can't do that
anymore. Not sure when the change occurred -- some time between 6.3
and 6.5. The problem is I beleive related to blank padding: it formerly
showed through only in selects, now it affects comparison as well.

I'm just wondering: are there any alternatives to blank padding? Why
is it done in the first place?

--Gene

From bouncefilter Thu Dec 16 21:12:01 1999
Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA93553
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 21:11:44 -0500 (EST)
(envelope-from huang@fcs.mt.nec.co.jp)
Received: from mailsv4.nec.co.jp ([192.168.1.93])
by TYO202.gate.nec.co.jp (8.9.3/3.7W99110115) with ESMTP id LAA03587
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 11:11:42 +0900 (JST)
Received: from steffy.fcs.mt.nec.co.jp (steffy.fcs.mt.nec.co.jp
[133.201.61.1]) by mailsv4.nec.co.jp (8.9.3/3.7W-MAILSV4-NEC)
with ESMTP id LAA26391 for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 11:11:41 +0900 (JST)
Received: from fcs.mt.nec.co.jp ([133.201.61.76] (may be forged)) by
steffy.fcs.mt.nec.co.jp (8.8.6/3.5Wpl7) with ESMTP id CAA03465
for <pgsql-general@postgresql.org.>; Fri, 17 Dec 1999 02:05:16 GMT
Message-ID: <38599BF6.9C8F25C4@fcs.mt.nec.co.jp>
Date: Fri, 17 Dec 1999 11:12:06 +0900
From: Huang <huang@fcs.mt.nec.co.jp>
X-Mailer: Mozilla 4.7 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Is PostgreSQL a trademark?
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Hi,
Can someone tell me if PostgreSQL is a trademark?
I want to do something for PostgreSQL which is reg an domain
postgreSQL.??.?? and use it to offer
PostgreSQL related service. Is it need some law consideration?

(Sorry if such a question is not include in this list)

Thanks.

-------
huang.

From bouncefilter Thu Dec 16 21:23:02 1999
Received: from TYO203.gate.nec.co.jp (TYO203.gate.nec.co.jp [202.32.8.211])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA07055
for <pgsql-general@postgresql.org>;
Thu, 16 Dec 1999 21:22:47 -0500 (EST)
(envelope-from huang@fcs.mt.nec.co.jp)
Received: from mailsv2.nec.co.jp ([192.168.1.91])
by TYO203.gate.nec.co.jp (8.9.3/3.7W99110115) with ESMTP id LAA04470
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 11:22:45 +0900 (JST)
Received: from mailsv.nec.co.jp (mailsv.nec.co.jp [10.7.68.90]) by
mailsv2.nec.co.jp (8.9.3/3.7W-MAILSV2-NEC) with ESMTP
id LAA10199 for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 11:22:43 +0900 (JST)
Received: from steffy.fcs.mt.nec.co.jp (steffy.fcs.mt.nec.co.jp
[133.201.61.1]) by mailsv.nec.co.jp (8.9.3/3.7W-MAILSV-NEC)
with ESMTP id LAA16617 for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 11:21:27 +0900 (JST)
Received: from fcs.mt.nec.co.jp ([133.201.61.76] (may be forged)) by
steffy.fcs.mt.nec.co.jp (8.8.6/3.5Wpl7) with ESMTP id CAA03725
for <pgsql-general@postgresql.org.>; Fri, 17 Dec 1999 02:15:02 GMT
Message-ID: <38599E3E.B02E7143@fcs.mt.nec.co.jp>
Date: Fri, 17 Dec 1999 11:21:51 +0900
From: Huang <huang@fcs.mt.nec.co.jp>
X-Mailer: Mozilla 4.7 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Is PostgreSQL a trademark?
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

(Sorry if such a question is not include in this list)

Thanks.

-------
huang.

From bouncefilter Thu Dec 16 21:54:01 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id VAA13213
for <pgsql-general@postgreSQL.org>;
Thu, 16 Dec 1999 21:53:08 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id WAA09445;
Thu, 16 Dec 1999 22:53:21 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 16 Dec 1999 22:53:21 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Huang <huang@fcs.mt.nec.co.jp>
cc: pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] Is PostgreSQL a trademark?
In-Reply-To: <38599E3E.B02E7143@fcs.mt.nec.co.jp>
Message-ID: <Pine.BSF.4.21.9912162252360.4452-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 17 Dec 1999, Huang wrote:

Hi,
Can someone tell me if PostgreSQL is a trademark?
I want to do something for PostgreSQL which is reg an domain
postgreSQL.??.?? and use it to offer
PostgreSQL related service. Is it need some law consideration?

The name PostgreSQL is trademark'd in Canada, yes...it was done as part of
the Incorporation of PostgreSQL...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Thu Dec 16 22:07:01 1999
Received: from ns2.cybervale.com ([207.241.176.10])
by hub.org (8.9.3/8.9.3) with ESMTP id WAA17515
for <pgsql-general@hub.org>; Thu, 16 Dec 1999 22:06:41 -0500 (EST)
(envelope-from caspanis@cybervale.com)
Received: from cybervale.com (crandle@[207.241.176.197])
by ns2.cybervale.com (8.9.3/8.9.3) with ESMTP id WAA13455;
Thu, 16 Dec 1999 22:19:11 -0500
Sender: crandle@ns2.cybervale.com
Message-ID: <3859A7E9.DD5925F6@cybervale.com>
Date: Thu, 16 Dec 1999 22:03:05 -0500
From: Charles Alexander Randle <caspanis@cybervale.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Alliban <MarkA@idnltd.com>
CC: pgsql-general@hub.org
Subject: SCO Openserver & pg_hba.conf
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mark,

I saw your posting regarding the problem and if you've already obtained
a solution for this problem you can ignore this message .

There is a problem with Unix domain sockets and the pg_hba.conf file on
SCO openserver unix . The only way I've been able to access the data on
SCO is via internat domain sockets.
1)To enable access this way , you have to restart the 'postmaster'
process with the '-i' option to enable this
access method .
2) Any application which needs access to the database would need to
connect via that same method : Hence if
you are connecting with 'psql' on your machine , you would do
something like 'psql -h localhost -d
<dbname>' (I think that the -d flag is optional , you just need to
specify the database name .)
3) This applies to any application needing a connection (createdb , etc.
etc.)

Good Luck ,
Charles.

From bouncefilter Fri Dec 17 02:22:06 1999
Received: from photon.skillbrokers.bg (root@photon.skillbrokers.bg
[195.24.42.194]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA66406
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 02:22:00 -0500 (EST) (envelope-from nmmm@nmmm.nu)
Received: from niki (proton.skillbrokers.bg [195.24.42.206])
by photon.skillbrokers.bg (8.9.0/8.9.0) with SMTP id JAA21786;
Fri, 17 Dec 1999 09:14:13 +0200
Message-ID: <002501bf485f$3f5fd000$ce2a18c3@skillbrokers.bg>
From: "Nikolay Mijaylov" <nmmm@nmmm.nu>
To: "Gene Selkov, Jr." <selkovjr@mcs.anl.gov>
Cc: "pgsql-general" <pgsql-general@postgreSQL.org>
References: <199912170100.TAA11338@mail.xnet.com>
Subject: Re: [GENERAL] char(xx) problem
Date: Fri, 17 Dec 1999 09:19:54 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Sorry PG is 6.4.2
--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <nmmm@nmmm.nu>

----- Original Message -----
From: Gene Selkov, Jr. <selkovjr@mcs.anl.gov>
To: Nikolay Mijaylov <nmmm@nmmm.nu>
Cc: pgsql-general <pgsql-general@postgreSQL.org>
Sent: ��, �� 17, 1999 04:02
Subject: Re: [GENERAL] char(xx) problem

Hi
we have two servers with installed Linux and PostGreSQL. They are quite
same. One is for development (Linux 2.2.9; 128 MB RAM; very overloaded

with

processes), another for real HTTP serving in Internet (Linux 2.2.9; 64

RAM; only http and pgsql)

In one of projects we had two tables:

create table a(
x char(2)
);

create table b(
y char(3)
);

When we try to execute SQL like this:

select * from a, b
where a.x = b.y;

one of servers selects 5-6 records (e.g. all mached records)
another selects empty table.

The database is one and same.

What are the versions of pg?

I have similar experience. I used to routinely join on char() and
text, or on char() attributes of different length. Can't do that
anymore. Not sure when the change occurred -- some time between 6.3
and 6.5. The problem is I beleive related to blank padding: it formerly
showed through only in selects, now it affects comparison as well.

I'm just wondering: are there any alternatives to blank padding? Why
is it done in the first place?

--Gene

************

From bouncefilter Fri Dec 17 02:58:05 1999
Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
by hub.org (8.9.3/8.9.3) with ESMTP id CAA72180
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 02:57:32 -0500 (EST)
(envelope-from ELOEHR@austin.rr.com)
Received: from austin.rr.com ([24.27.3.138]) by Mail.austin.rr.com with
Microsoft SMTPSVC(5.5.1877.197.19); Fri, 17 Dec 1999 01:49:12 -0600
Sender: ed
Message-ID: <3859ED29.1267B897@austin.rr.com>
Date: Fri, 17 Dec 1999 01:58:33 -0600
From: Ed Loehr <ELOEHR@austin.rr.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: [GENERAL] How to get timestamped pgsql logging?
References: <38525CB7.5A0DE3A@robert.cz>
<m2iu25eyiw.fsf@chameleon.localdomain>
<38534F22.57EA6E8A@robert.cz>
<m2wvqjpg4n.fsf@chameleon.localdomain>
<3855477C.11EF5AAF@robert.cz> <38554BE5.66A09278@wgcr.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

After following some hints from Bruce Momjian and the pgsql documentation,
I'm still missing something on how to get timestamped backend logging from
pgsql...any help is appreciated...

After running ./configure, I modifed ...src/include/config.h to uncomment
the two lines...

#define ELOG_TIMESTAMPS
#define USE_SYSLOG

Then I ran make, etc, created the file $PGDATA/pg_options...

% cat $PGDATA/pg_options
verbose=2
query
syslog=2

And restarted the server...and still no timestamps.

I verified most everything syslog-wise (configured in /etc/syslog.conf) is
being sent to /var/log/messages...

Anyone notice what am I missing?

Cheers,
Ed Loehr

From bouncefilter Fri Dec 17 03:44:05 1999
Received: from webmail05.sohu.com ([202.106.185.57])
by hub.org (8.9.3/8.9.3) with ESMTP id DAA85820
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 03:43:45 -0500 (EST)
(envelope-from jesselee@sohu.com)
From: jesselee@sohu.com
Received: from mail pickup service by webmail05.sohu.com with Microsoft
SMTPSVC; Fri, 17 Dec 1999 16:35:20 +0800
To: <pgsql-general@postgresql.org>
Subject: How to create a new PL language in postgres
Date: Fri, 17 Dec 1999 16:35:19 +0800
Message-ID: <8eef01bf4869$a6e25540$39b96aca@sohu.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
X-Mailer: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id DAA85830

Dear Sir,

I want to use plpgsql as a program language in my postgres, and install it reference to the document in postgres.

I do the following:

1. Login postgres database
2. Enter the script:
create function plpgsql_call_handler() returns OPAQUE as
' /usr/lib/plpgsql.so' language 'C';

create trusted procedural language 'plpgsql'
handler plpgsql_call_handler
lancompiler 'PL/pgsql';

3.create a function like this:
create function test3(int4) returns int4 as
' begin
insert into customer values($1, 'China','Jesse');
return 1;
end;
' language 'plpgsql;

and all the operation above return create and I use the following command to test the funciton:
select test3(1) as answer

but the system returns the error:

ERROR: fmgr_info: Cache lookup for language %d failed 21153

Can you tell me what have happen and how can I use plpgsql in postgres?

My Mailaddress: JesseLee@soho.com

Thanks & Regards,
Jesse

From bouncefilter Fri Dec 17 04:46:06 1999
Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
by hub.org (8.9.3/8.9.3) with ESMTP id EAA97172;
Fri, 17 Dec 1999 04:45:37 -0500 (EST)
(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (sfcabop1.nettuno.it [193.207.10.213])
by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id KAA09117;
Fri, 17 Dec 1999 10:45:33 +0100 (MET)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
id 11yulW-00064C-00; Fri, 17 Dec 1999 10:37:38 +0000
Message-ID: <385A04E5.C6169AC5@sferacarta.com>
Date: Fri, 17 Dec 1999 10:39:49 +0100
From: Jose Soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: general <pgsql-general@postgresql.org>,
hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] \copy problem
References: <Pine.LNX.4.21.9912162038270.5199-100000@localhost.localdomain>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Sorry Peter, I don't say you any thing, I'm using psql on win95.

1. I see psql for Linux requires \N only for data fields with null
values other fields (char,int,etc)
doesn't need \N. Why ?
2. psql for M$Windows95 has a different behavior. For example I can't
insert date fields even using \N

I tried to load a file by changing every NULL value of date fields with
\N and it works
on Linux psql, but Win95 psql shows me the following message:
pqReadData() -- read() failed: errno=0
No error
PQendcopy: resetting connection
Copy failed.

Any ideas ?

Peter Eisentraut wrote:

On 1999-12-16, Jose Soares mentioned:

I have a problem using \copy to load data into tables.

I have to load data into a table that contains data type fields with
NULL values.
I tried using \N but it doesn't work.
What can I do to insert a null into a data field?

Works for me. I also just messed with that part in the devel sources the
other day and I don't see a reason why it wouldn't. Perhaps you could run
the COPY command instead (and make sure the file is accessible to the
server process) or simply run a COPY FROM STDIN; and enter a few things by
hand and see what you get.

the \copy error messages..

What about to have the row number and the error type instead of that...
hygea=> \copy movimentazioni from 4;
pqReadData() -- read() failed: errno=32
Broken pipe
PQendcopy: resetting connection
Copy failed.

When the backend sends garbage it cannot possibly send the error
message. The error was that the read from the connection failed. Of course
one could argue why that is ... Hmm.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

************

From bouncefilter Fri Dec 17 04:53:06 1999
Received: from web3106.mail.yahoo.com (web3106.mail.yahoo.com
[204.71.202.191])
by hub.org (8.9.3/8.9.3) with SMTP id EAA97924
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 04:52:31 -0500 (EST)
(envelope-from jesselee770112@yahoo.com)
Message-ID: <19991217095201.11596.qmail@web3106.mail.yahoo.com>
Received: from [202.104.71.119] by web3106.mail.yahoo.com;
Fri, 17 Dec 1999 01:52:01 PST
Date: Fri, 17 Dec 1999 01:52:01 -0800 (PST)
From: Jesse Lee <jesselee770112@yahoo.com>
Subject: Create language PL/pgSQL failed
To: pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I want to using pl/pgsql in postgres, but failed to
create the language.

When I create a function written by pl/pgsql, met the
following error:

ERROR: fmgr_info: function 21696: cache lookup failed

What happen to the system and how can I correctly
configure the language?

Jesse
MailAddress:JesseLee770112@Yahoo.com

__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

From bouncefilter Fri Dec 17 05:15:06 1999
Received: from vpcit.ru (qmailr@dialup.vpcit.ru [195.38.52.246])
by hub.org (8.9.3/8.9.3) with SMTP id FAA04756
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 05:14:13 -0500 (EST) (envelope-from yura@vpcit.ru)
Received: (qmail 13820 invoked from network); 17 Dec 1999 10:14:03 -0000
Received: from gercon.vpcit.ru (195.38.52.226)
by dialup.vpcit.ru with SMTP; 17 Dec 1999 10:14:03 -0000
Date: Fri, 17 Dec 1999 15:14:17 +0500
From: yura <yura@vpcit.ru>
X-Mailer: The Bat! (v1.36) S/N F29DEE5D / Educational
Reply-To: yura <yura@vpcit.ru>
Organization: Gercon
X-Priority: 3 (Normal)
Message-ID: <18634.991217@vpcit.ru>
To: pgsql-general@postgreSQL.org
Subject: Redefine operator = for text
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello All,

Is it possible to change the behavior of operator "=" for text? I
wolud like to redefine this operator in order to it compare strings
without checking of letter case.
I tried the following:

create function TextEqual(text, text)
returns bool
as '
begin
if texteq(upper($1), upper($2)) then
return TRUE;
else
return FALSE;
end if;
end;
'
language 'plpgsql';

drop operator = (text, text);
create operator = (
leftarg=text,
rightarg=text,
procedure=TextEqual,
commutator='=',
negator='<>',
restrict=eqsel,
join=eqjoinsel
);

This works, but after that many queries return error "unknown operator
98".

--
Best regards,
Yury mailto:yura@vpcit.ru

From bouncefilter Fri Dec 17 07:02:08 1999
Received: from relay5.ftech.net (littleblue.ftech.net [195.200.12.27])
by hub.org (8.9.3/8.9.3) with ESMTP id HAA25672
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 07:01:35 -0500 (EST)
(envelope-from MarkA@idnltd.com)
Received: from ibm9.ftech.net ([212.32.16.79] helo=idnltd.com)
by relay5.ftech.net with smtp (Exim 3.12.ftech-p6 #1)
id 11yw9w-0004er-00; Fri, 17 Dec 1999 12:06:56 +0000
Message-ID: <003401bf4886$746cad00$c80110ac@centauri>
From: "Mark Alliban" <MarkA@idnltd.com>
To: "Charles Alexander Randle" <caspanis@cybervale.com>
Cc: <pgsql-general@hub.org>
Subject: Re: SCO Openserver & pg_hba.conf
Date: Fri, 17 Dec 1999 12:01:28 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2110.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,
Thanks for the suggestion! I've been trying to get it to work for ages and
using the -h option was the workaround I was looking for.

However I still have a small problem, in that when I do "CREATE UNIQUE INDEX
AcT_AcNo ON AccountTable (AccountNo);" where AccountNo is NUMERIC or DECIMAL
I get "ERROR: Can't find a default operator class for type 1700.". If
AccountNo is INT2 or INT8 then there is no problem. Is this another problem
with SCO OpenServer?

To get PostgreSQL to compile, I had to edit Makefile.port after doing
configure, and remove the first 2 lines containing CCFLAGS and LDFLAGS.

Thanks,
Mark.

From bouncefilter Fri Dec 17 08:23:08 1999
Received: from corvette.mascari.com (dhcp26131045.columbus.rr.com
[24.26.131.45]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA38544
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 08:23:07 -0500 (EST)
(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
by corvette.mascari.com (8.8.7/8.8.7) with ESMTP id IAA07494;
Fri, 17 Dec 1999 08:21:25 -0500
Message-ID: <385A38E2.62F43F2A@mascari.com>
Date: Fri, 17 Dec 1999 08:21:39 -0500
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Alliban <MarkA@idnltd.com>
CC: Charles Alexander Randle <caspanis@cybervale.com>, pgsql-general@hub.org
Subject: Re: [GENERAL] Re: SCO Openserver & pg_hba.conf
References: <003401bf4886$746cad00$c80110ac@centauri>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mark Alliban wrote:

Hi,
Thanks for the suggestion! I've been trying to get it to work for ages and
using the -h option was the workaround I was looking for.

However I still have a small problem, in that when I do "CREATE UNIQUE INDEX
AcT_AcNo ON AccountTable (AccountNo);" where AccountNo is NUMERIC or DECIMAL
I get "ERROR: Can't find a default operator class for type 1700.". If
AccountNo is INT2 or INT8 then there is no problem. Is this another problem
with SCO OpenServer?

To get PostgreSQL to compile, I had to edit Makefile.port after doing
configure, and remove the first 2 lines containing CCFLAGS and LDFLAGS.

Thanks,
Mark.

I believe this is fixed in current sources, since the TODO
shows a '-' in front of any TODO item which is believed to
be addressed in current. To see if it has been fixed, you
could always try the latest snapshot at ftp.postgresql.org.
Here's the TODO entry:

-Add index on NUMERIC/DECIMAL type(Jan)

Hope that helps,

Mike Mascari

From bouncefilter Fri Dec 17 08:36:08 1999
Received: from Cantor.suse.de (Cantor.suse.de [194.112.123.193])
by hub.org (8.9.3/8.9.3) with ESMTP id IAA42675
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 08:35:15 -0500 (EST) (envelope-from ke@suse.de)
Received: from Galois.suse.de (Galois.suse.de [194.112.123.130])
by Cantor.suse.de (Postfix) with ESMTP
id 201E31E13E; Fri, 17 Dec 1999 14:34:44 +0100 (MET)
Received: from Wotan.suse.de (Wotan.suse.de [10.10.0.1])
by Galois.suse.de (Postfix) with ESMTP
id 78D1567B7; Fri, 17 Dec 1999 14:34:43 +0100 (MET)
Received: from Frechet.suse.de (Frechet.suse.de [10.10.0.123])
by Wotan.suse.de (Postfix) with ESMTP
id 3E2E77F8B; Fri, 17 Dec 1999 14:34:43 +0100 (MET)
Received: (from ke@localhost)
by Frechet.suse.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id OAA30058;
Fri, 17 Dec 1999 14:34:45 +0100
Sender: ke@suse.de
To: Wim Ceulemans <wim.ceulemans@nice.be>
Cc: pgsql-general@postgreSQL.org
Subject: Re: Installation problem on Suse linux 6.3
References: <3852493A.5484BB07@nice.be> <shwvqj9cky.fsf@Frechet.suse.de>
<38577B03.A612ECAD@nice.be>
From: Karl Eichwalder <ke@suse.de>
Date: 17 Dec 1999 14:34:44 +0100
In-Reply-To: Wim Ceulemans's message of "Wed, 15 Dec 1999 12:26:59 +0100"
Message-ID: <shhfhh1yiz.fsf@Frechet.suse.de>
Lines: 20
User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Wim Ceulemans <wim.ceulemans@nice.be> writes:

Okay, maybe some other parts are still to be installed; e.g., you'll
need egcs, of course. Please, have a look at config.log.

| I can't find a libgpp under /lib or /usr/lib, I do find a libg++
| library.
| Is this normal, or has the library another name?

You'll find he library in "gppshare".

--
work : ke@suse.de
Karl Eichwalder home : ke@gnu.franken.de

From bouncefilter Fri Dec 17 09:19:09 1999
Received: from giasbg01.vsnl.net.in (giasbg01.vsnl.net.in [202.54.12.17])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA49367
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 09:18:59 -0500 (EST)
(envelope-from diffs@vsnl.com)
Received: from nagma (PPP-181-75.bng.vsnl.net.in [203.197.181.75])
by giasbg01.vsnl.net.in (8.9.3/8.9.3) with SMTP id TAA24890
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 19:49:56 +0500 (GMT+0500)
Message-ID: <001801bf4899$7d8c3500$4bb5c5cb@nagma>
From: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
To: <pgsql-general@hub.org>
Subject: Vacuum clarifications/issues
Date: Fri, 17 Dec 1999 19:41:42 +0530
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi,

I'm vacuming a table containing 300,000 rows with a single index.
Currently it is taking 1.5 hours to complete. It was faster earlier.
I have dropped and recreated and reloaded this table. THis does not seem to
help.

Further... vacuum returns several messages.... like crashed... unused...
moved etc.,
Some of them have numbers.
Can anybody tell me what I should do with these and how to interpret them
etc.,

Thanks,

Murali

Differentiated Software Solutions Pvt. Ltd.,
176, Gr. Floor, 6th Main
2nd Block RT Nagar
Bangalore - 560 032
India
Ph: 91 80 3431470

From bouncefilter Fri Dec 17 09:49:10 1999
Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191])
by hub.org (8.9.3/8.9.3) with ESMTP id JAA59773
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 09:48:39 -0500 (EST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA41389;
Fri, 17 Dec 1999 10:45:34 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Fri, 17 Dec 1999 10:45:34 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Differentiated Software Solutions Pvt. Ltd." <diffs@vsnl.com>
cc: pgsql-general@hub.org
Subject: Re: [GENERAL] Vacuum clarifications/issues
In-Reply-To: <001801bf4899$7d8c3500$4bb5c5cb@nagma>
Message-ID: <Pine.BSF.4.21.9912171045260.4452-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 17 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:

Hi,

I'm vacuming a table containing 300,000 rows with a single index.
Currently it is taking 1.5 hours to complete. It was faster earlier.
I have dropped and recreated and reloaded this table. THis does not seem to
help.

Further... vacuum returns several messages.... like crashed... unused...
moved etc.,
Some of them have numbers.
Can anybody tell me what I should do with these and how to interpret them
etc.,

Post them? :)

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

From bouncefilter Fri Dec 17 10:04:10 1999
Received: from ns2.cybervale.com ([207.241.176.10])
by hub.org (8.9.3/8.9.3) with ESMTP id KAA65708
for <pgsql-general@hub.org>; Fri, 17 Dec 1999 10:03:22 -0500 (EST)
(envelope-from caspanis@cybervale.com)
Received: from cybervale.com (crandle@[207.241.176.100])
by ns2.cybervale.com (8.9.3/8.9.3) with ESMTP id KAA26051;
Fri, 17 Dec 1999 10:16:18 -0500
Sender: crandle@ns2.cybervale.com
Message-ID: <385A4FFD.1E1314E8@cybervale.com>
Date: Fri, 17 Dec 1999 10:00:13 -0500
From: Charles Alexander Randle <caspanis@cybervale.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Alliban <MarkA@idnltd.com>
CC: pgsql-general@hub.org
Subject: Re: SCO Openserver & pg_hba.conf
References: <003401bf4886$746cad00$c80110ac@centauri>
Content-Type: multipart/mixed; boundary="------------24D6C420764E69FB0909D014"

This is a multi-part message in MIME format.
--------------24D6C420764E69FB0909D014
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mark,

I think your best bet for a solution to the index problem would be
posting a question to the sql mailing list , because I don't have a
solution to that .

1) The current postgresql source tree (Version 6.5.3) doesn't recognize
support for shared libraries under
SCO Openserver 5.0.5 . To get all the shared libraries compiled , I
had to modify Makefile.shlib to include
support for sco . I would be interested to know if there's another
way to get this working .
If oyu haven't got it working , I've attached my version of
'Makefile.shlib' you can take a look at it.
If you're going to try this then I think you'll have to remove the
CFLAGS component in 'Makefile.port'
because the '-dy ' does something completely different on the
SCO native C compiler as against the
GNU C compiler . but the LDFLAGS component canremain the same (
LDFLAGS += -Wl,-Bexport ).

2) Were you able to get libpq++ to compile successfully ? I could only
get it to work by using
GNU c/c++ compilation system (ersion 2.95.2). and I also had to use
this on the command line to make :
make all COPT="-g -DSTDC_HEADERS" . You also have to make changes
to the 'templates/sco' file to
make provision for the new compiler & compiler tools that you're
using (namely gcc,flex,bison etc. etc.).

Best Regards,
Charles.

--------------24D6C420764E69FB0909D014
Content-Type: text/plain; charset=us-ascii;
name="Makefile.shlib"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="Makefile.shlib"

#-------------------------------------------------------------------------
#
# Makefile.shlib
# Common rules for building shared libraries
#
# Copyright (c) 1998, Regents of the University of California
#
# IDENTIFICATION
# $Header: /usr/local/cvsroot/pgsql/src/Makefile.shlib,v 1.12.2.3 1999/07/30 04:13:44 scrappy Exp $
#
#-------------------------------------------------------------------------

# This file should be included by any Postgres module Makefile that wants
# to build a shared library (if possible for the current platform).
# A static library is also built from the same object files.
# RESTRICTION: only one library can be built per makefile...

# Before including this file, the module Makefile must define these variables:
# NAME Name of library to build (no suffix nor "lib" prefix)
# SO_MAJOR_VERSION Major version number to use for shared library
# SO_MINOR_VERSION Minor version number to use for shared library
# OBJS List of object files to include in library
# SHLIB_LINK If shared library relies on other libraries, additional
# stuff to put in its link command
# (If you want a patchlevel, include it in SO_MINOR_VERSION, eg, "6.2".)
#
# The module Makefile must also include $(SRCDIR)/Makefile.global before
# including this file (Makefile.global sets PORTNAME and other needed symbols).
#
# The first rule in this file is a rule for "all", which causes both the
# static and shared libraries to be built (as well as all the object files).
# If you have other files that need to be made before building object files
# and libraries, put another rule for "all" before you include this file.
#
# Your install rule should look like
#
# install: install-headers install-lib $(install-shlib-dep)
#
# where install-headers is only needed if you have header files to install
# (and, of course, it has to be provided by your makefile). The rules
# install-lib and install-shlib are provided by this makefile --- they
# automatically install the plain and shared libraries into $(LIBDIR).
# install-shlib-dep is a variable that expands to install-shlib if the
# shared library needs to be installed, empty if not.
#
# Got that? Look at src/interfaces/libpq/Makefile.in for an example.

# shlib and install-shlib-dep default to empty, and stay that way if we're
# on a platform where we don't know how to build a shared library.
shlib :=
install-shlib-dep :=

# For each platform we support shlibs on, set shlib and install-shlib-dep,
# and update flags as needed to build a shared lib. Note we depend on
# Makefile.global (or really Makefile.port) to supply DLSUFFIX and other
# symbols.

# Try to keep the sections in some kind of order, folks...

ifeq ($(PORTNAME), aix)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX)
SHLIB_LINK += -lc
endif

ifeq ($(PORTNAME), bsd)
ifdef BSD_SHLIB
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
ifdef ELF_SYSTEM
LDFLAGS_SL := -x -Bshareable -soname $(shlib)
else
LDFLAGS_SL := -x -Bshareable -Bforcearchive
endif
CFLAGS += $(CFLAGS_SL)
endif
endif

ifeq ($(PORTNAME), bsdi)
ifdef BSD_SHLIB
ifeq ($(DLSUFFIX), .so)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL += -shared
CFLAGS += $(CFLAGS_SL)
endif
ifeq ($(DLSUFFIX), .o)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LD := shlicc
LDFLAGS_SL += -O -r
CFLAGS += $(CFLAGS_SL)
endif
endif
endif

ifeq ($(PORTNAME), freebsd)
ifdef BSD_SHLIB
install-shlib-dep := install-shlib
ifdef ELF_SYSTEM
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION)
LDFLAGS_SL := -x -shared -soname $(shlib)
else
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -x -Bshareable -Bforcearchive
endif
CFLAGS += $(CFLAGS_SL)
endif
endif

ifeq ($(PORTNAME), hpux)
install-shlib-dep := install-shlib
# HPUX doesn't believe in version numbers for shlibs
shlib := lib$(NAME)$(DLSUFFIX)
LDFLAGS_SL := -b
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), irix5)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -shared
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), linux)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -Bdynamic -shared -soname $(shlib)
LDFLAGS_ODBC := -Bsymbolic -lc -lm
SHLIB_LINK += -lc
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), sco)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G -Bdynamic
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), solaris_i386)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G
SHLIB_LINK += -ldl -lsocket -lresolv -lnsl -lm -lc
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), solaris_sparc)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G
SHLIB_LINK += -ldl -lsocket -lresolv -lnsl -lm -lc
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), alpha)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL += -shared -expect_unresolved '*'
endif

ifeq ($(PORTNAME), svr4)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G
CFLAGS += $(CFLAGS_SL)
endif

ifeq ($(PORTNAME), univel)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G -z text
CFLAGS += $(CFLAGS_SL)
ifeq ($(CXX), CC)
CXXFLAGS += -Xw
COMPILE.cc = $(CXX) $(CXXFLAGS:ll,alloca=ll) $(CPPFLAGS) $(TARGET_ARCH) -c
endif
endif

ifeq ($(PORTNAME), unixware)
install-shlib-dep := install-shlib
shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
LDFLAGS_SL := -G -z text
CFLAGS += $(CFLAGS_SL)
ifeq ($(CXX), CC)
CXXFLAGS += -Xw
COMPILE.cc = $(CXX) $(CXXFLAGS:ll,alloca=ll) $(CPPFLAGS) $(TARGET_ARCH) -c
endif
endif

ifeq ($(PORTNAME), win)
install-shlib-dep := install-shlib
shlib := $(NAME)$(DLSUFFIX)
endif

# Default target definition. Note shlib is empty if not building a shlib.

all: lib$(NAME).a $(shlib)

# Rules to build regular and shared libraries

ifneq ($(PORTNAME), win)

lib$(NAME).a: $(OBJS)
ifdef MK_NO_LORDER
$(AR) $(AROPT) $@ $(OBJS)
else
$(AR) $(AROPT) $@ `lorder $(OBJS) | tsort`
endif
$(RANLIB) $@

endif

ifneq ($(shlib),)
ifneq ($(PORTNAME), win)
ifneq ($(PORTNAME), aix)

# Normal case
$(shlib): $(OBJS)
$(LD) $(LDFLAGS_SL) -o $@ $(OBJS) $(SHLIB_LINK)
if [ "$(shlib)" != "lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION)" ]; then \
rm -f lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION); \
$(LN_S) $(shlib) lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION); \
fi
if [ "$(shlib)" != "lib$(NAME)$(DLSUFFIX)" ]; then \
rm -f lib$(NAME)$(DLSUFFIX); \
$(LN_S) $(shlib) lib$(NAME)$(DLSUFFIX); \
fi

else

# AIX case
$(shlib): lib$(NAME).a
$(MKLDEXPORT) lib$(NAME).a $(LIBDIR) > lib$(NAME)$(EXPSUFF)
$(LD) -H512 -bM:SRE -bI:$(SRCDIR)/backend/$(POSTGRES_IMP) -bE:lib$(NAME)$(EXPSUFF) -o $@ $< $(LDFLAGS) $(SHLIB_LINK)

endif

else

# WIN case
$(shlib) lib$(NAME).a: $(OBJS) $(SRCDIR)/utils/dllinit.o
$(DLLTOOL) --export-all --output-def $(NAME).def $(OBJS)
$(DLLWRAP) -o $(shlib) --dllname $(shlib) --def $(NAME).def $(OBJS) $(SRCDIR)/utils/dllinit.o $(DLLINIT) $(SHLIB_LINK)
$(DLLTOOL) --dllname $(shlib) --def $(NAME).def --output-lib lib$(NAME).a

$(SRCDIR)/utils/dllinit.o: $(SRCDIR)/utils/dllinit.c
$(MAKE) -C $(SRCDIR)/utils dllinit.o

endif
endif

# Rules to install regular and shared libraries

.PHONY: all install-lib install-shlib

install-lib: lib$(NAME).a
$(INSTALL) $(INSTL_LIB_OPTS) lib$(NAME).a $(LIBDIR)/lib$(NAME).a

install-shlib: $(shlib)
$(INSTALL) $(INSTL_SHLIB_OPTS) $(shlib) $(LIBDIR)/$(shlib)
ifneq ($(PORTNAME), win)
if [ "$(shlib)" != "lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION)" ]; then \
cd $(LIBDIR); \
rm -f lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION); \
$(LN_S) $(shlib) lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION); \
fi
if [ "$(shlib)" != "lib$(NAME)$(DLSUFFIX)" ]; then \
cd $(LIBDIR); \
rm -f lib$(NAME)$(DLSUFFIX); \
$(LN_S) $(shlib) lib$(NAME)$(DLSUFFIX); \
fi
endif

# Rule to delete shared library during "make clean"

.PHONY: clean-shlib

clean-shlib:
rm -f $(shlib) lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION) lib$(NAME)$(DLSUFFIX)

--------------24D6C420764E69FB0909D014--

From bouncefilter Fri Dec 17 03:50:05 1999
Received: from impact1.hpcc.nectec.or.th (impact1.hpcc.nectec.or.th
[164.115.24.217]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA86311
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 03:49:09 -0500 (EST)
(envelope-from jhickey@impact1.hpcc.nectec.or.th)
Received: (from jhickey@localhost)
by impact1.hpcc.nectec.or.th (8.9.3/8.9.3) id PAA03243
for pgsql-general@postgreSQL.org; Fri, 17 Dec 1999 15:48:13 +0700 (TST)
From: "Justin Hickey" <jhickey@impact1.hpcc.nectec.or.th>
Message-Id: <9912171548.ZM3241@impact1.hpcc.nectec.or.th>
Date: Fri, 17 Dec 1999 15:48:13 +0000
X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail)
To: pgsql-general@postgreSQL.org
Subject: Confirmation of feature of in version 7
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hello all

On another mailing list unassociated with postgres, someone posted a message
indicating that in version 7.x, the 8k limit for tuple size was going to be
eliminated. Can any of the developers confirm this?

Thank you for your time.

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
==================================================================
People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!
==================================================================

From bouncefilter Fri Dec 17 12:55:11 1999
Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA02139
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 12:55:08 -0500 (EST)
(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
MAA17569;
Fri, 17 Dec 1999 12:52:45 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <199912171752.MAA17569@candle.pha.pa.us>
Subject: Re: [GENERAL] Confirmation of feature of in version 7
In-Reply-To: <9912171548.ZM3241@impact1.hpcc.nectec.or.th> from Justin Hickey
at "Dec 17, 1999 03:48:13 pm"
To: Justin Hickey <jhickey@impact1.hpcc.nectec.or.th>
Date: Fri, 17 Dec 1999 12:52:44 -0500 (EST)
CC: pgsql-general@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hello all

On another mailing list unassociated with postgres, someone posted a message
indicating that in version 7.x, the 8k limit for tuple size was going to be
eliminated. Can any of the developers confirm this?

Thank you for your time.

Man, we can't keep any secrets. :-)

Until today, there was hope that we could eliminate that limit in 7.0,
which goes to beta on Feb 1. However, the group has decided to not
included that in 7.0 because the job is larger than anticipated. It
will certainly be in 7.1. We realize many people need that
functionality, and we clearly have a plan to implement it. In fact,
coding has already begun on it.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

From bouncefilter Fri Dec 17 12:56:12 1999
Received: from mi.marnnet (pd7.warszawa.ppp.tpnet.pl [212.160.55.7])
by hub.org (8.9.3/8.9.3) with ESMTP id MAA02191
for <pgsql-general@postgreSQL.org>;
Fri, 17 Dec 1999 12:55:50 -0500 (EST)
(envelope-from marn@wsisiz.edu.pl)
Received: from localhost (marn@localhost)
by mi.marnnet (8.8.7/8.8.7) with ESMTP id SAA23736
for <pgsql-general@postgreSQL.org>; Fri, 17 Dec 1999 18:55:39 +0100
X-Authentication-Warning: mi.marnnet: marn owned process doing -bs
Date: Fri, 17 Dec 1999 18:55:38 +0100 (EET)
From: Marcin Inkielman <marn@wsisiz.edu.pl>
X-Sender: marn@mi.marnnet
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] a problem with single char recoding
In-Reply-To: <18634.991217@vpcit.ru>
Message-ID: <Pine.LNX.4.21.9912171821480.18960-100000@mi.marnnet>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

hi all!

i have 2 boxes in my local net:
192.168.1.1 - linux 2.2.12/postgres 6.5.3
192.168.1.2 - windows 98+postgres_odbc+MS Access 97

i want use my postgres database in 3 ways:
- via psql,
- with libpq,CGI,HTTP -> MS Explorer on my Win boxe
- with ODBC on MS Access

the problem is that my linux box runs with LATIN2 and Windows
with 1250 charset.

I know that Postgres offers a method of character recoding.
Following docs and hints from this list I configured my Postgres with
apropriate options and this recoding works quite well but....

when I start postmaster and access my database
1. with libpq, CGI: LATIN2 on my browser works fine - OK
2. with ODBC+ACCESS : WIN 1250 - OK

and then I retry it with

3. libpq, CGI, browser - WIN1250 is still there - WRONG
4. psql - has also WIN1250 !!!

when I restart postmaster psql/libpq work fine again

I tryed to connect libpq via lo and eth0 interface with the same result
and my charset.conf is:

------------------------------
BaseCharset iso

RecodeTable iso win iso-win.tab
RecodeTable win iso win-iso.tab

HostCharset 192.168.1.1 iso
HostCharset 192.168.1.2 win
HostCharset localhost iso
------------------------------

i think files iso-win.tab/win-iso.tab are ok.

thanks for any hint...

************************************

Marcin Inkielman

************************************

From bouncefilter Fri Dec 17 18:19:16 1999
Received: from pcr.ca (www.pcr.ca [207.139.158.13] (may be forged))
by hub.org (8.9.3/8.9.3) with ESMTP id SAA68025
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 18:18:49 -0500 (EST)
(envelope-from admin@wtbwts.com)
Received: by pcr.ca (Postfix, from userid 1000)
id 8426A1F4C; Fri, 17 Dec 1999 18:17:40 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
by pcr.ca (Postfix) with ESMTP id 700F51F43
for <pgsql-general@postgresql.org>;
Fri, 17 Dec 1999 18:17:40 +0000 (GMT)
Date: Fri, 17 Dec 1999 18:17:40 +0000 (GMT)
From: admin <admin@wtbwts.com>
X-Sender: admin@server.b0x.com
To: pgsql-general@postgresql.org
Subject: making 'like' queries quicker
Message-ID: <Pine.BSF.4.10.9912171814430.7821-100000@server.b0x.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there a way to make queries using the 'like' operator quicker, more
specifically for queries that look like:
select name from table where name like '%abc%';

Thanks,
Marc