Josh Berkus wrote:
Where is the most current version of this patch? I want to test it on TPCE,
but there seem to be 4-5 different versions floating around, and the patch
tracker hasn't been updated.
It would be the ldc-justwrites-2.patch:
Hello
I found simply function which is buggy, but it crashes server
CREATE OR REPLACE FUNCTION test(anyarray)
RETURNS anyarray AS $$
SELECT $1[k]; -- k is bug
$$ LANGUAGE sql;
SELECT test(array[10,2,3]);
Correct function works well.
Regards
Pavel Stehule
Output:
postgres=# select
On Sun, 17 Jun 2007, Bruce Momjian wrote:
I have completed my first pass over the tsearch documentation:
http://momjian.us/expire/fulltext/HTML/sql.html
They are from section 14 and following.
I have come up with a number of questions that I placed in SGML comments
in these files:
Pavel Stehule [EMAIL PROTECTED] writes:
SGVsbG8KCkkgZm91bmQgc2ltcGx5IGZ1bmN0aW9uIHdoaWNoIGlzIGJ1Z2d5
LCBidXQgaXQgY3Jhc2hlcyBzZXJ2ZXIKCkNSRUFURSBPUiBSRVBMQUNFIEZV
TkNUSU9OIHRlc3QoYW55YXJyYXkpClJFVFVSTlMgYW55YXJyYXkgQVMgJCQK
ICBTRUxFQ1QgJDFba107IC0tIGsgaXMgYnVnCiQkIExBTkdVQUdFIHNxbDsK
...
Please don't send HTML-only email :-(
I am sorry. It's stupid web mail. I didn't know so my messages was in
html format.
Anyway, seems I broke this a couple months ago. Fixed, thanks
for the report.
regards, tom lane
---(end of
Pavel Stehule wrote:
Please don't send HTML-only email :-(
I am sorry. It's stupid web mail. I didn't know so my messages was in
html format.
Actually, it looks to me like it was sent as plain text encoded as
base64. I got:
Content-Type: text/plain; charset=UTF-8; format=flowed
On 6/17/07, Andrew Dunstan [EMAIL PROTECTED] wrote:
Pavel Stehule wrote:
Please don't send HTML-only email :-(
I am sorry. It's stupid web mail. I didn't know so my messages was in
html format.
Actually, it looks to me like it was sent as plain text encoded as
base64. I got:
Andrew Dunstan wrote:
Now that we've fixed the partial/interleaved log line issue, I have
returned to trying toi get the CSV log patch into shape. Sadly, it still
needs lots of work, even after Greg Smith and I both attacked it, so I
am now going through it with a fine tooth comb.
One
FAST PostgreSQL wrote:
Andrew Dunstan wrote:
Now that we've fixed the partial/interleaved log line issue, I have
returned to trying toi get the CSV log patch into shape. Sadly, it
still needs lots of work, even after Greg Smith and I both attacked
it, so I am now going through it with a
Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
A message entitled Having Fun With PostgreSQL was posted to Bugtraq
today. I haven't read through the paper yet so I don't know if the
author discusses security problems that need attention or if the
article is more like a compilation of
The world rejoiced as [EMAIL PROTECTED] (Joshua D. Drake) wrote:
Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
A message entitled Having Fun With PostgreSQL was posted to Bugtraq
today. I haven't read through the paper yet so I don't know if the
author discusses security problems
Christopher Browne wrote:
The world rejoiced as [EMAIL PROTECTED] (Joshua D. Drake) wrote:
Tom Lane wrote:
We've debated #1 before, and a lot of repackagers change it, but I
don't really feel a strong urge to change it in the source distro.
As for #2, that's not a bug, it's intended
Christopher Browne [EMAIL PROTECTED] writes:
The world rejoiced as [EMAIL PROTECTED] (Joshua D. Drake) wrote:
On #1, the fact that we allow trust as default is embarrassing.
This is a case where it takes careful thought to grasp whether there
is a problem or not.
If all we do is to shift the
Heikki Linnakangas [EMAIL PROTECTED] wrote:
Michael Paesold wrote:
Why do you think so? Is it too much risk to adapt the sorted writes? The
numbers shown by ITAGAKI Takahiro looked quite impressive, at least for
large shared_buffers configurations. The reactions where rather
positive,
14 matches
Mail list logo
