Dan Ports writes:
> On Mon, Apr 04, 2011 at 07:04:59PM -0400, Robert Haas wrote:
>> On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost wrote:
>>> What'd be horribly useful would be the pid and the *time* that the lock
>>> was taken.
>> Well, I don't think we're likely to redesign pg_locks at this poi
On Mon, Apr 04, 2011 at 07:04:59PM -0400, Robert Haas wrote:
> On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost wrote:
> > What'd be horribly useful would be the pid and the *time* that the lock
> > was taken.. ?Knowing just the pid blows, since the pid could technically
> > end up reused (tho not te
On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost wrote:
> * Robert Haas (robertmh...@gmail.com) wrote:
>> Well, the flip side is that if you have appropriate logging turned on,
>> you might be able to go back and look at what the transaction that
>> took the lock actually did, which won't be possible
* Robert Haas (robertmh...@gmail.com) wrote:
> Well, the flip side is that if you have appropriate logging turned on,
> you might be able to go back and look at what the transaction that
> took the lock actually did, which won't be possible if you arbitrarily
> throw the PID away.
What'd be horrib
On Mon, Apr 4, 2011 at 2:50 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>> Dan Ports wrote:
>>> I see Robert committed that one already. If there's a consensus
>>> that omitting the pid for committed transactions is the right
>>> thing to do, I'm happy to put together a patch. I think that is
Robert Haas wrote:
> Dan Ports wrote:
>> I see Robert committed that one already. If there's a consensus
>> that omitting the pid for committed transactions is the right
>> thing to do, I'm happy to put together a patch. I think that is a
>> better approach than trying to keep it after commit unt
On Mon, Apr 4, 2011 at 2:37 PM, Dan Ports wrote:
> I see Robert committed that one already. If there's a consensus that
> omitting the pid for committed transactions is the right thing to do,
> I'm happy to put together a patch. I think that is a better approach
> than trying to keep it after comm
On Mon, Apr 04, 2011 at 10:33:22AM -0500, Kevin Grittner wrote:
> There are patches for all known issues except one. Dan Ports was
> able to replicate the latest issue uncovered by YAMAMOTO Takashi
> using a particular DBT-2 configuration, found the issue, and posted
> a patch:
Well, it would be
> Betas are usually done using the regular release process, which is
> wrap-on-Thursday-release-on-Monday (to accommodate both packagers who
> work weekdays and those who can only spare time on weekends). So we'd
> really be talking about code freeze on the 14th if we want release on
> the 18th.
On Mon, Apr 4, 2011 at 12:01 PM, Dave Page wrote:
> On Mon, Apr 4, 2011 at 4:54 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> At the risk of getting laughed at, how about, say, ~2 weeks from now?
>>
>> Seems reasonable to me.
>>
>>> Plus or minus a couple of days based on people's schedules a
On Mon, Apr 4, 2011 at 4:54 PM, Tom Lane wrote:
> Robert Haas writes:
>> At the risk of getting laughed at, how about, say, ~2 weeks from now?
>
> Seems reasonable to me.
>
>> Plus or minus a couple of days based on people's schedules and which
>> day of the week we'd like the wrap to happen on
Robert Haas wrote:
> On Mon, Apr 4, 2011 at 11:33 AM, Kevin Grittner
> wrote:
>> Should these items be on the open issues list?
>
> Yes, please.
Done.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Robert Haas writes:
> At the risk of getting laughed at, how about, say, ~2 weeks from now?
Seems reasonable to me.
> Plus or minus a couple of days based on people's schedules and which
> day of the week we'd like the wrap to happen on.
Betas are usually done using the regular release proces
On Mon, Apr 4, 2011 at 11:33 AM, Kevin Grittner
wrote:
> Should these items be on the open issues list?
Yes, please.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Robert Haas wrote:
> I have the impression from the SSI threads that there might be an
> issue or two there that needs to be dealt with, but there again I
> think that there are patches already posted, and that we just need
> to get around to dealing with them.
There are patches for all known
Folks,
I think it might be about time to start thinking concretely about when
we might like to kick beta1 out the door. The open issues list still
has 9 issues on it, but we now have patches awaiting review for most
of those issues (credit where credit is due: Fujii Masao, Noah Misch,
Joey Adams
16 matches
Mail list logo
