Robert Treat wrote:
> On Monday 30 July 2007 03:47, Dave Page wrote:
>> Joshua D. Drake wrote:
>>> Peter Eisentraut wrote:
>>>> Dave Page wrote:
>>>>> As discussed at the first meeting of what will become the European
>>>>> PostgreSQL Users Group after pgDay in Prato, we now have a mailing
>>>>> list setup at pgsql-eu-general@xxxxxxxxxxxxxxx
>>>>>
>>>>> This is for the European users group, so is not really intended as a
>>>>> technical list but as a place to discuss events, advocacy and other
>>>>> topics relevant to our work in Europe.
>>>> If it's not a general list, why did you name it "general"? That will
>>>> certainly cause confusion. It sounds like -eu-advocacy might have
>>>> been better.
>>> +1 -eu-advocacy seems to make more sense.
>> With all due repect JD, you were not at the meeting at which this was
>> discussed and are presumably unaware that we discussed more than just
>> 'advocacy'. I expect there to be 3 or 4 -eu lists eventually, one of
>> which may well be -advocacy.
>>
>
> *shrug* I wasn't there either, but seems all the emails I have seen reffered
> to it as the "European PostgreSQL Users Group", so I expected it to look more
> like other users groups, ie. eupug@xxxxxxxxxxxxxxx
I was at that meeting and for the record: there is no european
postgresql user group (yet) - so a general list seems vastly appropriate
for discussing "general" european stuff.
If we ever get a european user group we can simply add a list for that
but what we now need is a list to discuss general topics and only time
will tell if we ever need eupug@, pgsql-eu-advocacy@ or nothing at all.
>
>> But for now, I was asked to arrange a general mailing list, which I have
>> done.
>>
>
> Except we already had a general european mailing list, so I'm really not clear
> on what the above is meant for accomplishing.
that list was not running on official infrastructure and only meant as a
short term solution until there was enough momentum and interest to put
it on official infrastructure.
Stefan
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
