Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Date: 2010-01-05 20:48:23
Message-ID: 15018.1262724503@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Something like:
>     (my $bkival = $row->{bki_values}) =~ s/"[^"]*"/"xxx"/g;
>     my $atts = {};
>     @{$atts}{(at)attnames} = split /\s+/, $bkival;
> might work better.

I committed Alvaro's suggestion (undef at the bottom), but feel
free to clean it up if you like this way better.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-05 20:59:42
Subject: Re: We no longer have a fallback for machines without working int64
Previous:From: Andrew DunstanDate: 2010-01-05 20:36:30
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

pgsql-committers by date

Next:From: Robert HaasDate: 2010-01-05 21:54:00
Subject: pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).
Previous:From: Andrew DunstanDate: 2010-01-05 20:36:30
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group