Re: [PATCHES] [HACKERS] CURRENT CVS: MULTIBYTE: CANT CONNECT....

2001-09-09 Thread Tatsuo Ishii
> > Why? set_default_client_encoding does the job anyway. > > Here can't be used static default encoding as for DatabaseEncoding, because > typical code is > > if (!ClientEncoding) > /* ...means "if user doesn't set itself client >* encoding by SET command" >*/ >

[HACKERS] COMMENT ON

2001-09-09 Thread Tatsuo Ishii
In comment.sgml: COMMENT ON AGGREGATE my_aggregate (double precision) IS 'Computes sample variance'; this raises error. However, COMMENT ON AGGREGATE my_aggregate double precision IS 'Computes sample variance'; works but looks strange syntax. Should we fix the program or docs? -- Tatsuo Ishii

Re: [PATCHES] [HACKERS] CURRENT CVS: MULTIBYTE: CANT CONNECT....

2001-09-09 Thread Karel Zak
On Sat, Sep 08, 2001 at 11:51:24PM +0900, Tatsuo Ishii wrote: > > > > > CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \ > > > > > --with-CXX --with-perl --enable-multibyte --enable-cassert \ > > > > > --with-includes=/usr/local/include --with-libs=/usr/local/lib \

Re: [HACKERS] factorial doc bug?

2001-09-09 Thread Tatsuo Ishii
> On Mon, 10 Sep 2001, Tatsuo Ishii wrote: > > > In typeconv.sgml we have an example: > > > > tgl=> select (4.3 !); > > ?column? > > -- > >24 > > (1 row) > > Mathematically speaking, one cannot find the factorial of such a > number. Users could easily cast/round a float to an i

Re: [HACKERS] factorial doc bug?

2001-09-09 Thread Gavin Sherry
On Mon, 10 Sep 2001, Tatsuo Ishii wrote: > In typeconv.sgml we have an example: > > tgl=> select (4.3 !); > ?column? > -- >24 > (1 row) Mathematically speaking, one cannot find the factorial of such a number. Users could easily cast/round a float to an integer - making it suita

[HACKERS] pg_client_encoding

2001-09-09 Thread Tatsuo Ishii
Hi, I'm going to add a new function "pg_client_encoding" returning the current client side encoding name. I know there is a similar functionality already there in PostgreSQL (show client_encoding) but it's pain to handle notice message by a program. Also note that JDBC driver and maybe some othe

[HACKERS] factorial doc bug?

2001-09-09 Thread Tatsuo Ishii
In typeconv.sgml we have an example: tgl=> select (4.3 !); ?column? -- 24 (1 row) However, actually it does not work: test=# select (4.3 !); ERROR: Unable to identify a postfix operator '!' for type 'double precision' You may need to add parentheses or an explicit cast

Re: [HACKERS] INV_ARCHIVE?

2001-09-09 Thread Bruce Momjian
> There are many places in our docs where INV_ARCHIVE is mentioned. In > my understanding, INV_ARCHIVE has never been supported since > PostgreSQL 6.0 was born. Shall we remove it from the docs? It is for large object/inverted object archiving, which we don't have. I have applied this patch to re

Re: [HACKERS] Abort state on duplicated PKey in transactions

2001-09-09 Thread Lincoln Yeoh
I had a similar issue. I needed to make sure I had a unique row- insert if not there, update if there. So I resorted to locking the whole table, then select, then insert/update. What Tom told me to do was to use lock table tablename in exclusive mode for my case. This blocks select for update

[HACKERS] INV_ARCHIVE?

2001-09-09 Thread Tatsuo Ishii
There are many places in our docs where INV_ARCHIVE is mentioned. In my understanding, INV_ARCHIVE has never been supported since PostgreSQL 6.0 was born. Shall we remove it from the docs? -- Tatsuo Ishii ---(end of broadcast)--- TIP 2: you can get

[HACKERS] pg_dump -C and locations (with subject this time)

2001-09-09 Thread Jim Buttafuoco
(sorry for the repost. I forgot the subject last time...) All, I am working a some patches to the code and I noticed that "pg_dump -C database" doesn't provide the database location information in the dump file. Is this correct? Thanks Jim Example: datname | datdba | encoding | datistemp

Re: [HACKERS] INHERIT

2001-09-09 Thread Hannu Krosing
Oliver Elphick wrote: > > Peter Harvey wrote: > >If I try to get the columns from pg_attribute using the oid of a child > >table created with INHERIT I get its columns AND all of its inherited > >columns. > > > >How do I just get the columns added by the child table? > > > >I figure

Re: [HACKERS] Timezones and time/timestamp values in FE/BE protocol

2001-09-09 Thread Barry Lind
Rene, Since the FE/BE protocol deals only with string representations of values, the protocol doesn't have too much to do with it directly. It is what happens on the client and server sides that is important here. Under the covers the server stores all timestamp values as GMT. When a select

Re: [HACKERS] INHERIT

2001-09-09 Thread Oliver Elphick
Peter Harvey wrote: >If I try to get the columns from pg_attribute using the oid of a child >table created with INHERIT I get its columns AND all of its inherited >columns. > >How do I just get the columns added by the child table? > >I figure I could check each column to see if they

[HACKERS] Timezones and time/timestamp values in FE/BE protocol

2001-09-09 Thread Rene Pijlman
I'm working on a problem in the JDBC driver that's related to timezones. How does PostgreSQL handle timezones in the FE/BE protocol exactly? When a client sends a time or timestamp value to the server via the FE/BE protocol, should that be: 1) a value in the client's timezone? 2) a value in the

[HACKERS]

2001-09-09 Thread Jim Buttafuoco
All, I am working a some patches to the code and I noticed that "pg_dump -C database" doesn't provide the database location information in the dump file. Is this correct? Thanks Jim Example: datname | datdba | encoding | datistemplate | datallowconn | datlastsysoid | datpath | idxpath -

[HACKERS] INHERIT

2001-09-09 Thread Peter Harvey
If I try to get the columns from pg_attribute using the oid of a child table created with INHERIT I get its columns AND all of its inherited columns. How do I just get the columns added by the child table? I figure I could check each column to see if they also exist in pg_attribute under a paren

Re: [HACKERS] CVS commit messages

2001-09-09 Thread Bruce Momjian
> Question: > > What has changed with the CVS repository lately? I notice that all of the > commit messages I've read lately on pgsql-committers seem to come from > Marc Fournier. Has Marc just been committing all recent changes, or are > all commit messages, regardless of committer, showing as f

Re: [HACKERS] CVS commit messages

2001-09-09 Thread Marc G. Fournier
I have to look into the commit script to see about pulling out th eproper committer ... cvs logs show the person who did the commit, but the email's are coming from me ... On Sun, 9 Sep 2001, Neil Padgett wrote: > Question: > > What has changed with the CVS repository lately? I notice that all

Re: [HACKERS] [JDBC] NULLs and sort order

2001-09-09 Thread Rene Pijlman
On Sun, 9 Sep 2001 15:25:17 +0200 (CEST), you wrote: >That is correct. Thanks. >> Would it be useful to add this information to the documentation, >> e.g. the documentation of ORDER BY in SELECT? > >Most likely. I'll post it on the docs list. Regards, René Pijlman <[EMAIL PROTECTED]>

Re: [HACKERS] [JDBC] NULLs and sort order

2001-09-09 Thread Peter Eisentraut
Rene Pijlman writes: > Currently the JDBC driver says: > - Backend >= 7.2 sorts nulls higher than any other value in a > domain. In other words: ascending means nulls at the end, > descending means nulls at the start. > - Backend < 7.2 puts nulls at the end regardless of sort order. That is corr

[HACKERS] NULLs and sort order

2001-09-09 Thread Rene Pijlman
The JDBC driver's test suite currently fails on DatabaseMetaData methods that provide information about NULLs and sort order. I've looked through the documentation, but couldn't find anything about it. The JDBC driver returns different values, depending on the backend version (<7.2 vs. >= 7.2), s

[HACKERS] CVS access

2001-09-09 Thread Michael Meskes
Somehow I cannot get ecpg anymore: cvs server: nothing known about pgsql-ecpg CVSROOT is :pserver:[EMAIL PROTECTED]:/home/projects/pgsql/cvsroot. Any idea what I misconfigured? Michael -- Michael Meskes [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!