Tom Lane wrote:
> Magnus Hagander writes:
>> 2010/1/24 Joe Conway :
>>> Sorry for being thick -- I'm still missing something. I don't understand
>>> why any user program using libpq/PQexec running on Windows does not have
>>> the same issue. Or to put it another way, why does this only apply to
>>
On sön, 2010-01-24 at 20:32 +, Simon Riggs wrote:
> Why do we have a parameter called "default_do_language" when we don't
> have a parameter called "default_language"?
According to the SQL standard, the default language for CREATE FUNCTION
is SQL. Should we implement that?
--
Sent via pgsq
2010/1/25 Peter Eisentraut :
> On sön, 2010-01-24 at 20:32 +, Simon Riggs wrote:
>> Why do we have a parameter called "default_do_language" when we don't
>> have a parameter called "default_language"?
>
> According to the SQL standard, the default language for CREATE FUNCTION
> is SQL. Should
On mån, 2010-01-25 at 08:09 +0100, Pavel Stehule wrote:
> 2010/1/25 Peter Eisentraut :
> > On sön, 2010-01-24 at 20:32 +, Simon Riggs wrote:
> >> Why do we have a parameter called "default_do_language" when we don't
> >> have a parameter called "default_language"?
> >
> > According to the SQL s
2010/1/25 Peter Eisentraut :
> On mån, 2010-01-25 at 08:09 +0100, Pavel Stehule wrote:
>> 2010/1/25 Peter Eisentraut :
>> > On sön, 2010-01-24 at 20:32 +, Simon Riggs wrote:
>> >> Why do we have a parameter called "default_do_language" when we don't
>> >> have a parameter called "default_langua
Simon Riggs wrote:
> On Sat, 2010-01-23 at 21:40 +, Greg Stark wrote:
>> On Sat, Jan 23, 2010 at 8:28 PM, Simon Riggs wrote:
>>> What is your proposed way of handling buffer pin deadlocks? That will be
>>> acceptable and working to some extent in the next week?
>>>
>>> Wait forever isn't alway
101 - 106 of 106 matches
Mail list logo