Re: [GENERAL] How can I select rows by comparing an array data type column with multiple values ?

2014-06-03 Thread Arup Rakshit
Just to help you guys the error - here is the full error stack . I am using an ORM with Rails 2.1.0 :001 > ReportingGroup.where("ARRAY[?] && workplace_ids", Workplace.select(:id))    (0.4ms)  SELECT COUNT("workplaces"."id") FROM "workplaces" D, [2014-06-04T12:00:23.479024 #14429] DEBUG -- :    (

Re: [GENERAL] How can I select rows by comparing an array data type column with multiple values ?

2014-06-03 Thread Arup Rakshit
Hi, Suppose I have a table  CREATE TABLE sal_emp (     name            text,     pay_by_quarter  integer[], ); Now I have a query - select * from sal_emp where pay_by_quarter && some_var Now some var some times is fully empty, then I am getting error as  PG::UndefinedFunction: ERROR:  operato

Re: [GENERAL] bytea Issue - Reg

2014-06-03 Thread Adrian Klaver
On 06/03/2014 01:25 AM, sramay wrote: Hi all, I am having a specifc issue of bytea. When we started storing more records in the database on bytea field on version 9.1.x the data has gone to pg_toast tables. The strange observation is now after a table size of 700 gb it now all of a sudden re

Re: [GENERAL] libpq: indefinite block on poll during network problems

2014-06-03 Thread Merlin Moncure
On Fri, May 30, 2014 at 4:00 PM, Dmitry Samonenko wrote: > I'm troubled with possible 'imperfection' of very simple, yet core feature > - PQexec, which can lead to blocked applications. You believe that the > problem is caused by client design flaw. Okay, fine. Is it possible to mark > this poten

[GENERAL] bytea Issue - Reg

2014-06-03 Thread sramay
Hi all, I am having a specifc issue of bytea. When we started storing more records in the database on bytea field on version 9.1.x the data has gone to pg_toast tables. The strange observation is now after a table size of 700 gb it now all of a sudden reporting table not found on the tomcat lo

Re: [GENERAL] new index type with clustering in mind.

2014-06-03 Thread Jack Douglas
> > > To reduce complexity (eg MVCC/snapshot related issues), index entries > > > would be added when a row is inserted, but they would not be removed > > > when the row is updated/deleted (or when an insert is rolled back): > > It's an interesting idea, but, how can you *ever* delete index ent