Re: [BUGS] BUG #2164: Very minor, very low priority SQL parser 'bug' with /* */ comments

2006-01-10 Thread Tom Lane
"John Engelhart" <[EMAIL PROTECTED]> writes: > It looks like there's a minor problem with the SQL parser where it tokenizes > any */ to mean 'end of comment block'. You appear to be suggesting that given /* ... $$ ... */ the parser should think that the $$ is significant. Sorry, that's *not* go

Re: [BUGS] BUG #2164: Very minor, very low priority SQL parser 'bug' with /* */ comments

2006-01-10 Thread Peter Eisentraut
John Engelhart wrote: > When this piece of code is wrapped fully inside a /* */ style comment block, > the parser interprets the */ inside the substring() function as the end of > comment. 'Expected' behavior (principle of least astonishment, at least) is > that the .*/ part inside the substring f

Re: [BUGS] BUG #2162: Same as bug #1679 - finite() - unresolved symbol

2006-01-10 Thread Tom Lane
"Francois Laupretre" <[EMAIL PROTECTED]> writes: > As bug #1679 is more than 6 months old, I'd like to get a status. If it can > help, I confirm that, without modifications, the current stable release of > PostgreSQL does not compile on HP-UX 11.11. It works fine for me anytime I try it on HP's te

Re: [BUGS] INSERT causes psql to crash

2006-01-10 Thread Tom Lane
[EMAIL PROTECTED] writes: > Quoting Tom Lane <[EMAIL PROTECTED]>: >> If it just started happening, I'd speculate about a corrupt executable >> file for psql or libpq. I doubt it's got anything to do with the server >> side. > But this doesn't explain the data I posted previously: That's an inter

[BUGS] BUG #2159: Run-time library path not set

2006-01-10 Thread Henry B. Hotz
The following bug has been logged online: Bug reference: 2159 Logged by: Henry B. Hotz Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.1 Operating system: Solaris 9 Description:Run-time library path not set Details: When the --with-libraries=:... configure

[BUGS] BUG #2161: ILIKE does not work with german umlauts in UTF8

2006-01-10 Thread Thomas Robak
The following bug has been logged online: Bug reference: 2161 Logged by: Thomas Robak Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: i686-pc-linux-gnu SuSE kernel 2.6.11.4-20a-smp Description:ILIKE does not work with german umlauts in UTF

[BUGS] BUG #2160: All the user and Databases are display at client!

2006-01-10 Thread canglong
The following bug has been logged online: Bug reference: 2160 Logged by: canglong Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 All pgs? Operating system: Linux Description:All the user and Databases are display at client! Details: I set pg_hba.conf wi

[BUGS] BUG #2163: feature req: create schema with tablespace foo

2006-01-10 Thread ben
The following bug has been logged online: Bug reference: 2163 Logged by: ben Email address: [EMAIL PROTECTED] PostgreSQL version: na Operating system: all Description:feature req: create schema with tablespace foo Details: request for support of default tablespace i

[BUGS] BUG #2164: Very minor, very low priority SQL parser 'bug' with /* */ comments

2006-01-10 Thread John Engelhart
The following bug has been logged online: Bug reference: 2164 Logged by: John Engelhart Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: FreeBSD 5.4 Description:Very minor, very low priority SQL parser 'bug' with /* */ comments Details: Thi

[BUGS] BUG #2165: excessive number of postgres.exe processes

2006-01-10 Thread Matt Olson
The following bug has been logged online: Bug reference: 2165 Logged by: Matt Olson Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.2 Operating system: Windows XP Professional SP2 Description:excessive number of postgres.exe processes Details: This is somet

[BUGS] createlang plpgsql failed

2006-01-10 Thread Jeevanandam, Kathirvel \(IE10\)
Hi,     We are getting error as “bus error” while running the createlang command createlang –d dbname plpgsql   Please give suggestion, how to resolve this issue.   Best Regards, Jeeva.K

[BUGS] BUG #2162: Same as bug #1679 - finite() - unresolved symbol

2006-01-10 Thread Francois Laupretre
The following bug has been logged online: Bug reference: 2162 Logged by: Francois Laupretre Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.1 Operating system: HP-UX 11.11 Description:Same as bug #1679 - finite() - unresolved symbol Details: Same problem as

Re: [BUGS] INSERT causes psql to crash

2006-01-10 Thread jao
Quoting Tom Lane <[EMAIL PROTECTED]>: [EMAIL PROTECTED] writes: mydb=> insert into test values(11); *** buffer overflow detected ***: psql terminated You seem to have a rather badly broken build there :-(. What's the platform exactly, and what compiler did you use? Can you rebuild wit

Re: [BUGS] Unsuscribe

2006-01-10 Thread Sebastjan Trepca
NO, you will be subscribed to this mailing-list forever and ever!HO-HO-HOOn 1/10/06, Juan Pablo Yañez < [EMAIL PROTECTED]> wrote:Please unsuscribe me.Thanks.---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [BUGS] INSERT causes psql to crash

2006-01-10 Thread Tom Lane
[EMAIL PROTECTED] writes: >mydb=> insert into test values(11); >*** buffer overflow detected ***: psql terminated You seem to have a rather badly broken build there :-(. What's the platform exactly, and what compiler did you use? Can you rebuild with debug support enabled so you can get

Re: [BUGS] possible when setting the timezone

2006-01-10 Thread Tom Lane
Nick Martens <[EMAIL PROTECTED]> writes: > i just tried the commands from the psql console, and seems to crash then too. It turns out that the problem is specific to referencing a timezone name that is a directory (rather than an individual datafile) in the timezone database. In that case the tzl

[BUGS] Unsuscribe

2006-01-10 Thread Juan Pablo Yañez
Please unsuscribe me. Thanks. ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [BUGS] possible when setting the timezone

2006-01-10 Thread Nick Martens
i just tried the commands from the psql console, and seems to crash then too. mydb=# SET TimeZone TO 'America/Indiana'; ERROR: unrecognized time zone name: "America/Indiana" mydb=# SELECT memo_id, memo_title, memo_comment, mydb-# memo_date::timestamp, bedrijf_id, persoon_id, initialenachternaam,

Re: [BUGS] possible when setting the timezone

2006-01-10 Thread Tom Lane
Nick Martens <[EMAIL PROTECTED]> writes: > here it is, including the defenition of the table and view in question, as it > seems it coredumped when it tried to execute a query using a typecast from > timestamptz to timestamp, after setting an invalid timezone, hope it helps. Ah, that's the missin

Re: [BUGS] possible when setting the timezone

2006-01-10 Thread Nick Martens
here it is, including the defenition of the table and view in question, as it seems it coredumped when it tried to execute a query using a typecast from timestamptz to timestamp, after setting an invalid timezone, hope it helps. Nick. ps. there are some strangely named columns as the db is bein

[BUGS] INSERT causes psql to crash

2006-01-10 Thread jao
I have two postgres 7.4.8 databases on hosts X and Y (both P4, running FC4). I create a table: create table test(x int) I then go into psql and insert a row. Here are the results I'm seeing: psql host postgres host result -- X X

Re: [BUGS] possible when setting the timezone

2006-01-10 Thread Tom Lane
Nick Martens <[EMAIL PROTECTED]> writes: > Jan 10 17:14:40 dndwebdev01 postgres[17374]: [1-1] ERROR: unrecognized time > zone name: "America/Indiana" > Jan 10 17:14:40 dndwebdev01 kernel: pid 17374 (postgres), uid 70: exited on > signal 11 (core dumped) Doesn't happen for me: regression=# set

[BUGS] possible when setting the timezone

2006-01-10 Thread Nick Martens
Hello, I am developing an php application and by mistake a wrong timezone was set after I initialized the connection, which resulted in a core dump of the current process. The postgres version is 8.0.3 running on a freebsd 6.0-RELEASE machine with the generic kernel. I tried searching for simila