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

Re: lock_timeout GUC patch

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>, Josh Berkus <josh(at)agliodbs(dot)com>, Sándor Miglécz <sandor(at)cybertec(dot)at>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: lock_timeout GUC patch
Date: 2010-01-15 04:43:58
Message-ID: 3073cc9b1001142043s566ffe7cyb744da9a7e45c1f8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2010/1/13 Boszormenyi Zoltan <zb(at)cybertec(dot)at>:
>>
>> Your smaller patch is attached, with the above strangeness. :-)
>>

you still had to add this parameter to the postgresql.conf.sample in
the section about lock management

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-15 05:45:54
Subject: Re: PG_MODULE_MAGIC checks and pg_migrator
Previous:From: Simon RiggsDate: 2010-01-15 04:20:41
Subject: Re: Streaming replication status

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