[BUGS] timezone offsets and documentation
The documentation says the time with time zone datatype allows zone offsets from +12 to -12. http://www.postgresql.org/docs/8.0/static/datatype-datetime.html This is at odds with the implementation which allows values +1359 to -1359 jurka=# select '00:00:00+1359'::timetz; timetz 00:00:00+13:59 (1 row) Further the list of available timezone names says that Etc/GMT-14 is a valid timezone. http://www.postgresql.org/docs/8.0/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE This allows: jurka=# set timezone to 'Etc/GMT-14'; SET jurka=# select '00:00:00'::timetz; timetz - 00:00:00+14 (1 row) but this is not an allowed value: jurka=# select '00:00:00+14'::timetz; ERROR: time zone displacement out of range: "00:00:00+14" Kris Jurka ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] BUG #1457: ./configure --with-openssl --enabled-thread-safety fails
The following bug has been logged online: Bug reference: 1457 Logged by: Tim Larson Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: YDLinux 3.0.1 Description:./configure --with-openssl --enabled-thread-safety fails Details: Required lib installed at /usr/include/openssl/ssl.h, but ./configure step still fails all three tests for it. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] Postgres install on windows 2003 server
I am having problems installing PostgresSQL 8.0.0 on our windows 2003
server. I downloaded the postgresql-8.0.1.zip installer from
http://www.postgresql.org/ftp/win32/ but each time I try to install it I get
a "Error binding test network socket: 10013" error message. This always
happens at the point where the installer brings up the initialise database
cluster window dialogue.
I checked on the Microsoft website to find out what the error code meant and
it said "Permission denied.
An attempt was made to access a socket in a way forbidden by its access
permissions."
I get this error no matter who am logged in as or how.
Any help you can offer will be highly appreciated
Thanks
Adewale Adodo
Systems Administrator
PRO IV Limited
Boundary Way
Hemel Hempstead
Tel:+44 (0) 1442 232424 ext 2667
Fax:+44 (0) 1442 231382
[EMAIL PROTECTED]
www.proiv.com
This email is sent on behalf of Northgate Information Solutions UK Limited
("Northgate") and is strictly confidential and intended solely for the
addressee(s). It may contain personal and confidential information and as such
may be protected by the Data Protection Act 1998.
If you are not the intended recipient of this email you must: (i) not disclose,
copy or distribute its contents to any other person nor use its contents in any
way or you may be acting unlawfully; (ii) contact Northgate immediately on +44
(0)1442 232424 quoting the name of the sender and the addressee then delete it
from your system.
Any views or opinions expressed within this email are those of the author, and
do not necessarily represent those of Northgate.
Northgate has scanned this email for viruses but does not accept any
responsibility once this email has been transmitted. You should scan
attachments (if any) for viruses.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
[BUGS] BUG #1454: error in "select * from table where a1 like '%\%%' " ???
The following bug has been logged online: Bug reference: 1454 Logged by: Ricky Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Mandrake Linux 10.1 Description:error in "select * from table where a1 like '%\%%' " ??? Details: I perform a query to get data,which contains '%'. so I do this query. select * from table where a1 like '%\%%'; but it returns all rows. then I do another query. select * from table where a1 like '\%'; but it still return all rows. like "select * from table" ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] BUG #1455: pg_dumpall fails
The following bug has been logged online: Bug reference: 1455 Logged by: Boris Makovecki Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Windows 2K3 web server Description:pg_dumpall fails Details: I'm trying to migrate postgre DB from 7.4 to 8.0. When I start pg_dumpall (8.0) and connect it to 7.4 it fails with error: pg_dump: SQL command failed pg_dump: Error message from server: ERROR: cannot cast type "unknown" to text pg_dump: The command was: SELECT proretset, prosrc, probin, null::text as proargnames, provolatile, proisstrict, prosecdef, (SELECT lanname FROM pg_catalog.pg_language WHERE oid = prolang) as lanname FROM pg_catalog.pg_proc WHERE oid = '17926077'::pg_catalog.oid oid 17926077 stand for recursive function: CREATE OR REPLACE FUNCTION meta.entity_inherit_from(int4) RETURNS varchar AS 'DECLARE id_e ALIAS FOR $1; rez varchar; a int4; BEGIN SELECT INTO a lng_inherit_from_fkeyi_ref FROM meta.entity WHERE lng_entity_pkeyi=id_e; IF a IS NULL THEN rez= \'\' || id_e; ELSE rez=meta.entity_inherit_from(a) || \',\' || id_e; END IF; RETURN rez; END; ' LANGUAGE 'plpgsql' VOLATILE; please advice, regards, Boris Makovecki ABAK.NET ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] BUG #1456: COPY FROM error
The following bug has been logged online: Bug reference: 1456 Logged by: Pascal Van Puymbroeck Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Windows 2000 Description:COPY FROM error Details: The COPY table FROM command works fine as long as you use drives local to the machine like c: or e: , but when you try to use the command with a network drive mapped to o: for eaxmple, you get a 'could not open file for reading: invalid argument' error. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] install errors with dspace
Hello I am installing postgresql 7.4.3 with ant 1.6.1 jdk1.4.3 tomcat web server 5.0.19 under linux enterprise ws and I ran in to trouble with the with-java switch og the configure option. It produed errors so I left out the with-java switch and downloaded jdbc compiled driver. I noticed however that at the end of the postgresql install phase I saw a reference to the command /etc/initd/postgresql restart problem is there is a path/etc/init.d on my machine but that’s where the similarity ends and I cant locate any postgresql folder…… let alone command restart…. Is this a installation problem with postgresql or is there something else I have missed? Where else can the restart command and postgresql folder be ? Also , I am installing all this software with dspace 1.2 and that software generates a build failure which references some java issues is there any link ? ant problem/ java problem? thanks Nigel Pegus Systems Unit Main Library The University of The West Indies Ph: 662-2002 Ext: 2263 / 3358 <>
[BUGS] Password authentication on Windows psql
Hello, I have a problem with psql on Windows XP Pro. After an attempt to connect to a database I get this error: psql: FATAL: password authentication failed for user "" This happens both for local (Windows) and remote (Linux) database. Both databases are easily accessible from other clients (psql for Linux, pgAdmin III, jdbc). The problem is that there is no password prompt even if I try to force it by -W option. According to pg_hba.conf, there should be no need to ask for password at all (local/all databases/trust). There is the same error message in the postgresql log as on the screen (see above). Version: psql (PostgreSQL) 8.0.0 Similar bug report: #1354 Best regards Filip Hrbek
Re: [BUGS] Bad planner decision in Postgres
> Matthew Wakeling <[EMAIL PROTECTED]> writes: > > [ snip... ] > > If we remove the limit, then the planner switches to this query plan: > > > Limit (cost=156.24..156.26 rows=10 width=14) > > ... which still has a limit. I think you have made several cut-and-paste > errors here, because the plans you are exhibiting aren't legal for the > queries you say they are for. Nor do I see a reason that the planner > would use, eg, a Sort step for a query with no ORDER BY. Have you > perhaps been fooling with the various enable_xxx options to try to force > the planner to do what you think it should do? I'm sorry, yes they are cut-and-paste errors. I haven't fiddled with the enable_xxx options to get those results. The queries that I ran actually did have an order by clause (ordered on column), and that query you point out as having a limit is another copy-and-paste error - I used a limit with a large offset, which has an identical performance characteristic as having no limit. The problem stands, my copy-and-paste sucked. Matthew -- If pro is the opposite of con, what is the opposite of progress? ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] Probably libpq on windows bug
Hello, I have a problem with libpq behaviour on Windows. I have no problem to connect to the database and execute SQL statments. The error happens if I try to call a non-existent SQL function, e.g. select function_which_is_really_not_here(); I should get an error: ERROR: function function_which_is_really_not_here() does not existHINT: No function matches the given name and argument types. You may need to add explicit type casts. But I don't - the client does NOTING, it means no error, no result, no hanging... The problem is in the windows native client (libpq) since this problem does not depend on the database I connect to. On the other hand, if I connect to any database (including the one running on Windows) with other clients (libpq on Linux, jdbc etc.) there is no problem. Product version: "PostgreSQL 8.0.0 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)" Best regards Filip Hrbek
[BUGS] BUG #1458: to_char is crazy
The following bug has been logged online: Bug reference: 1458 Logged by: Tomás Zandoná Email address: [EMAIL PROTECTED] PostgreSQL version: 7.3.2 Operating system: i don't know Description:to_char is crazy Details: I'm from brazil. I don't wrote English very well. I dont't know if it's a bug, but I insert the date 2005-10-09 in a Date field. Later I execute: select to_char(day, 'DD/MM/') from test_table; It returns 08/10/2005. ? I don't understand why it returns 08 instead of 09... Can you help me? I'm waiting for an answare. Thanks, Tomás Zandoná. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1455: pg_dumpall fails
"Boris Makovecki" <[EMAIL PROTECTED]> writes: > I'm trying to migrate postgre DB from 7.4 to 8.0. When I start pg_dumpall > (8.0) and connect it to 7.4 it fails with error: > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: cannot cast type "unknown" to > text > pg_dump: The command was: SELECT proretset, prosrc, probin, null::text as > proargnames, provolatile, proisstrict, prosecdef, (SELECT lanname FROM > pg_catalog.pg_language WHERE oid = prolang) as lanname FROM > pg_catalog.pg_proc WHERE oid = '17926077'::pg_catalog.oid Works fine for me, using a 7.4.7 server. Possibly you are hitting some bug in an earlier 7.4.* release? (I don't see anything promising looking in the CVS logs, though.) What *exactly* is the server version? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] BUG #1458: to_char is crazy
On Wed, Feb 02, 2005 at 12:27:53AM +, Tomás Zandoná wrote: Hey Tomás, > I dont't know if it's a bug, but I insert the date 2005-10-09 in a Date > field. > Later I execute: > > select to_char(day, 'DD/MM/') from test_table; > > It returns 08/10/2005. > > ? I don't understand why it returns 08 instead of 09... Is the column of type timestamp or something similar? If so, probably you are being bitten by a timezone problem. If you want just a date, declare the column with type date. -- Alvaro Herrera (<[EMAIL PROTECTED]>) Bob [Floyd] used to say that he was planning to get a Ph.D. by the "green stamp method," namely by saving envelopes addressed to him as 'Dr. Floyd'. After collecting 500 such letters, he mused, a university somewhere in Arizona would probably grant him a degree. (Don Knuth) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1454: error in "select * from table where a1 like '%\%%' " ???
Ricky wrote: > I perform a query to get data,which contains '%'. > so I do this query. > select * from table where a1 like '%\%%'; > but it returns all rows. select * from table where a1 like '%\\%%'; The first \ escapes the second \ for the string parser, the second \ is the escape character for the LIKE pattern. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1457: ./configure --with-openssl --enabled-thread-safety fails
Tim Larson wrote: > Required lib installed at /usr/include/openssl/ssl.h, but ./configure > step still fails all three tests for it. But without showing us the complete details, we won't be able to fix it. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #1455: pg_dumpall fails
Currently I'm using 7.4.0 version. I'll first upgarade to 7.4.7 and then try to upgarade to 8.0.1, thanks, Boris Makovecki -Original Message- From: Tom Lane <[EMAIL PROTECTED]> To: "Boris Makovecki" <[EMAIL PROTECTED]> Cc: pgsql-bugs@postgresql.org Date: Thu, 03 Feb 2005 01:02:01 -0500 Subject: Re: [BUGS] BUG #1455: pg_dumpall fails > "Boris Makovecki" <[EMAIL PROTECTED]> writes: > > I'm trying to migrate postgre DB from 7.4 to 8.0. When I start > pg_dumpall > > (8.0) and connect it to 7.4 it fails with error: > > > pg_dump: SQL command failed > > pg_dump: Error message from server: ERROR: cannot cast type > "unknown" to > > text > > pg_dump: The command was: SELECT proretset, prosrc, probin, > null::text as > > proargnames, provolatile, proisstrict, prosecdef, (SELECT lanname > FROM > > pg_catalog.pg_language WHERE oid = prolang) as lanname FROM > > pg_catalog.pg_proc WHERE oid = '17926077'::pg_catalog.oid > > Works fine for me, using a 7.4.7 server. Possibly you are hitting some > bug in an earlier 7.4.* release? (I don't see anything promising > looking in the CVS logs, though.) What *exactly* is the server > version? > > regards, tom lane > > ---(end of > broadcast)--- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to > [EMAIL PROTECTED]) ---(end of broadcast)--- TIP 8: explain analyze is your friend
