Re: [BUGS] wrong search_path being used

2013-01-13 Thread Rodrigo Rosenfeld Rosas
Em 12-01-2013 18:13, Tom Lane escreveu: Andres Freundand...@2ndquadrant.com writes: On 2013-01-12 14:29:38 -0500, Tom Lane wrote: I think that the alternative most likely to succeed is to consider any change in the active value of search_path as forcing replanning of cached plans. I guess it

Re: [BUGS] wrong search_path being used

2013-01-09 Thread Rodrigo Rosenfeld Rosas
Em 09-01-2013 20:09, Kevin Grittner escreveu: Rodrigo Rosenfeld Rosas wrote: Tom Lane wrote: There have been discussions about changing that if I understand it correctly, you do consider it a bug but you don't want to backport a fix because it might break existent behavior in some dbs, right

[BUGS] wrong search_path being used

2013-01-07 Thread Rodrigo Rosenfeld Rosas
I didn't want to report the bug using the form before confirming it here. Here is a gist of what I'm trying: https://gist.github.com/49fcc8c4a5a810f66833#file-cleanup-sql The relevant part being this: old_path := pg_catalog.current_setting('search_path'); raise notice 'setting search_path

Re: [BUGS] wrong search_path being used

2013-01-07 Thread Rodrigo Rosenfeld Rosas
Em 07-01-2013 17:17, Tom Lane escreveu: Rodrigo Rosenfeld Rosasrr.ro...@gmail.com writes: perform pg_catalog.set_config('search_path', templ, true); ... select count(distinct transaction_id) from public.transaction_condition into temp_count; raise notice '% remaining transactions in