Fwd: [GENERAL] Array Comparison

2014-12-05 Thread David Johnston
Please send replies to the list. On Friday, December 5, 2014, Ian Harding > wrote: > > > On Fri, Dec 5, 2014 at 5:37 PM, David G Johnston < > david.g.johns...@gmail.com> wrote: > >> Ian Harding wrote >> > On Fri, Dec 5, 2014 at 4:55 PM, Ian Harding < >> >> > harding.ian@ >> >> > > wrote: >> >> I

Re: [GENERAL] Array Comparison

2014-12-05 Thread David G Johnston
Ian Harding wrote > On Fri, Dec 5, 2014 at 4:55 PM, Ian Harding < > harding.ian@ > > wrote: >> I have a function that returns bigint[] and would like to be able to >> compare a bigint to the result. Here are some of your options: http://www.postgresql.org/docs/9.3/interactive/functions-array.ht

Re: [GENERAL] Array Comparison

2014-12-05 Thread Ian Harding
On Fri, Dec 5, 2014 at 4:55 PM, Ian Harding wrote: > I have a function that returns bigint[] and would like to be able to > compare a bigint to the result. > > freeload=> select fn_descendents('trip'::varchar,61::bigint); > fn_descendents > --- > {935,81

[GENERAL] Array Comparison

2014-12-05 Thread Ian Harding
I have a function that returns bigint[] and would like to be able to compare a bigint to the result. freeload=> select fn_descendents('trip'::varchar,61::bigint); fn_descendents --- {935,815,689,569,446,325,205,191} (1 row) freeload=> select 935::bigint i

Re: [GENERAL] autovacuum with inheritance

2014-12-05 Thread David G Johnston
yhe wrote > From looking at the log, [...] Any reason not to share it with the people from whom you are asking for help? > I was thinking that autovacuum should only happen on updated table so it > should only autovacuum on one child and not the others for my case. At the point of "stop usage"

Re: [GENERAL] Multiple call handlers per language

2014-12-05 Thread Tom Lane
Kelly Burkhart writes: > Hello, our production database has existed for quite a few years and been > dumped/restored several times for hardware or postgresql upgrades. > Original version was late 7 or early 8, we're currently on 8.4.2. I > noticed on our production database I have two call handle

[GENERAL] Multiple call handlers per language

2014-12-05 Thread Kelly Burkhart
Hello, our production database has existed for quite a few years and been dumped/restored several times for hardware or postgresql upgrades. Original version was late 7 or early 8, we're currently on 8.4.2. I noticed on our production database I have two call handlers for plpgsql and for plpython;

Re: Fwd: Fwd: [GENERAL] Problem with pg_dump and decimal mark

2014-12-05 Thread Adrian Klaver
On 12/05/2014 01:13 AM, Eric Svenson wrote: Hi Adrian, Is the above how the message was actually presented or has a partialtranslation taken >place? Just asking because it would seem to indicate further confusion about the locale. This is an exact copy of the screen contents, no translatio

[GENERAL] Help with ltree queries

2014-12-05 Thread Tim Smith
Hi, I'm trying to use PostgreSQL ltree to make a basic RBAC system as it seems a sensible thing to do because of the hierarchical parsing ltree can do ! I currently have the tables below which I've simplified as follows : /*** create table app_users

Fwd: Fwd: [GENERAL] Problem with pg_dump and decimal mark

2014-12-05 Thread Eric Svenson
Hi Adrian, >Is the above how the message was actually presented or has a partial translation taken >place? Just asking because it would seem to indicate further confusion about the locale. This is an exact copy of the screen contents, no translation by me has taken place. Indeed strange, "ERROR"

Re: [GENERAL] (never executed) in the execution plan

2014-12-05 Thread Albe Laurenz
Thomas Kellerer wrote: > I just encountered something like this in an execution plan: > > -> Hash (cost=19865.48..19865.48 rows=489 width=12) (never executed) > Output: ly.total_count, ly.customer_id > -> Subquery Scan on ly (cost=19864.50..19865.48 rows=489 width=12) > (never exe

[GENERAL] (never executed) in the execution plan

2014-12-05 Thread Thomas Kellerer
I just encountered something like this in an execution plan: -> Hash (cost=19865.48..19865.48 rows=489 width=12) (never executed) Output: ly.total_count, ly.customer_id -> Subquery Scan on ly (cost=19864.50..19865.48 rows=489 width=12) (never executed) Output: ly.total