Re: Strange Windows problem, lock_timeout test request

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hari Babu <haribabu(dot)kommi(at)huawei(dot)com>, 'Craig Ringer' <craig(at)2ndQuadrant(dot)com>, 'Hans-Jürgen Schönig' <hs(at)cybertec(dot)at>, 'Ants Aasma' <ants(at)cybertec(dot)at>, 'PostgreSQL Hackers' <pgsql-hackers(at)postgresql(dot)org>, 'Amit kapila' <amit(dot)kapila(at)huawei(dot)com>
Subject: Re: Strange Windows problem, lock_timeout test request
Date: 2013-02-27 19:38:29
Message-ID: 512E60B5.8020707@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013-02-27 20:06 keltezéssel, Stephen Frost írta:
> Zoltan,
>
> * Boszormenyi Zoltan (zb(at)cybertec(dot)at) wrote:
>> If we get rid of the per-statement variant, there is no need for that either.
> For my 2c, I didn't see Tom's comments as saying that we shouldn't have
> that capability, just that the implementation was ugly. :)

But I am happy to drop it. ;-)

> That said, perhaps we should just drop it for now, get the lock_timeout
> piece solid, and then come back to the question about lock_timeout_stmt.

OK, let's do it this way.

>
> Thanks,
>
> Stephen

--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
http://www.postgresql.at/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2013-02-27 23:57:34 Database system identifier via SELECT
Previous Message Heikki Linnakangas 2013-02-27 19:28:18 Re: Typo in usage of pg_xlogdump