On 2013-05-22 23:05:40 -0400, Robert Haas wrote:
> On Wed, May 22, 2013 at 11:02 PM, Andres Freund
> wrote:
> > On 2013-05-22 22:51:13 -0400, Robert Haas wrote:
> >> In discussions today, Tom Lane suggested testing the time to start up
> >> a backend and run a simple query such as "SELECT 2+2" in
On Wed, May 22, 2013 at 11:02 PM, Andres Freund wrote:
> On 2013-05-22 22:51:13 -0400, Robert Haas wrote:
>> In discussions today, Tom Lane suggested testing the time to start up
>> a backend and run a simple query such as "SELECT 2+2" in the absence
>> of a relcache file.
>
>> I did this and can'
On Mon, May 20, 2013 at 10:19 AM, Heikki Linnakangas
wrote:
>> It shouldn't be difficult to restrict the set of backends that have to
>> be signaled to those that have the relation open. You could have a
>> special kind of catchup signal that means "catch yourself up, but
>> don't chain"
>
> What
On 2013-05-22 22:51:13 -0400, Robert Haas wrote:
> In discussions today, Tom Lane suggested testing the time to start up
> a backend and run a simple query such as "SELECT 2+2" in the absence
> of a relcache file.
> I did this and can't measure any overhead as a result of MVCC catalog
> access. I
On Wed, May 22, 2013 at 1:52 PM, Bruce Momjian wrote:
> Do we want to run pgindent soon?
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Tue, May 21, 2013 at 10:18 PM, Robert Haas wrote:
> [ MVCC catalog access seems to be pretty cheap ]
In discussions today, Tom Lane suggested testing the time to start up
a backend and run a simple query such as "SELECT 2+2" in the absence
of a relcache file.
I did this and can't measure any
A PostgreSQL user recently reported on pgsql-admin about an issue:
when he changed wal_level from 'minimal' to 'hot_standby', the WAL
segment sequence rewound, that is, it started using old names. A
snippet of his "ls -lrt pg_xlog":
-rw--- 1 postgres postgres 16777216 May 21 12:13 0001
Hi,
Please find attached a patch to take code-coverage of CREATE OPERATOR
(src/backend/commands/operatorcmds.c) from 56% to 91%.
Any and all feedback is welcome.
--
Robins Tharakan
regress_createoperator.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
Do we want to run pgindent soon?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
On 17 May 2013 21:46, Jaime Casanova wrote:
> On Sun, Nov 4, 2012 at 10:22 PM, Qi Huang wrote:
>> Dear hackers
>> Sorry for not replying the patch review. I didn't see the review until
>> recently as my mail box is full of Postgres mails and I didn't notice the
>> one for me, my mail box con
10 matches
Mail list logo