Re: [BUGS] BUG #5568: will not install

2010-07-22 Thread Kevin Grittner
Lowell Harris lhar...@goldstandardit.com wrote: I keep getting an error message: An error occured executing the Microsoft VC++ runtime installer This computer has MS Visual Studion 2005 and I also went ot Microsoft and updated the CV++ runtimes. What was the URL of the download you're

Re: [BUGS] BUG #5565: ERROR : syntax error at or near )

2010-07-19 Thread Kevin Grittner
john syaba...@yahoo.com wrote: PostgreSQL version: 8.4.1 If you update to the latest 8.4 bug fix release (currently 8.4.4), you'll avoid any bugs which have already been found and fixed. http://www.postgresql.org/support/versioning when insert using client dataset after post

Re: [BUGS] BUG #5547: not able to connect to postgres through the oracle using Linux ODBC driver for Postgres

2010-07-08 Thread Kevin Grittner
Hemanth hxku...@qwest.com wrote: role AIP does not exist This suggests that you're trying to log in as AIP, and PostgreSQL is not finding that role. Can you connect to PostgreSQL with the psql command-line utility and run?: \du If so, please show us the results. By the way, in the

Re: [BUGS] BUG #5535: Backslash in condition for LIKE statement is not seen

2010-07-01 Thread Kevin Grittner
Jeff Benjamin j...@ivertex.com wrote: Seems one cannot use a backslash character in a LIKE condition. By default that has special meaning as an escape character. Try this: select * from test where pattern like E'\\w%' escape '#'; or this: select * from test where pattern like

Re: [BUGS] JDBC: 2 bugs: Getting a smallint array actually gets an integer array and return type of a boolean array is bit.

2010-06-29 Thread Kevin Grittner
Saneesh Apte s...@calccit.org wrote: the base type of a boolean[] is java.sql.Types.BIT instead or java.sql.Types.BOOLEAN. At the very least shouldn't these be aliases for the same type? And secondly the returned type from a smallint[] is an Integer[] instead of a Short[]. Should the

Re: [BUGS] Postgres on AIX5.3 and AIX6.1

2010-06-23 Thread Kevin Grittner
Liang Giap Wee we...@sg.ibm.com wrote: We are considering using your open source Postgres on AIX5.3 and AIX6.1. May i know if you have a opensource community to help with support issues should we face problem with during installation? Thanks... Yeah, you'll find that there's an active

Re: [BUGS] BUG #5509: PostgreSQL fail to show table names containing

2010-06-17 Thread Kevin Grittner
Fosforo Mann fosf...@gmail.com wrote: Tried to view the table schema without success, and them only typing TAB TAB If the table name contains uppercase letters, you need to type the before trying the TAB. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make

Re: [BUGS] BUG #5507: missing chunk number 0 for toast value XXXXX in pg_toast_XXXXX

2010-06-15 Thread Kevin Grittner
中嶋 信二sina...@jops.co.jp wrote: postgres is duplicated. Red Hat Cluster Suite watches a process of each service. PGDATA shares it in strage. There is the thing that a wait server started. A cluster began the change disposal of servers. Because A cluster judged a state of postgres to be

Re: [BUGS] BUG #5507: missing chunk number 0 for toast value XXXXX in pg_toast_XXXXX

2010-06-14 Thread Kevin Grittner
Shinji Nakajima sina...@jops.co.jp wrote: Error message called missing chunk number occurred when I did select of the specific column of the specific table. I delete a record, and the system restores, but prime cause is unknown. Will this be a bug of the databases? Errors like this are

Re: [BUGS] BUG #5499: SQL syntax bug

2010-06-11 Thread Kevin Grittner
Curtis Stecke cste...@interlegis.com wrote: Inserting text that starts with or ends with a dollar sign ($) is impossible. Documentation is not clear on how to do this as well. Works for me. Care to give an example of your problem? test=# create table t1 (c1 text); CREATE TABLE test=#

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-10 Thread Kevin Grittner
Hartmut Goebel wrote: re. 1): While this may be true for many applications it is using hand-crafted SQL statements, it is plain wrong for all applications using some abstraction layer. These layers need to quote column names anyway and the application does not need to be changed here at

Re: [BUGS] BUG #5495: RI/FK on self and inherited table

2010-06-09 Thread Kevin Grittner
Martin Edlman edl...@fortech.cz wrote: ERROR: insert or update on table device violates foreign key constraint device_parent_id_fkey DETAIL: Key (parent_id)=(19947) is not present in table device. But the record is there, it was inserted into net.computer so it's selectable from

Re: [BUGS] BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

2010-06-04 Thread Kevin Grittner
Farid Zidan fa...@zidsoft.com wrote: insert into test_insert (col1, col2) select distinct 'b', '2010-04-30 00:00:00' ERROR: column col2 is of type timestamp without time zone but expression is of type text LINE 16: '2010-04-30 00:00:00' ^ HINT: You will need to rewrite

Re: [BUGS] BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

2010-06-04 Thread Kevin Grittner
Farid Zidan fa...@zidsoft.com wrote: If we were strictly complying with the SQL standard, Considering the statement works in all the 9 DBMS systems+ that I have tested so far as mentioned above, I would say PostgreSQL is not compliant with SQL standard in this regard. The SQL standard is

Re: [BUGS] BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

2010-06-04 Thread Kevin Grittner
Farid Zidan fa...@zidsoft.com wrote: can be eliminated by appropriately handling the distinct keyword and does not have to occur. Based on previous discussions around our approaching data types, I don't think any of the regular PostgreSQL developers are likely to agree with you; but if you

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-04 Thread Kevin Grittner
Hartmut Goebel h.goe...@goebel-consult.de wrote: The application already quotes all column names :-) It's using a generic framework which does not (and must not) rely on column names being non-keywords. Same here. I suspect that this is much more commonn than many PostgreSQL developers

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-04 Thread Kevin Grittner
David Fetter da...@fetter.org wrote: It seems like something that's doable by pg_dump as a default off option. TODO for 9.1? Sounds good to me. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription:

[BUGS] Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

2010-06-04 Thread Kevin Grittner
Farid Zidan fa...@zidsoft.com wrote: but when it gets to use the resultset of the subquery in the insert it forgets how to convert '2010-04-30 00:00:00' to timestamp value Not really. In versions prior to 8.3 it did automagically convert like that. PostgreSQL has some pretty fancy

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-03 Thread Kevin Grittner
Hartmut Goebel h.goe...@goebel-consult.de wrote: Description:pg_dump does not quote column names - pg_restore may fail when upgrading If a 8.3 table contains a column named window, the dump can not be restored into a 8.4 database. Reasons: a) window is a new

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-03 Thread Kevin Grittner
Hartmut Goebel h.goe...@goebel-consult.de wrote: I dumped with the executable form 8.3. That's not expected to work for an upgrade to 8.4. 8.4 did not allow accessing the 8.3 database What do you mean? (What did you try and what happened?) -Kevin -- Sent via pgsql-bugs mailing list

Re: [BUGS] BUG #5488: pg_dump does not quote column names - pg_restore may fail when upgrading

2010-06-03 Thread Kevin Grittner
Hartmut Goebel h.goe...@goebel-consult.de wrote: If upgraded the rpm-packages from 8.3 to 8.4. Then postgres failed starting (something like Database version mismatch). You need to be running the old server using 8.3 software and while using pg_dump from 8.4 software. Does your packager

Re: [BUGS] BUG #5443: Undetected deadlock situation

2010-06-03 Thread Kevin Grittner
Claudio Freire clau...@livra.com wrote: On Thu, 2010-06-03 at 13:42 -0400, Tom Lane wrote: Claudio Freire clau...@livra.com writes: What I did do is analyze server load during the events, and as I suspected, disk activity during the deadlocks seems to suggest a vacuuming taking place.

Re: [BUGS] canceling statement due to user request

2010-06-02 Thread Kevin Grittner
Spangler, Todd toddspang...@comsys.com wrote: canceling statement due to user request I cannot seem to fix. Your application is canceling queries, probably because they're not completing as quickly as it wants them to; that's not a PostgreSQL bug. You should probably gather a bit more

Re: [BUGS] BUG #5484: sum() bug

2010-06-01 Thread Kevin Grittner
Robert Haas robertmh...@gmail.com wrote: On Tue, Jun 1, 2010 at 9:24 AM, viras vi...@yandex.ru wrote: What type of the data is better for using? Numbers up to 10 and accuracy of 2 fractional signs. numeric is a good choice to avoid loss of precision, but can be a bit slower. You

Re: [BUGS] BUG #5477: CREATE DOMAIN NOT NULL constraints not always enforced for INSERT with subquery

2010-05-29 Thread Kevin Grittner
Tom Lane wrote: NOT NULL constraints at the domain level suck. Don't use 'em. +1 As someone who uses domains very heavily, I can attest that the semantics of that are very weak. Whether a domain is nullable depends almost entirely on the context of its use, which you can't (and shouldn't

Re: [BUGS] BUG #5474: Installation

2010-05-26 Thread Kevin Grittner
Nelson da Silva ndsfantas...@hotmail.com wrote: PostgreSQL version: 8.0.2.1 Operating system: Windows XP That's not a supported combination: http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy You should look at upgrading as soon as practicable. An error ocurred

Re: [BUGS] BUG #5448: psql \set does not terminate if variable is referenced recursively

2010-05-05 Thread Kevin Grittner
Francis fmark...@gmail.com wrote: psql \set does not terminate if a variable is referenced recursively. For example, the following will hang the psql client in a nasty way: db=# \set n 1 db=# \set n (:n + 1) It seem to me that the above doesn't hang the psql client, but a subsequent

Re: [BUGS] BUG #5448: psql \set does not terminate if variable is referenced recursively

2010-05-05 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: I think we need to add an explicit recursion test and suppress further expansion of the variable when we see it We can definitely print a message Sounds perfect to me. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make

Re: [BUGS] BUG #5443: Undetected deadlock situation

2010-04-30 Thread Kevin Grittner
Peter Eisentraut pete...@gmx.net wrote: This is not a deadlock. Agreed. It's just two locks on the same table Not as I read it. (and maybe a bit more readable formatting). Eliminating null columns and mangling column headers for length, I get this: locktype| tranid |

Re: [BUGS] BUG #5443: Undetected deadlock situation

2010-04-30 Thread Kevin Grittner
Claudio Freire clau...@livra.com wrote: I know it doesn't look like a deadlock from where you're standing, but it does so from where I am. It's possible that you're filtering out the information which would be most useful to diagnosing the problem. Next time it happens, please send the

Re: [BUGS] BUG #5441: Why Not?????

2010-04-29 Thread Kevin Grittner
sibal si...@sibal.com wrote: Description:Why Not? Why Not Download PG8.4? It's not clear what bug you think you've seen. If the problem is that you're having trouble downloading a file, we'd need a lot more information (like the URL from which you're trying to download)

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-27 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: We'd probably not want to apply this as-is, but should first tighten up what characters URLPath allows, per Kevin's spec research. If we're headed that way, I figured I should double-check. The RFC I referenced was later obsoleted by:

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-27 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Kevin Grittner kevin.gritt...@wicourts.gov writes: Tom Lane t...@sss.pgh.pa.us wrote: We'd probably not want to apply this as-is, but should first tighten up what characters URLPath allows, per Kevin's spec research. If we're headed that way, I figured I

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-27 Thread Kevin Grittner
Kevin Grittner kevin.gritt...@wicourts.gov wrote: I'll read this RFC closely and follow up later today. For anyone not clear on what a URI is compared to a URL, every URL is also a URI (but not the other way around): A URI can be further classified as a locator, a name, or both. The term

Re: [BUGS] BUG #5439: Table crash after CLUSTER command

2010-04-26 Thread Kevin Grittner
Stefan Kirchev stefan.kirc...@gmail.com wrote: PostgreSQL version: 8.3.3 Description:Table crash after CLUSTER command I order to keep good performance on tables CLUSTER is done regularly on each table every Sunday. Almost every time we loose a table which must be recreated

Re: [BUGS] BUG #5438: Bug/quirk in ascii() function

2010-04-26 Thread Kevin Grittner
Christoph Zwerschke c...@online.de wrote: Am 26.04.2010 12:11, schrieb Takahiro Itagaki: Do you know how the SQL standard mention the behavior? IMHO, postgres' behavior is more reasonable because length(' '::char(1)) is 0. Just found http://troels.arvin.dk/db/rdbms/ which claims that this

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-26 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: ie the critical point seems to be that url_path is willing to soak up a string containing and , so the span tags don't get recognized as separate lexemes. While that's obviously the wrong thing in this particular example, I'm not sure if it's the wrong

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-26 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Hmm, thanks for the reference, but I'm not sure this is specifying quite what we want to get at. In particular I note that it excludes '%' on the grounds that that ought to be escaped, so I guess this is specifying the characters allowed in an underlying

Re: [BUGS] Bug with Tsearch and tsvector

2010-04-26 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: there's a potential compatibility issue here, so my thought is to apply this only in HEAD. Agreed. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5437: Production db down

2010-04-23 Thread Kevin Grittner
shanmugavel shanmugave...@onwardgroup.com wrote: Description:Production db down now i face the problem how can i resolve that the problem [cut and paste from an archive post from three years ago about a non-production version under development] You've actually given no

Re: [BUGS] query related to pgsql

2010-04-20 Thread Kevin Grittner
Abhishek Maurya abhi.cse@gmail.com wrote: while connecting php with database created in postgres,we r facing one error ..errror is that its demanding a password of postgres..but while installing or using postgres we hadnt gave any password.. so hw cn we solve this problem.. You haven't

Re: [BUGS] bugs that have not been replied-to on list

2010-04-19 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: IME many of the bugs that go unanswered are non-bugs (eg #5316) or inadequately described (eg #5429) Agreed. If the goal is make sure nothing important slips through the cracks, a tracker could help. If the goal is 100% response rate to pgsql-bugs

Re: [BUGS] BUG #5421: pg_attribute broken

2010-04-14 Thread Kevin Grittner
cool shower coolshower2...@yahoo.co.jp wrote: PostgreSQL version: 8.1.8 Q2:Does anything have repair patches ? You may want to review the fixes between 8.1.8 and the latest 8.1 bug fix release, which is 8.1.20: http://www.postgresql.org/docs/8.1/static/release.html Perhaps one of these

Re: [BUGS] BUG #5408: Failed to connect to the database

2010-04-08 Thread Kevin Grittner
omar omarar...@hotmail.com wrote: PostgreSQL version: 8.0.0 Operating system: XP Professional SV2 The earliest version of PostgreSQL supported on Windows is 8.2. You should be running a recent version of any release -- the 8.0 major release is up to a 8.0.24 bug patch release, which fixes

Re: [BUGS] pgadmin supports on SLES10.3

2010-04-08 Thread Kevin Grittner
manohar cr manohar...@gmail.com wrote: I am trying to install pgadmin on Suse Linux Enterprise version 10.3. I've never heard of that. I've heard of openSUSE 10.3 and I've heard of SuSE Linux Enterprise Server (SLES) 10 SP3. They're not at all the same thing. Which do you have? -Kevin

Re: [BUGS] dividing money by money

2010-04-05 Thread Kevin Grittner
John R Pierce pie...@hogranch.com wrote: Chris Travers wrote: Hmm... Back to the drawing board on that helper module :-). like I said, its a big tarpit. If you start up on this again, you might want to start a new thread with a more descriptive subject. Those who weren't interested in

Re: [BUGS] dividing money by money

2010-04-01 Thread Kevin Grittner
Andy Balholm a...@balholm.com wrote: That's hardly an improvement if you're concerned about lack of exactness. I know; I lose a couple of digits by using float8 instead of numeric, but it's much simpler and faster It also has the advantage of being symmetrical with the other operators.

Re: [BUGS] dividing money by money

2010-04-01 Thread Kevin Grittner
Andy Balholm a...@balholm.com wrote: OK. Here is the whole thing in C Cool! I'll take it for a spin when I get a little time. I guess there's not much point adding that TODO item now. ;-) -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your

Re: [BUGS] dividing money by money

2010-03-31 Thread Kevin Grittner
Chris Travers ch...@metatrontech.com wrote: Just thinking about the more general problem and how things could be handled more gracefully... Sure, but in the meantime, consider: test=# select '12'::money * '2'::numeric; ?column? -- $24.00 (1 row) test=# select '24'::money /

Re: [BUGS] dividing money by money

2010-03-31 Thread Kevin Grittner
Andy Balholm a...@balholm.com wrote: quotient = (float8)dividend / (float8)divisor; PG_RETURN_FLOAT8(quotient); That was my first inclination, but the fact that two different people talked about using division by '1'::money as a way to convert money to another type has me nervous about

Re: [BUGS] dividing money by money

2010-03-30 Thread Kevin Grittner
John R Pierce pie...@hogranch.com wrote: Boszormenyi Zoltan wrote: But then any operator between two money values would only work if both values have the same currency. That sounds like a sane limitation. and, are there still any currenccies like old style UK where the subunits aren't

Re: [BUGS] dividing money by money

2010-03-30 Thread Kevin Grittner
Chris Travers ch...@metatrontech.com wrote: With due respect, this sort of thing is rather difficult to get right all at once. The existing type is fixed point and we know how to add and subtract two of them. I don't think it's all that difficult to add division, yielding some non-money

Re: [BUGS] dividing money by money

2010-03-30 Thread Kevin Grittner
I wrote: yielding some non-money numeric type (like perhaps float8). Hmmm... Given that we've already had a couple posts on the idea that dividing by '1'::money could convert money to something more general, I guess it would be safer to stick to numeric. -Kevin -- Sent via pgsql-bugs

Re: [BUGS] dividing money by money

2010-03-29 Thread Kevin Grittner
Andy Balholm wrote: The ability to divide money by money would be useful for finding what percent one money value is of another. That certainly sounds useful and natural to me. I don't think it rises to the level of a *bug*, but it's a reasonable request for enhancement. If there are no

Re: [BUGS] BUG #5377: group by problem

2010-03-18 Thread Kevin Grittner
michel rosa mr...@geomatic.ch wrote: I get extras rows for 2010-03-02 I'm not sure I understand your concern. Is it that the result set includes these rows?: to_char | cost | count +--+--- 2010-03-02 | 2.0 | 7 2010-03-02 | 3.0 | 3 What do you get

Re: [BUGS] what can i do

2010-03-17 Thread Kevin Grittner
vladislav DONCHEV vladui...@abv.bg wrote: Hello guys , i have a problem :( I had a postgreSQL before some days but i delete it , and now i cant install it , cause there are 2 message at the end of install when it making account or something like that You haven't told us what operating

Re: [BUGS] update the same tuple in one command twice

2010-03-16 Thread Kevin Grittner
terry 94487...@qq.com wrote: In one command, why can we update the same tuple for twice? TEST=# update t1 set a = t2.d from t2 where a=t2.c; UPDATE 1 It says it updated it once. Why do you think otherwise? And the result is not predicated!! When you select multiple rows without

Re: [BUGS] BUG #5373: Crash at the first time system bootup

2010-03-12 Thread Kevin Grittner
Bhavin rahul_bhav...@yahoo.com wrote: PostgreSQL version: postgresSQL 8.4 Operating system: windows xp Description:Crash at the first time system bootup My postgreSQL 8.4 crashes everytime at the first bootup of my system. It works fine after first system bootup. What could

Re: [BUGS] BUG #5354: Type timestamptz doesn't allow to store time zone

2010-03-02 Thread Kevin Grittner
Robert Haas wrote: Vitali wrote: When I select from the table, the timetz has the correct time zone, the timestamptz has -6 as a time zone, which is my server default. I'm not sure what you think the bug is, but timestamptz definitely doesn't store the time zone in which the value is

Re: [BUGS] BUG #5342: Error

2010-02-23 Thread Kevin Grittner
Shilpa.R shilpar1...@gmail.com wrote: PostgreSQL version: PostgreSQL Data That's not very informative; what do you get from running?: select version(); I found an error stating syntax error near or at sets in the following query select agegrp, cartype, risk, count(*) as count from

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-23 Thread Kevin Grittner
Bruce Momjian br...@momjian.us wrote: I think you should just edit the TODO wiki and list all the things we agree need fixing: Done, although with the wealth of opinions and dearth of agreement I referenced much material and said that more discussion was needed before starting development.

Re: [BUGS] helo

2010-02-22 Thread Kevin Grittner
Kris Jurka bo...@ejurka.com wrote: You need to pass an instance of java.sql.Array, not a Collection or something else that is array like. Ah, right. After extracting an array from the java.util.ArrayList, it needs to be turned into a java.sql.Array using the Connection.createArrayOf method.

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Kevin Grittner
Bruce Momjian br...@momjian.us wrote: Was this ever addressed? It should probably be on the TODO list. I was going to try to do this along with other items which came out of generating an LSB conforming init script, but have been pulled in different directions for now. When I get the time

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Kevin Grittner
Bruce Momjian br...@momjian.us wrote: I think you should just edit the TODO wiki and list all the things we agree need fixing Will do. It may take me a while to chase down all the issues from the LSB script work. If I recall correctly, some of what I was looking at seems necessary for a

Re: [BUGS] BUG #5308: How to disable Case sensitivity on naming identifiers

2010-02-03 Thread Kevin Grittner
Chris Travers ch...@metatrontech.com wrote: It is probably understandable that some people would miss it (I did, a moment ago, until you mentioned it). That seems like pretty good evidence that a footnote or qualification of the initial statement would occasionally save some confusion.

Re: [BUGS] BUG #5308: How to disable Case sensitivity on naming identifiers

2010-02-03 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Key words and unquoted identifiers are case insensitive... FWIW, that is the *exact* rewording that came to mind for me as a possible solution. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription:

Re: [BUGS] BUG #5299: unable to start postgres service

2010-01-29 Thread Kevin Grittner
Savita savita.ha...@gmail.com wrote: I have installed postgres. When I check the status of postgres service I get it is not running. But when I start pg_ctl start it says server starting. But server is actually not started. How do we get debug information for pg_ctl start? This doesn't

Re: [BUGS] BUG #5301: difference of behaviour between 8.3 and 8.4 on IS NULL with sub rows of nulls

2010-01-29 Thread Kevin Grittner
Jehan-Guillaume (ioguix) de Rorthais iog...@free.fr wrote: and here is another test case where 8.3 is inconsistent with *himself* this time: Sounds like an argument that the behavior *should* have changed in 8.4. We don't like to introduce behavioral changes which might break something in a

Re: [BUGS] BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown

2010-01-26 Thread Kevin Grittner
yua **azun...@hotmail.com wrote: PostgreSQL 8.3.3 on i386-portbld-freebsd7.0, compiled by GCC cc (GCC) 4.2.1 20070719 [FreeBSD] postgres[681]: [506-1] WARNING: worker took too long to start; cancelled Nov 12 11:15:12 kddi-nwmgr01 postgres[681]: [507-1] WARNING: worker took too long

Re: [BUGS] BUG #5292: Corrupted installer

2010-01-21 Thread Kevin Grittner
. Uszkodzony means corrupted. Dnia 20 stycznia 2010 16:21 Kevin Grittner kevin.gritt...@wicourts.gov napisa*(a): Adam Rakowski foo-scr...@o2.pl wrote: Both one-click installer and zip archive from postgresql.org are corrupted. Where did you get them (e.g., a URL)? Any chance

Re: [BUGS] Hi

2010-01-20 Thread Kevin Grittner
beulah prasanthi wrote: Can i insert all the data into all the tables(multiple tables) with a single trip to the database,by creating rules/triggers This is not a bug. Please repost to another list; perhaps pgsql-general. When you re-post, you may want to provide more detail about the

Re: [BUGS] BUG #5293: constant function (date_trunc) is repeatedly evaluated inside loop

2010-01-20 Thread Kevin Grittner
Richard Neill rn...@cam.ac.uk wrote: date_trunc('day', timestamp '2010-01-20 10:16:55') What happens with a timestamp with time zone literal? -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription:

Re: [BUGS] BUG #5292: Corrupted installer

2010-01-20 Thread Kevin Grittner
Adam Rakowski foo-scr...@o2.pl wrote: Both one-click installer and zip archive from postgresql.org are corrupted. Where did you get them (e.g., a URL)? Any chance of download problems? -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your

Re: [BUGS] BUG #5293: constant function (date_trunc) is repeatedly evaluated inside loop

2010-01-20 Thread Kevin Grittner
Richard Neill rn...@cam.ac.uk wrote: #fast WHERE column '2010-010-20 00:00:00' #fast WHERE column date_trunc('day', timestamp with time zone '2010-01-20 10:16:55') #slow WHERE column date_trunc('day', timestamp

Re: [BUGS] BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown

2010-01-19 Thread Kevin Grittner
yua **azun...@hotmail.com wrote: What kind of information shall, I geve you There are some good guidelines here: http://wiki.postgresql.org/wiki/SlowQueryQuestions -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription:

Re: [BUGS] BUG #5278: Postgres hangs / crashes every day

2010-01-15 Thread Kevin Grittner
Murali Mohan Nareddy nmmredd...@hotmail.com wrote: Do any of the problems I am facing are fixed in a recent release so that I can upgrade to that release? You're taking a big risk if you don't update, even though your immediate problems seem to be caused by the AV software. To view the bugs

Re: [BUGS] BUG #5281: Timestamp fields not inserting from 8.3 to 8.4

2010-01-15 Thread Kevin Grittner
Jodi Escalante jescala...@assistgroup.com wrote: INSERT INTO assessment (id, created, taken, current_weight, note, assessment_type, stay_id, contact_id, estimated_discharge_date, cond_chf, cond_pulm_heart, cond_endocrine_other, cond_skin_temp, ) VALUES ( 50, 2008-01-11 15:06:40.257000

Re: [BUGS] BUG #5278: Postgres hangs / crashes every day

2010-01-14 Thread Kevin Grittner
Murali nmmredd...@hotmail.com wrote: PostgreSQL version: 8.0.6 Operating system: Windows Server 2003 Standard 32 Bit Description:Postgres hangs / crashes every day You do realize that Windows is not a supported platform for any release less than 8.2?

Re: [BUGS] Substring auto trim

2010-01-13 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: What's the data type of the value being compared to? I get, for instance, postgres=# select substr('ab '::char(4), 1, 4) = 'ab '::char(4); ?column? -- t (1 row) This looks like another situation where we're running into trouble because

Re: [BUGS] Substring auto trim

2010-01-13 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Kevin Grittner kevin.gritt...@wicourts.gov writes: This looks like another situation where we're running into trouble because of non-standard behavior when people might be expecting something consistent with other products and the explicit language

Re: [BUGS] OutOfMemory hibernate scroll with 2M records | Postgresql 8.4 DB

2009-12-22 Thread Kevin Grittner
Craig Ringer wrote: Greg Stark wrote: Ankit Kumar wrote: Thanks for your response. Hibernate works well when I change the DB to SQL server but somehow the moment I point to Postgresql it start generating OutOfMemory. Is there some configuration at DB end to ensure it starts using the

Re: [BUGS] BUG #5246: Misleading/inconsistent SQLSTATE behavior

2009-12-16 Thread Kevin Grittner
Chris Travers chris.trav...@gmail.com wrote: I am noticing that that a failed database connection results in an unusable SQLSTATE in libpq, and a very different SQLSTATE than the backend registers. Well, if the client fails to connect to the server, I'm not sure how the server could

Re: [BUGS] Inserts taking exponentially longer as table size grows

2009-12-15 Thread Kevin Grittner
postgres bee postgres_...@live.com wrote: insertion time is increasing as the data in the table is growing. You have given no indication that there is a bug. Please re-post to the performance list, but first you should read these pages (both referenced in the description of the performance

Re: [BUGS] BUG #5225: create table: cast necessary for constant??

2009-12-03 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Sorry about that --- I had confused this case with that of a bare NULL literal, which Postgres treats the same as an unadorned string literal for type determination purposes. You're right that the spec treats them differently. This is feasible for the

Re: [BUGS] BUG #5225: create table: cast necessary for constant??

2009-12-03 Thread Kevin Grittner
Wagner, Kurt kurt.wagnerext...@leoni.com wrote: when writing a character constant elsewhere then at first it is interpreted as character constant - right? then it is casted to the desired type No. It was confusing for me, too; but the PostgreSQL behavior is to treat what the standard

Re: [BUGS] BUG #5225: create table: cast necessary for constant??

2009-12-03 Thread Kevin Grittner
Kevin Grittner kevin.gritt...@wicourts.gov wrote: There is an understandable tendency of those who work deep in the guts of the PostgreSQL software, making all this custom type code work, I mangled that sentence worse than usual. The tendency is to see the PostgreSQL behavior as natural

Re: [BUGS] BUG #5225: create table: cast necessary for constant??

2009-12-02 Thread Kevin Grittner
Craig Ringer cr...@postnewspapers.com.au wrote: On 3/12/2009 12:35 AM, Tom Lane wrote: You really ought to cast the 'I' to some specific type. It's usually neatest to do this by just explicitly identifying the intended type in the first place, eg: SELECT firmnr,

Re: [BUGS] BUG #5212: incorrect resource manager data checksum in record at ...

2009-11-24 Thread Kevin Grittner
Amaya Gamarra amaya.gama...@gtd.es wrote: PostgreSQL version: 8.1.11 We've got a Slony-I cluster over 2 postgres 8.1.11 servers. I join the pgsql.conf file. logging_collector = on That option (and others) are not present in 8.1. Either that's not your version or it's not your

Re: [BUGS] BUG #5127: AbstractJdbc2Connection#doRollback should throws Exception if connection is closed

2009-10-20 Thread Kevin Grittner
tak...@gmail.com wrote: If PostgreSQL server is restarted, old Connection pooled in Application server's ConnectionPool cannot connect to DB. That's OK. But, I can call rollback() on old Connection and it throws no exception. Hmmm What problem are you having? The transaction would

Re: [BUGS] BUG #5127: AbstractJdbc2Connection#doRollback should throws Exception if connection is closed

2009-10-20 Thread Kevin Grittner
takiguchi tak...@gmail.com wrote: This is a problem of connection pooling, not of transaction. public void testConnection() { Connection con = dataSource.getConnection(); // get a connection from pool (If DB server restarted, invalid connection will be returned) boolean valid =

Re: [BUGS] BUG #5127: AbstractJdbc2Connection#doRollback should throws Exception if connection is closed

2009-10-20 Thread Kevin Grittner
takiguchi tak...@gmail.com wrote: public void testConnection() { Connection con = dataSource.getConnection(); // get a connection from pool (If DB server restarted, invalid connection will be returned) boolean valid = true; try { // execute some DMLs...

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-16 Thread Kevin Grittner
Pedro Gimeno pgsql-...@personal.formauri.es wrote: Tom Lane wrote: This could be addressed by having the postmaster report its $PGDATA value in the pg_ping response, but I would be against that on security grounds. We don't let nonprivileged users know where PGDATA is, why would we make

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-16 Thread Kevin Grittner
Robert Haas robertmh...@gmail.com wrote: Well, then Tom's idea of using a random number seems pretty solid no matter how you slice it. Maybe a UUID. A random number is looking like the best option. I'm not sure why I'd want to generate a perfectly good 128 bit random number and then throw

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-16 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: I was envisioning just using PostmasterRandom() (after initializing the seed from time(NULL) as we do now). I don't think we need a super-wide random number. Fine with me. Just that and CanAcceptConnections in the response? It seems like pg_ping

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-16 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Alternatively, do the postmaster support and make the presumably-minor pg_ctl mods to use it, and then a standalone pg_ping utility could come later. I'm not sure how big the utility would be, but surely bigger than the delta in pg_ctl. Bigger than the

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-16 Thread Kevin Grittner
Robert Haas robertmh...@gmail.com wrote: UUIDs throw away 6 bits? http://en.wikipedia.org/wiki/Universally_Unique_Identifier#Version_4_.28random.29 -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription:

Re: [BUGS] issue with integer nullable column and value 0

2009-10-15 Thread Kevin Grittner
Sean Hsien umph...@gmail.com wrote: 2009/10/15 Kevin Grittner kevin.gritt...@wicourts.gov: what are the OS and Java versions on the client side? I'm using CentOS 5.2 64-bits with postgres 8.1.11 + java 6u16, and Windows Vista 32-bits with postgres 8.4.1 + java 6u13. So the Java code

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-15 Thread Kevin Grittner
Gerhard Leykam gel...@sealsystems.de wrote: I am using a start script to set up my PostgreSQL database: it runs initdb, if not done yet, starts the instance with pg_ctl start and checks everything is fine by pg_ctl status. If there is another PostgreSQL database on the same machine

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-15 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Well, it's arguably a start-script bug OK. While mulling that it occurred to me that some additional output from the postmaster would help to solve another thing that's an acknowledged shortcoming of pg_ctl, namely that it can't parse postgresql.conf

Re: [BUGS] BUG #5118: start-status-insert-fatal

2009-10-15 Thread Kevin Grittner
Kevin Grittner kevin.gritt...@wicourts.gov wrote: I neglected that point in my recently proposed LSB conforming script Hmmm... On review, I see that I assumed that the -w switch on pg_ctl start would cover this. I see that the problem is that this uses psql to connect to the specified port

<    1   2   3   4   5   >