Re: [HACKERS] Maximum number of WAL files in the pg_xlog directory

Hi, Le 15 oct. 2014 22:25, "Guillaume Lelarge" a écrit : > > 2014-10-15 22:11 GMT+02:00 Jeff Janes : >> >> On Fri, Aug 8, 2014 at 12:08 AM, Guillaume Lelarge < guilla...@lelarge.info> wrote: >>> >>> Hi, >>> >>> As part of our monitoring work for our customers, we stumbled upon an issue with our c

Re: [HACKERS] CINE in CREATE TABLE AS ... and CREATE MATERIALIZED VIEW ...

Patch looks good, assigning to committer. On Fri, Oct 31, 2014 at 8:36 AM, Fabrízio de Royes Mello < fabriziome...@gmail.com> wrote: > > > On Mon, Oct 27, 2014 at 4:15 AM, Rushabh Lathia > wrote: > > > > Hi All, > > > > - Patch got applied cleanly. > > - Regression make check run fine. > > - Pat

Re: [HACKERS] Silly coding in pgcrypto

On Sun, Nov 02, 2014 at 10:53:27PM +0100, Marko Tiikkaja wrote: > On 11/2/14, 10:34 PM, Noah Misch wrote: > >On Sun, Nov 02, 2014 at 05:10:25AM +0100, Marko Tiikkaja wrote: > >>*** a/contrib/pgcrypto/pgp-decrypt.c > >>--- b/contrib/pgcrypto/pgp-decrypt.c > >>*** > >>*** 1069,1075 p

Re: [JDBC] [HACKERS] Pipelining executions to postgresql server

On 2014-11-01 14:04:05 +, Mikko Tiihonen wrote: I created a proof of concecpt patch for postgresql JDBC driver that allows the caller to do pipelining of requests within a transaction. The pipelining here means same as for HTTP: the client can send the next execution already before waiting fo

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

On 11/02/2014 02:41 PM, Tom Lane wrote: Andrew Dunstan writes: On 11/02/2014 11:53 AM, Tom Lane wrote: Well, the OID compatibility issue could be dodged by saying that we can't do a pg_upgrade (in-place upgrade) of a database containing MONEY columns. In fact, we might be able to just reject

Re: [HACKERS] Silly coding in pgcrypto

On 11/2/14, 10:34 PM, Noah Misch wrote: On Sun, Nov 02, 2014 at 05:10:25AM +0100, Marko Tiikkaja wrote: *** a/contrib/pgcrypto/pgp-decrypt.c --- b/contrib/pgcrypto/pgp-decrypt.c *** *** 1069,1075 pgp_skip_packet(PullFilter *pkt) while (res > 0) res = pul

Re: [HACKERS] Silly coding in pgcrypto

On 2.11.2014 22:34, Noah Misch wrote: > On Sun, Nov 02, 2014 at 05:10:25AM +0100, Marko Tiikkaja wrote: >> *** a/contrib/pgcrypto/pgp-decrypt.c >> --- b/contrib/pgcrypto/pgp-decrypt.c >> *** >> *** 1069,1075 pgp_skip_packet(PullFilter *pkt) >> >> while (res > 0) >>

Re: [HACKERS] Silly coding in pgcrypto

On Sun, Nov 02, 2014 at 05:10:25AM +0100, Marko Tiikkaja wrote: > *** a/contrib/pgcrypto/pgp-decrypt.c > --- b/contrib/pgcrypto/pgp-decrypt.c > *** > *** 1069,1075 pgp_skip_packet(PullFilter *pkt) > > while (res > 0) > res = pullf_read(pkt, 32 * 1024, &tmp);

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

Andrew Dunstan writes: > On 11/02/2014 11:53 AM, Tom Lane wrote: >> Well, the OID compatibility issue could be dodged by saying that we can't >> do a pg_upgrade (in-place upgrade) of a database containing MONEY >> columns. In fact, we might be able to just reject databases containing >> MONEY[] (

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

On 11/02/2014 11:53 AM, Tom Lane wrote: Andrew Dunstan writes: On 11/02/2014 10:01 AM, Jaime Casanova wrote: Not knowing how difficult it could be maybe a fair compromise is to move MONEY datatype to a contrib. And documenting its limitations. That's pretty much dead in the water, I think. B

Re: [HACKERS] TAP test breakage on MacOS X

On Thu, Oct 30, 2014 at 01:57:15AM -0400, Noah Misch wrote: > On Wed, Oct 29, 2014 at 08:14:07PM -0400, Peter Eisentraut wrote: > > On 10/28/14 9:09 PM, Peter Eisentraut wrote: > > > I have looked into IPC::Cmd, but the documentation keeps telling me that > > > to do anything interesting I have to

Re: [HACKERS] tracking commit timestamps

On 01/11/14 18:44, Andres Freund wrote: On 2014-11-01 22:00:40 +0900, Michael Paquier wrote: On Sat, Nov 1, 2014 at 1:45 PM, Michael Paquier wrote: I am still planning to do more extensive tests, and study a bit more committs.c (with even more comments) as it is the core part of the feature.

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

I wrote: > Either way, requiring a dump/reload for upgrade is surely a better answer > for users of the type than just summarily screwing them. BTW, after reflecting a bit more I'm less than convinced that this datatype is completely useless. Even if you prefer to store currency values in numeric

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

Andrew Dunstan writes: > On 11/02/2014 10:01 AM, Jaime Casanova wrote: >> Not knowing how difficult it could be maybe a fair compromise is to >> move MONEY datatype to a contrib. And documenting its limitations. > That's pretty much dead in the water, I think. Builtin types and > functions have

Re: [HACKERS] how to handle missing "prove"

Peter Eisentraut writes: > On 10/30/14 9:09 PM, Tom Lane wrote: >> Looks generally reasonable, but I thought you were planning to choose a >> different option name? > Yeah, but I couldn't think of a better one. (Anything involving, > "enable-perl-..." would have been confusing with regard to PL/

Re: [HACKERS] How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL

rohtodeveloper writes: > I need the convert function because that Our application will be switched > from SQL Server to PostgreSQL. >> For the options you suggested: >> 1) Pass in datatype as string and deparse and process in the function. >> 2) Are you referring to pg_convert here? > 1) is ye

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

On 11/02/2014 10:01 AM, Jaime Casanova wrote: El nov 2, 2014 7:54 AM, "Andres Freund" > escribió: > > On 2014-11-01 16:59:35 -0700, Josh Berkus wrote: > > All, > > > > While there's argument about hash indexes, it looks like nobody minds if > > the MONEY type

Re: [HACKERS] how to handle missing "prove"

On 10/30/14 9:09 PM, Tom Lane wrote: > Looks generally reasonable, but I thought you were planning to choose a > different option name? Yeah, but I couldn't think of a better one. (Anything involving, "enable-perl-..." would have been confusing with regard to PL/Perl.) > One minor nitpick: perha

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

El nov 2, 2014 7:54 AM, "Andres Freund" escribió: > > On 2014-11-01 16:59:35 -0700, Josh Berkus wrote: > > All, > > > > While there's argument about hash indexes, it looks like nobody minds if > > the MONEY type goes bye-bye. So, time for a patch ... > > FWIW there have been somewhat recent patch

Re: [HACKERS] pg_receivelog completion command

On 2014-11-02 14:33:32 +0100, Magnus Hagander wrote: > On Sun, Nov 2, 2014 at 2:31 PM, Andres Freund wrote: > > This will nead some persistent state about the commands success - > > similar to the current archive status stuff. Given retries and > > everything it might end up to be easier to have a

Re: [HACKERS] Pipelining executions to postgresql server

> > > From: Andres Freund > > > On 2014-11-01 14:04:05 +, Mikko Tiihonen wrote: > > > > I created a proof of concecpt patch for postgresql JDBC driver that > > > > allows the caller to do pipelining of requests within a > > > > transaction. The pipelining here means same as for HTTP: the clien

Re: [HACKERS] pg_receivelog completion command

On Sun, Nov 2, 2014 at 2:31 PM, Andres Freund wrote: > On 2014-11-02 14:26:04 +0100, Magnus Hagander wrote: >> I had a discussion with a few people recently about a hack I wrote for >> pg_receivexlog at some point, but never ended up submitting, and in >> cleaning that up realized I had an open it

Re: [HACKERS] pg_receivelog completion command

On 2014-11-02 14:26:04 +0100, Magnus Hagander wrote: > I had a discussion with a few people recently about a hack I wrote for > pg_receivexlog at some point, but never ended up submitting, and in > cleaning that up realized I had an open item on it. > > The idea is to add a switch to pg_receivexlo

[HACKERS] pg_receivelog completion command

I had a discussion with a few people recently about a hack I wrote for pg_receivexlog at some point, but never ended up submitting, and in cleaning that up realized I had an open item on it. The idea is to add a switch to pg_receivexlog (in this case, -a, but that can always be bikeshedded ot cour

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

On 2014-11-01 16:59:35 -0700, Josh Berkus wrote: > All, > > While there's argument about hash indexes, it looks like nobody minds if > the MONEY type goes bye-bye. So, time for a patch ... FWIW there have been somewhat recent patches for money and it was undeprecated not too long ago. So apparen

Re: [HACKERS] How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL

2014-11-02 13:22 GMT+01:00 rohtodeveloper : > I need the convert function because that Our application will be > switched from SQL Server to PostgreSQL. > > >For the options you suggested: > > >1) Pass in datatype as string and deparse and process in the function. > >2) Are you referring to pg_co

Re: [HACKERS] group locking: incomplete patch, just for discussion

On 2 November 2014 10:39, Simon Riggs wrote: > On 15 October 2014 05:03, Robert Haas wrote: > >> At least to me, that simple scenario is clear-cut[1], but what do we >> do in more complicated situations? For example, suppose backends A >> and B are members of the same locking group. A locks a r

Re: [HACKERS] Pipelining executions to postgresql server

On 2014-11-02 12:11:49 +, Mikko Tiihonen wrote: > > From: Andres Freund > > On 2014-11-01 14:04:05 +, Mikko Tiihonen wrote: > > > I created a proof of concecpt patch for postgresql JDBC driver that > > > allows the caller to do pipelining of requests within a > > > transaction. The pipelin

Re: [HACKERS] How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL

I need the convert function because that Our application will be switched from SQL Server to PostgreSQL. >For the options you suggested: >1) Pass in datatype as string and deparse and process in the function. >2) Are you referring to pg_convert here? 1) is yes. but I want to use the CONVERT (

Re: [HACKERS] Pipelining executions to postgresql server

> From: Andres Freund > On 2014-11-01 14:04:05 +, Mikko Tiihonen wrote: > > I created a proof of concecpt patch for postgresql JDBC driver that > > allows the caller to do pipelining of requests within a > > transaction. The pipelining here means same as for HTTP: the client > > can send the n

Re: [HACKERS] group locking: incomplete patch, just for discussion

On 15 October 2014 05:03, Robert Haas wrote: > At least to me, that simple scenario is clear-cut[1], but what do we > do in more complicated situations? For example, suppose backends A > and B are members of the same locking group. A locks a relation with > AccessShareLock, an unrelated process

Re: [HACKERS] How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL

On Sun, Nov 2, 2014 at 3:40 PM, rohtodeveloper wrote: > > Dear > > > In SQLServer, there'are two functions to converte an expression of one > data type to another. > > 1. CAST ( expression AS data_type [ ( length ) ] ) > 2. CONVERT ( data_type [ ( length ) ] , expression ) > > However, In Postgre

[HACKERS] How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL

Dear In SQLServer, there'are two functions to converte an expression of one data type to another. 1. CAST ( expression AS data_type [ ( length ) ] )2. CONVERT ( data_type [ ( length ) ] , expression ) However, In PostgreSQL, there's only the CAST ( expression AS data_type [ ( length ) ] ) funct