Magnus Hagander wrote:
> I think the item:
> o Check WSACancelBlockingCall() for interrupts [win32intr]
>
> could be removed from the TODO (incl detail). It's a bug in the old sysv
> semaphore emulation code, that was replaced with native semaphore code
> back in april 2006 (the bug report i
On Jul 3, 2007, at 3:36 PM, Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
On Mon, Jul 02, 2007 at 11:19:12PM -0400, Tom Lane wrote:
Is there a reason to say anything beyond "use autovac"?
There is; I know that things like web session tables aren't
handled very
well by autovacuum
2007/7/7, Bruce Momjian <[EMAIL PROTECTED]>:
FYI, I have massively reorganized the text search documentation and it
is getting closer to something I am happy with:
http://momjian.us/expire/fulltext/HTML/textsearch.html
The following is the result of me proofreading, mainly searching f
On 7/7/2007 11:40 AM, Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Jan Wieck wrote:
You mean as a second, optional argument? Good idea.
I think it should only be one argument, with the units being part of the
variable value, if any.
No, because that makes it hard to do thin
On Sat, 7 Jul 2007, Tom Lane wrote:
I think you lost at least one patch in this change, viz
"Maintaining cluster order on insert"
It's back. I double-checked: 40 patches before, 40 now. I thought that
I was safe editing this bugger at 5am, but Stefan was watching; I think I
lost that one
On Thu, Jul 05, 2007 at 12:26:45PM +0100, Heikki Linnakangas wrote:
> Kenneth Marshall wrote:
> >I definitely agree with Tom's assessment. If we cannot need to make the
> >hash index as performant as it is in theory, none of the other refinements
> >are worth it. You would need to use BTree if you
Hi,
I am mailing on behalf of the Database Systems Lab, Indian Institute of
Science(IISc), Bangalore, India. We have implemented three new operators
internal to the PostgreSQL 8.1.2 engine in order to support queries on
multilingual data(english and hindi as of now). It can be extended to
support
Gregory Stark <[EMAIL PROTECTED]> writes:
> At the least this sounds like an unfriendly error message:
> postgres=# select 1 order by 1;
> ERROR: could not find pathkey item to sort
Definitely a bug, since it works in all existing releases.
Thanks for the report.
regards
At the least this sounds like an unfriendly error message:
postgres=# select 1 order by 1;
ERROR: could not find pathkey item to sort
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if post
Greg Smith <[EMAIL PROTECTED]> writes:
> I'm not sure what order the patches at at
> http://developer.postgresql.org/index.php/Todo:PatchStatus were listed in
> before, but it seemed to me they'd be a whole lot more useful sorted by
> the remaining actions on them--so that's what I did.
I think
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Jan Wieck wrote:
>> You mean as a second, optional argument? Good idea.
> I think it should only be one argument, with the units being part of the
> variable value, if any.
No, because that makes it hard to do things like "sleep for a small
random n
Gregory Stark <[EMAIL PROTECTED]> writes:
> When we checkpoint we write out all dirty buffers. But ISTM we don't really
> need to write out buffers which are dirty but which have an LSN older than the
> previous checkpoint. Those represent buffers which were dirtied by a
> non-wal-logged modificati
I think the item:
o Check WSACancelBlockingCall() for interrupts [win32intr]
could be removed from the TODO (incl detail). It's a bug in the old sysv
semaphore emulation code, that was replaced with native semaphore code
back in april 2006 (the bug report is from feb 2006).
AFAIK the prob
Greg Smith wrote:
> I'm not sure what order the patches at at
> http://developer.postgresql.org/index.php/Todo:PatchStatus were listed in
> before, but it seemed to me they'd be a whole lot more useful sorted by
> the remaining actions on them--so that's what I did.
Yep, much better. I think w
Greg Smith wrote:
> I'm not sure what order the patches at at
> http://developer.postgresql.org/index.php/Todo:PatchStatus were listed
> in before, but it seemed to me they'd be a whole lot more useful sorted
> by the remaining actions on them--so that's what I did.
well the original order was bas
Jan Wieck wrote:
> You mean as a second, optional argument? Good idea.
I think it should only be one argument, with the units being part of the
variable value, if any.
>us = microseconds
>ms = milliseconds
>s = seconds (default)
>
>\sleep {value|:variable} [us|ms|s]
--
Peter Ei
I'm not sure what order the patches at at
http://developer.postgresql.org/index.php/Todo:PatchStatus were listed in
before, but it seemed to me they'd be a whole lot more useful sorted by
the remaining actions on them--so that's what I did.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmit
On Fri, 6 Jul 2007, Heikki Linnakangas wrote:
To strike a balance between cleaning buffers ahead of possible bursts in the
future and not doing unnecessary I/O when no such bursts come, I think a
reasonable strategy is to write buffers with usage_count=0 at a slow pace
when there's no buffer a
18 matches
Mail list logo
