Re: Where to load modules from?

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Where to load modules from?
Date: 2013-09-15 15:03:10
Message-ID: 5235CC2E.4090503@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-09-15 16:51, Peter Eisentraut wrote:
> On Sun, 2013-09-15 at 16:09 +0200, Dimitri Fontaine wrote:
>> My understanding is that a Commit Fest is mainly about Reviewing, that's
>> why I still added an entry for two designs that I need feedback on
>> before actually coding a solution.
>>
>> Writing the code is the easiest part of those proposals, but that's only
>> true as soon as we decide what code we should be writing.
>
> I understand why using the commit fest process is attractive for this,
> because it enables you to force the issue. But the point of the commit
> fest is to highlight patches whose discussion has mostly concluded and
> get them committed. If we add general discussion to the commit fest,
> it'll just become a mirror of the mailing list, and then we'll need yet
> another level of process to isolate the ready patches from that.

I have one item like this in the current commit fest. I wrote a PoC
patch, but that's just a bad excuse to get around the issue that we
don't really want just RFCs on there.

The problem is when you post an idea requesting comments on -HACKERS,
and nobody or only one person answers despite efforts to try and keep
the discussion alive and/or revive it. What should one do in that case?
Writing a patch just to throw it away later because something's
fundamentally broken (or unnacceptable) seems silly if people could have
just looked at the original -HACKERS post and said "this can't possibly
work with your current design".

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-09-15 15:20:20 Re: logical changeset generation v6
Previous Message Kevin Grittner 2013-09-15 14:52:23 Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE