Re: [HACKERS] proposed community service: make coverage

2012-10-24 Thread Amit Kapila
On Wednesday, October 24, 2012 6:37 AM Alvaro Herrera wrote: > Hi, > > During the course of some discussion, I proposed the possibility of us > exposing a continuously updated copy of the "make coverage" target, > after running some standard test suite (possibly some of the > "check-world" targets

Re: [HACKERS] enhanced error fields

2012-10-24 Thread Alvaro Herrera
Peter Geoghegan escribió: > On 24 October 2012 23:29, Alvaro Herrera wrote: > >> > >> Let me know if you think that that's a good idea. > > > > I guess you didn't get around to it. > > I did get some work on this done, which does change things somewhat. > In particular, I think that the need to h

Re: [HACKERS] autovacuum truncate exclusive lock round two

2012-10-24 Thread Stephen Frost
Jan, * Jan Wieck (janwi...@yahoo.com) wrote: > This problem has been discussed before. Those familiar with the > subject please skip the next paragraph. Apologies if this was already thought-of and ruled out for some reason, but... > Because all the scanning had been done in parallel to normal D

[HACKERS] Re: [WIP] Performance Improvement by reducing WAL for Update Operation

2012-10-24 Thread Noah Misch
On Tue, Oct 23, 2012 at 08:21:54PM -0400, Noah Misch wrote: > -Patch- -tps@-c1- -tps@-c2- -tps@-c8- -WAL@-c8- > HEAD,-F80 816 164465281821 MiB > xlogscale,-F80 824 164365511826 MiB > xlogscale+lz,-F80 717 146

Re: [HACKERS] enhanced error fields

2012-10-24 Thread Peter Geoghegan
On 24 October 2012 23:29, Alvaro Herrera wrote: >> >> Let me know if you think that that's a good idea. > > I guess you didn't get around to it. I did get some work on this done, which does change things somewhat. In particular, I think that the need to have so many new fields is questionable, an

Re: [HACKERS] enhanced error fields

2012-10-24 Thread Alvaro Herrera
Peter Geoghegan escribió: > > I think that we're both going to be busy next week, since we're both > attending pgconf.eu. For that reason, I would like to spend some time > tomorrow to get something in shape, that I can mark "ready for > committer". I'd like to get this patch committed during this

Re: [HACKERS] autovacuum truncate exclusive lock round two

2012-10-24 Thread Jan Wieck
Here is the patch for it. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin diff --git a/src/backend/commands/vacuumlazy.c b/src/backend/commands/vacuumlazy.c index c9253a9..9f880f0 100644 *** a/src/backend/commands/vacuumlazy.c --- b/src/

[HACKERS] autovacuum truncate exclusive lock round two

2012-10-24 Thread Jan Wieck
This problem has been discussed before. Those familiar with the subject please skip the next paragraph. When autovacuum finds a substantial amount of empty pages at the end of a relation, it attempts to truncate it in lazy_truncate_heap(). Because all the scanning had been done in parallel to

Re: [HACKERS] Re: [WIP] Performance Improvement by reducing WAL for Update Operation

2012-10-24 Thread Robert Haas
On Tue, Oct 23, 2012 at 8:21 PM, Noah Misch wrote: > -Patch- -tps@-c1- -tps@-c2- -tps@-c8- -WAL@-c8- > HEAD,-F80 816 164465281821 MiB > xlogscale,-F80 824 164365511826 MiB > xlogscale+lz,-F80 717 1466

Re: [HACKERS] Visual Studio 2012 RC

2012-10-24 Thread Brar Piening
Alvaro Herrera wrote: There having been no updated patch yet, I have closed this as returned with feedback. Thanks Noah! Please make sure to submit an updated patch to the upcoming commitfest, which is due to start in about three weeks. Due to an hyperacute increase of workload in my day job

Re: [HACKERS] proposal - assign result of query to psql variable

2012-10-24 Thread Phil Sorber
On Tue, Oct 16, 2012 at 12:24 PM, Pavel Stehule wrote: > 2012/10/16 Shigeru HANADA : >> Hi Pavel, >> >> On Tue, Oct 16, 2012 at 6:59 AM, Pavel Stehule >> wrote: >>> here is updated patch, I moved lot of code from lexer to command.com, >>> and now more \gset doesn't disable other backslash command

Re: [HACKERS] [PATCH] Support for Array ELEMENT Foreign Keys

2012-10-24 Thread Tom Lane
Marco Nenciarini writes: > Please find the attached refreshed patch (v2) which fixes the loose ends > you found. Attached is a v3 patch that updates the syntax per discussion, uses what seems to me to be a saner (more extensible) catalog representation, and contains assorted other code cleanup.

Re: [HACKERS] [PATCH] Support for Array ELEMENT Foreign Keys

2012-10-24 Thread Tom Lane
Noah Misch writes: > For FKs, we currently document that "The referenced columns must be the > columns of a non-deferrable unique or primary key constraint in the referenced > table." Taking that literally, one might imagine that bare UNIQUE indexes do > not qualify. However, transformFkeyCheckA

[HACKERS] Re: [WIP] Performance Improvement by reducing WAL for Update Operation

2012-10-24 Thread Noah Misch
On Wed, Oct 24, 2012 at 05:55:56AM +, Amit kapila wrote: > Wednesday, October 24, 2012 5:51 AM Noah Misch wrote: > > Stepping back a moment, I would expect this patch to change performance in > > at > > least four ways (Heikki largely covered this upthread): > > > a) High-concurrency workload

Re: [HACKERS] [PATCH] Support for Array ELEMENT Foreign Keys

2012-10-24 Thread Noah Misch
On Wed, Oct 24, 2012 at 12:36:31AM -0400, Tom Lane wrote: > The proposed patch uses this if the referencing column is an array: > > SELECT 1 WHERE > (SELECT pg_catalog.count(DISTINCT y) FROM pg_catalog.unnest($1) y) > OPERATOR(pg_catalog.=) > (SELECT pg_catalog.count(*) FROM > (SELECT 1

Re: [HACKERS] [WIP] pg_ping utility

2012-10-24 Thread Alvaro Herrera
Thom Brown wrote: > On 24 October 2012 15:24, Alvaro Herrera wrote: > > Guys, > > > > May I remind everyone that we still have an commitfest open, which to > > date has 23 patches needing some effort, and that this patch, while > > probably very useful and interesting, belongs to the next commitfe

Re: [HACKERS] [WIP] pg_ping utility

2012-10-24 Thread Thom Brown
On 24 October 2012 15:24, Alvaro Herrera wrote: > Guys, > > May I remind everyone that we still have an commitfest open, which to > date has 23 patches needing some effort, and that this patch, while > probably very useful and interesting, belongs to the next commitfest > which is not yet in progr

Re: [HACKERS] [WIP] pg_ping utility

2012-10-24 Thread Alvaro Herrera
Guys, May I remind everyone that we still have an commitfest open, which to date has 23 patches needing some effort, and that this patch, while probably very useful and interesting, belongs to the next commitfest which is not yet in progress. -- Álvaro Herrerahttp://www.2ndQuadra

Re: [HACKERS] patch to add \watch to psql

2012-10-24 Thread Peter Eisentraut
On 10/19/12 8:15 PM, Will Leinweber wrote: > This patch adds \watch to psql. It is much like the unix equivalent, > defaulting to every 2 seconds, and allowing you optionally specify a > number of seconds. This doesn't handle multiline queries: => \watch select 1 + ERROR: 42601: syntax error at

Re: [HACKERS] [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility

2012-10-24 Thread Hannu Krosing
On 10/23/2012 06:47 PM, Robert Haas wrote: On Wed, Oct 17, 2012 at 4:25 PM, Josh Berkus wrote: ... 3. Double-down on #2 in a multithreaded environment. For an application-level queue, the base functionality is: ADD ITEM READ NEXT (#) ITEM(S) LOCK ITEM DELETE ITEM More sophisticated an usefu

Re: [HACKERS] [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility

2012-10-24 Thread Hannu Krosing
On 10/23/2012 04:13 PM, Tom Lane wrote: [ hadn't been following this thread, sorry ] Hannu Krosing writes: My RFC was for a proposal to skip writing the unneeded info in local tables and put it _only_ in WAL. This concept seems fundamentally broken. What will happen if the master crashes imm

Re: [HACKERS] [help] Is it possible to support remote COPY operation on PG?

2012-10-24 Thread Michael Paquier
On Wed, Oct 24, 2012 at 3:54 PM, Xiong He wrote: > Is it possible to copy some table data from remote client to the PG > database server directly without upload the data file to the server side in > advance? > With a psql client you can use the command ¥copy to perform that. -- Michael Paquier h