Re: Posting to pgsql-hackers

Hi Danial,

Please see the bottom of this post...

On 19/02/13 16:56, Daniel Wood wrote:
> I believe my question, posted to pgsql-novice just after this post, is
> an actual bug/feature request. However, there is a rule "You must try
> elsewhere first!".
>
> I suspect the reason for the pgsql-hackers RULE is so that newbies,
> who may not research if a question has been asked before, don't waste
> the time of developers. The same thing applies to reporting bugs
> already reported. You should do your homework.
>
> I suspect the real rule is that:
> Before posting to pgsql-hacker you either need to ask elsewhere
> first or you better research the issue first to see if the problem has
> already been answered or the bug already been reported. It you make
> too many mistakes it will be frowned upon. As it should be.
>
> I just wanted to see if "common sense" was the real rule. I've just
> joined the PG community 3 hours ago and want to get off on the right
> foot. However, I've been deep in DB internals for 18+ years so only
> some of my questions will be off target.
>
> Thanks, I'll probably do what is probably right and adjust as I get
> slapped around. :-)
>
>
> On 02/18/2013 07:26 PM, Bruce Momjian wrote:
>> On Mon, Feb 18, 2013 at 05:41:10PM -0800, Daniel Wood wrote:
>>> First PG post ever. Slap me if you need to.
>>>
>>> How long should I wait on a response after I "try elsewhere first"
>>> before I can post a question to pgsql-hackers? I'm just trying to
>>> not get off to a bad start.
>>>
>>> My real question to follow.
>> Did you ask on general or novice? If you didn't get an answer on
>> general, I would try that. hackers is really for bugs and feature
>> stuff.
>>
>
>
>

The policy on this lists: is to post at the bottom of the post- like I
what I have done here.

Cheers,
Gavin

<slaps Daniel hard>
<looks at wrist>
<wanders off, howling in pain>