Re: [HACKERS] TODO : Allow parallel cores to be used by vacuumdb [ WIP ]

2014-11-22 Thread Amit Kapila
On Mon, Nov 17, 2014 at 8:55 AM, Dilip kumar wrote: > > On 13 November 2014 15:35 Amit Kapila Wrote, > >As mentioned by you offlist that you are not able reproduce this > > >issue, I have tried again and what I observe is that I am able to > > >reproduce it only on *release* build and some cases

Re: [HACKERS] [PATCH] Simplify EXISTS subqueries containing LIMIT

2014-11-22 Thread Tom Lane
David Rowley writes: > I'm reasonably happy with the patch now, the only small niggles are maybe > the Assert() is probably not so much needed as transformLimitClause() seems > to coerce to int8 anyway, and recompute_limits() does not bother with the > Assert() when it does the same thing, either

Re: [HACKERS] postgres_fdw behaves oddly

2014-11-22 Thread Tom Lane
Etsuro Fujita writes: > (2014/11/19 18:21), Ashutosh Bapat wrote: >> Ok. I added that comment to the commitfest and changed the status to >> "ready for commiter". > Many thanks! I committed this with some cosmetic adjustments, and one not-so-cosmetic one: I left it continuing to allow CTID condi

Re: [HACKERS] [v9.5] Custom Plan API

2014-11-22 Thread Tom Lane
Kouhei Kaigai writes: > Let me explain the current idea of mine. > CustomScan node will have a field that hold varnode mapping information > that is constructed by custom-scan provider on create_customscan_plan, > if they want. It is probably a list of varnode. > If exists, setrefs.c changes its b

Re: [HACKERS] some ideas from users

2014-11-22 Thread Pavel Stehule
2014-11-22 15:18 GMT+01:00 Andrew Dunstan : > > On 11/22/2014 06:20 AM, Pavel Stehule wrote: > >> Hi >> >> I did a week training and here are some ideas from people, who are >> starting with Postgres. >> >> 1. possibility to set server side variables simply as psql option. >> Motivation - more sim

Re: [HACKERS] HINTing on UPDATE foo SET foo.bar = ..;

2014-11-22 Thread Marko Tiikkaja
On 2014-11-22 18:02, Tom Lane wrote: Marko Tiikkaja writes: A common mistake is to try and qualify column references on the LHS of SET in UPDATE. The error message can be a bit cryptic at times, too. Perhaps, but this hint is not much of an improvement: HINT: Target column references in U

Re: [HACKERS] HINTing on UPDATE foo SET foo.bar = ..;

2014-11-22 Thread Tom Lane
Marko Tiikkaja writes: > A common mistake is to try and qualify column references on the LHS of > SET in UPDATE. The error message can be a bit cryptic at times, too. Perhaps, but this hint is not much of an improvement: > HINT: Target column references in UPDATE must not be qualified becau

Re: [HACKERS] some ideas from users

2014-11-22 Thread David G Johnston
Pavel Stehule wrote > : > > 2014-11-22 12:24 GMT+01:00 Marko Tiikkaja < > marko@ > >: > >> On 2014-11-22 12:20 PM, Pavel Stehule wrote: >> >>> 2. missing table function with all settings. Like SHOW ALL, but with >>> filtering possibility >>> >> >> What's wrong with pg_settings? >> > > nothing,

Re: [HACKERS] some ideas from users

2014-11-22 Thread Andrew Dunstan
On 11/22/2014 06:20 AM, Pavel Stehule wrote: Hi I did a week training and here are some ideas from people, who are starting with Postgres. 1. possibility to set server side variables simply as psql option. Motivation - more simple and natural changing datestyle for psql in shell scripts. "

Re: [HACKERS] How to use brin indexes?

2014-11-22 Thread hubert depesz lubaczewski
On Sat, Nov 22, 2014 at 3:29 AM, Alvaro Herrera wrote: > I won't push this right away because I want to add the cross-type stuff > to the tests, to ensure I haven't bollixed anything; I ran a few quick > manual tests and everything seems to work. But if Depesz wants to test > the behavior, be my

Re: [HACKERS] HINTing on UPDATE foo SET foo.bar = ..;

2014-11-22 Thread Marko Tiikkaja
On 2014-11-22 05:11, Peter Geoghegan wrote: On Fri, Nov 21, 2014 at 7:49 PM, Marko Tiikkaja wrote: A common mistake is to try and qualify column references on the LHS of SET in UPDATE. I think that this is a good idea, but as written the patch doesn't handle aliases correctly: postgres=# cre

Re: [HACKERS] some ideas from users

2014-11-22 Thread Pavel Stehule
2014-11-22 12:26 GMT+01:00 Antonin Houska : > On 11/22/2014 12:24 PM, Marko Tiikkaja wrote: > > On 2014-11-22 12:20 PM, Pavel Stehule wrote: > >> 2. missing table function with all settings. Like SHOW ALL, but with > >> filtering possibility > > > > What's wrong with pg_settings? > > Do you mean p

Re: [HACKERS] some ideas from users

2014-11-22 Thread Pavel Stehule
: 2014-11-22 12:24 GMT+01:00 Marko Tiikkaja : > On 2014-11-22 12:20 PM, Pavel Stehule wrote: > >> 2. missing table function with all settings. Like SHOW ALL, but with >> filtering possibility >> > > What's wrong with pg_settings? > nothing, I didn't find it in doc http://www.postgresql.org/docs/

Re: [HACKERS] some ideas from users

2014-11-22 Thread Antonin Houska
On 11/22/2014 12:24 PM, Marko Tiikkaja wrote: > On 2014-11-22 12:20 PM, Pavel Stehule wrote: >> 2. missing table function with all settings. Like SHOW ALL, but with >> filtering possibility > > What's wrong with pg_settings? Do you mean pg_show_all_settings() ? -- Antonin Houska Cybertec Schöni

Re: [HACKERS] some ideas from users

2014-11-22 Thread Marko Tiikkaja
On 2014-11-22 12:20 PM, Pavel Stehule wrote: 2. missing table function with all settings. Like SHOW ALL, but with filtering possibility What's wrong with pg_settings? .marko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://w

[HACKERS] some ideas from users

2014-11-22 Thread Pavel Stehule
Hi I did a week training and here are some ideas from people, who are starting with Postgres. 1. possibility to set server side variables simply as psql option. Motivation - more simple and natural changing datestyle for psql in shell scripts. "--set" is allocated now, but theoretically we can us