On Sep 7, 2013, at 6:54, Steve Atkins wrote:
> On Sep 6, 2013, at 9:37 PM, François Beausoleil wrote:
>
>> Le 2013-09-07 à 00:29, Steve Atkins a écrit :
>>
>>> If I have a partitioned table that has some range constraints that look
>>> kinda like they're intended for constraint exclusion, but
On 07/09/2013 01:34, Berend Tober wrote:
> Peter Geoghegan wrote:
>> On Thu, Sep 5, 2013 at 8:22 AM, Merlin Moncure
>> wrote:
>>> I'm still partial to this guy:
>>>
>>> http://www.commandprompt.com/images/mammoth_versus_dolphin_500.jpg
>>
>>
>> I dislike that image, and always have. ...
>
> I agr
Dear all
I'm developing a new type, and want to have hash index on it.
I must write a hash function for the new type, according to the PG manual,
section 35.14.3.
However, there is no example for this function. Actually signature of the
hash support function
would be sufficient for me.
Any help a
On Sat, Sep 7, 2013 at 7:01 PM, Raymond O'Donnell wrote:
> On 07/09/2013 01:34, Berend Tober wrote:
>> Peter Geoghegan wrote:
>>> On Thu, Sep 5, 2013 at 8:22 AM, Merlin Moncure
>>> wrote:
I'm still partial to this guy:
http://www.commandprompt.com/images/mammoth_versus_dolphin_500.
On Sat, Sep 7, 2013 at 6:28 AM, Janek Sendrowski wrote:
> Do you know the destination. I cant find it.
Here it is:
$ find . -name "*.[c|h]" | xgrep MAX_LEVENSHTEIN_STRLEN
./contrib/fuzzystrmatch/levenshtein.c:#define MAX_LEVENSHTEIN_STRLEN255
./contrib/fuzzystrmatch/levenshtein.c:if (m
Alban Hertroys writes:
> On Sep 7, 2013, at 6:54, Steve Atkins wrote:
>>> If I have a partitioned table that has some range constraints that look
>>> kinda like they're intended for constraint exclusion, but aren't quite
>>> non-overlapping, will that break anything?
> Next to that, putting da
Soroosh Sardari writes:
> I'm developing a new type, and want to have hash index on it.
> I must write a hash function for the new type, according to the PG manual,
> section 35.14.3.
> However, there is no example for this function. Actually signature of the
> hash support function
> would be suf
2013-09-06 09:57 keltezéssel, Boszormenyi Zoltan írta:
2013-09-06 02:57 keltezéssel, Wang, Jing írta:
Hi,
ECPG don't support the following scenario:
char cur_name = "cur1";
EXEC SQL DECLARE :cur_name CURSOR FOR ...
EXEC SQL OPEN :cur_name;
EXEC SQL FETCH cur1 INTO...
...
EXEC SQL CLOSE :
On Sep 7, 2013, at 7:20 AM, Tom Lane wrote:
> Alban Hertroys writes:
>> On Sep 7, 2013, at 6:54, Steve Atkins wrote:
If I have a partitioned table that has some range constraints that look
kinda like they're intended for constraint exclusion, but aren't quite
non-overlapping,
