Re: [BUGS] insert statement going into infinite loop

2010-12-27 Thread John R Pierce
On 12/27/10 10:31 PM, Trimurthulu Bandaru wrote: Can you produce a single .sql file that creates the tables and does the problem insert? Can you please make me clear in this issue.. he's asking if you can produce a test case in the form of a .SQL file that creates a schema and demonstrates t

Re: [BUGS] insert statement going into infinite loop

2010-12-27 Thread Trimurthulu Bandaru
On Sat, 2010-12-25 at 11:56 +1100, Craig Ringer wrote: > On 12/24/2010 10:57 PM, Trimurthulu Bandaru wrote: > > Hi everybody.. > > I have table with 11 attributes, 6 of them refers different tables and > > having one primary key. > > when I am trying to insert row with 121 key value, its going into

Re: [BUGS] pgAgent JobScheduler not running jobs

2010-12-27 Thread Robert Haas
On Thu, Dec 16, 2010 at 1:03 AM, Rajesh Sundar wrote: > From command line, i ran the pgAgent command as follows: > pgAgent INSTALL pgAgent hostaddr=127.0.0.1 -u <> -p > <> dbname=postgres USER=mowgli -l C:\Program > Files\PostgreSQL\8.3\bin\scheduler.log The pgAdmin folks also maintain pgAgent.

Re: [BUGS] BUG #5796: Problem with history-files

2010-12-27 Thread Robert Haas
On Mon, Dec 20, 2010 at 5:08 AM, Volker wrote: > first of all I have to say taht pg-admin is really a great tool and this is > my first problem with this program. Glad you like it - but this is not the right place to report a pgAdmin bug. From the "submit a bug" page: This bug report form shoul

Re: [BUGS] BUG #5801: characters not encoded properly for column names

2010-12-27 Thread Robert Haas
On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin wrote: > With the Windows server : > test=# SET client_encoding TO 'win1252'; > SET I have a vague recollection that the argument to SET client_encoding isn't validated on Windows, and if you enter a value that it doesn't like it simply silently doesn'

Re: [BUGS] BUG #5797: Strange bug with hstore

2010-12-27 Thread Robert Haas
On Sun, Dec 26, 2010 at 12:29 AM, Maxim Boguk wrote: > On Tue, Dec 21, 2010 at 7:48 AM, Tom Lane wrote: >> "Maxim Boguk" writes: >>> Bad explain: >>> billing=# EXPLAIN SELECT * from domains where >>> name='"name"=>"somedomain"'::text::hstore->'name'; >>>                                          

Re: [BUGS] BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist

2010-12-27 Thread Bruce Momjian
Heikki Linnakangas wrote: > On 05.12.2010 18:26, Tom Lane wrote: > > Andres Freund writes: > >> On Sunday 05 December 2010 17:42:59 Tom Lane wrote: > >>> I think the reason the given example fails is just that it's all being > >>> done in one transaction. If the null-containing row were known dea

Re: [BUGS] BUG #5781: unaccent() function should be marked IMMUTABLE

2010-12-27 Thread Bruce Momjian
Robert Haas wrote: > On Wed, Dec 22, 2010 at 8:45 PM, Bruce Momjian wrote: > > Tom Lane wrote: > >> "Grant Hutchins and Peter Jaros" writes: > >> > The unaccent(text) function supplied by contrib/unaccent is marked > >> > VOLATILE. > >> > This prevents it from being used in indexes. We believe t

Re: [BUGS] IN clause on BYTEA column works against table directly but gives error against view

2010-12-27 Thread Kevin Grittner
Eric Schwarzenbach wrote: > I've got a SELECT with a WHERE clause using IN against a BYTEA > column which works when I'm querying against the table directly. > However when I substitute an equivalent view in my query (a view > made of several inner joins which simply carry over that same > BYTEA

[BUGS] IN clause on BYTEA column works against table directly but gives error against view

2010-12-27 Thread Eric Schwarzenbach
I've got a SELECT with a WHERE clause using IN against a BYTEA column which works when I'm querying against the table directly. However when I substitute an equivalent view in my query (a view made of several inner joins which simply carry over that same BYTEA column), I get the error: operato