[BUGS] Date Representation Bug. Timezone and update on an already posted as #208 reportbug

2001-04-20 Thread pgsql-bugs
Gianfranco Pesce ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Date Representation Bug. Timezone and update on an already posted as #208 reportbug Long Description The problem of date representation of 22/05/1977 and 28/05/19

Re: [BUGS] Date Representation Bug. Timezone and update on an already posted as #208 reportbug

2001-04-20 Thread Tom Lane
[EMAIL PROTECTED] writes: > The problem of date representation of 22/05/1977 and 28/05/1978 is > related with time zone. What do you get if you coerce the funny dates to timestamp, eg, select '22/05/1977'::date::timestamp; regards, tom lane

[BUGS] Re: Postgresql date bug

2001-04-20 Thread Tom Lane
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > if I insert with > insert into pippo values ('22/05/1977 01:00:00'); > all goes ok. > with > insert into pippo values ('22/05/1977 00:59:00'); > the result is wrong! Is it related with daylight saving time? Possibly, but why just those dates? AF

[BUGS] pg_ctl restart bug

2001-04-20 Thread jmitchell
"pg_ctl restart" fails if anything is quoted in postmaster.opts. $ pg_ctl restart Smart Shutdown request at Fri Apr 20 10:11:38 2001 postmaster successfully shut down postmaster successfully started /usr/bin/postmaster: invalid argument -- '-D' Try '/usr/bin/postmaster --h

[BUGS] Bug: pg_ctl restart fails

2001-04-20 Thread wsheldah
Hi, When I try to restart postgresql, I get the following error: postgres@host $ pg_ctl restart [ok messages snipped here] /usr/local/pgsql/bin/postmaster: invalid argument -- '-D' The problem seems to be the single quotes surrounding the command line args. I confirmed this by starting postg

[BUGS] wrong dump order in pg_dump for new data types

2001-04-20 Thread pgsql-bugs
Harald Bartel ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description wrong dump order in pg_dump for new data types Long Description Version: PostgreSQL 7.1 System: Debian Woody, both Linux 2.2.14 and 2.4.3 The problem occurs for new

[BUGS] grant insert for single tables does not work

2001-04-20 Thread pgsql-bugs
Harald Bartel (harald.bartel@prozentor) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description grant insert for single tables does not work Long Description Version: PostgreSQL 7.1 System: Debian Woody, both Linux 2.2.14 and 2.4.3.1 It is not possible t

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Peter Eisentraut
[EMAIL PROTECTED] writes: > "pg_ctl restart" fails if anything is quoted in postmaster.opts. > > $ pg_ctl restart > Smart Shutdown request at Fri Apr 20 10:11:38 2001 > postmaster successfully shut down > postmaster successfully started > /usr/bin/postmaster: invalid argument

[BUGS] the operator "=" does not work for some SQL queries

2001-04-20 Thread pgsql-bugs
Harald Bartel ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description the operator "=" does not work for some SQL queries Long Description Version: PostgreSQL 7.1 System: Debian Woody, both Linux 2.2.14 and 2.4.3 For some SQL queries

Re: [BUGS] grant insert for single tables does not work

2001-04-20 Thread Tom Lane
[EMAIL PROTECTED] writes: > It is not possible to grant insert for a single table. Granting this > right only works if grant all is used. Works for me: << as postgres >> regression=# create user foo; CREATE USER regression=# create table zz (f1 int); CREATE << as foo >> regression=> select *

Re: [BUGS] grant insert for single tables does not work

2001-04-20 Thread Peter Eisentraut
> Harald Bartel (harald.bartel@prozentor) reports a bug with a severity of 3 > It is not possible to grant insert for a single table. Granting this > right only works if grant all is used. Works here. More details required. -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/

Re: [BUGS] wrong dump order in pg_dump for new data types

2001-04-20 Thread Tom Lane
[EMAIL PROTECTED] writes: > The problem occurs for new data types: > When pg_dump is called, sometimes the CREATE TYPE is dumped before > input/output functions are dumped. This makes a restore impossible. I believe this was fixed about two weeks ago. Are you sure you are using 7.1 final release

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Unless someone can show me a way to extract the command line options out > of the opts file while preserving whitespace in them, I'm going to > eliminate the quotes being put out. Won't work if any of the options contain whitespace, which is quite pr

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Tom Lane
pg_ctl restart works fine with this patch, but I'm not sure whether it breaks useful cases for the other paths: *** *** 323,335 shift po_path=$1 shift ! POSTOPTS=$@ fi else # -o given POSTOPTS="-D $PGDATA $

Re: [BUGS] the operator "=" does not work for some SQL queries

2001-04-20 Thread Tom Lane
[EMAIL PROTECTED] writes: > For some SQL queries (for an example see below) the operator "=" on text does not >work, that is, no rows are returned, although some should be returned.In PostgreSQL >7.0.3 I avoided this problem by using > the LIKE operator instead of the "=" operator.In PostgreSQL

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Bruce Momjian
> > $ cat postmaster.opts > > /usr/bin/postmaster '-D' '/var/lib/pgsql/data' > > Unless someone can show me a way to extract the command line options out > of the opts file while preserving whitespace in them, I'm going to > eliminate the quotes being put out. You know, I looked at that

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Bruce Momjian
I can assure you that $@ is never the way to go, always use "$@". Not sure about the second change. > pg_ctl restart works fine with this patch, but I'm not sure whether it > breaks useful cases for the other paths: > > *** > *** 323,335 > shift > po_pa

Re: [BUGS] pg_ctl restart bug

2001-04-20 Thread Peter Eisentraut
Tom Lane writes: > pg_ctl restart works fine with this patch, but I'm not sure whether it > breaks useful cases for the other paths: Looks good. -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter ---(end of broadcast)--

[BUGS] lo_import does not check type before performing an import

2001-04-20 Thread pgsql-bugs
Michael Richards ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description lo_import does not check type before performing an import Long Description lo_import within pgsql does not verify that it is reading from a file. You can import

[BUGS] SQL function lo_unlink is not documented

2001-04-20 Thread pgsql-bugs
Michael Richards ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description SQL function lo_unlink is not documented Long Description http://postgresql.readysetnet.com/users-lounge/docs/7.1/programmer/lo-funcs.html Says: There are two bu

[BUGS] lo_import does not check type before performing an import

2001-04-20 Thread pgsql-bugs
Michael Richards ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description lo_import does not check type before performing an import Long Description lo_import within pgsql does not verify that it is reading from a file. You can import

Re: [BUGS] lo_import does not check type before performing an import

2001-04-20 Thread Tom Lane
[EMAIL PROTECTED] writes: > lo_import within pgsql does not verify that it is reading from a file. So we should prohibit reading from, eg, a named pipe? Sorry, I don't agree. regards, tom lane ---(end of broadcast)--- TIP