Skip site navigation (1) Skip section navigation (2)

Re: effective_cache_size vs units

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Dunstan <pgsql(at)tomd(dot)cc>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: effective_cache_size vs units
Date: 2006-12-20 16:26:19
Message-ID: 4589642B.4050200@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut wrote:
> Am Mittwoch, 20. Dezember 2006 13:42 schrieb Tom Dunstan:
>   
>> I suppose we should think about mysql refugees at some point, though. I
>> wonder what they do. The documentation is silent on the matter (and all
>> their examples are in lower case). Mysql is generally case insensitive,
>> right?
>>     
>
> Maybe you can make sense of this, but I can't ...
>
>
>   
[lots of amusing non-orthogonal braindead stuff ...]
>
> Better not imitate that.
>
>   

The MySQL treatment of enums is generally quite reprehensible. The 
proposed patch by contrast fits quite well into our existing type 
system, I think. MySQL users migrating will have a bit of work to do.

I don't think their experience has much to teach us (except how not to 
do enums). We should decide on case sensitivity without having reference 
to it.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Chris BrowneDate: 2006-12-20 16:38:51
Subject: Stats Collector Oddity
Previous:From: Tom LaneDate: 2006-12-20 16:24:02
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group