Tom Lane wrote:
Aside from the how did this happen puzzle, the real point of any
investigation of course ought to be whether we can make heap_page_prune
more robust. At the very least it's undesirable to be leaving the page
in a state where VACUUM FULL will decide it can't shrink.
I'm as
Tom Lane píše v pá 13. 02. 2009 v 16:54 -0500:
Zdenek Kotala zdenek.kot...@sun.com writes:
I attached fix for regression tests and Czech locale. It is not complete
yet, because I fighting with foreign_data test. But it fix three other
tests.
As per buildfarm member gothic_moth, this
Tom Lane wrote:
The real problem I'm having with it is that I don't believe the
use-case. The normal scenario for a listener is that you LISTEN and
then you sit there waiting for events. In the above scenario, a client
thread would only be able to receive events when it actively had control
of
KaiGai Kohei wrote:
If you set up a VM from scratch, Fedora enables to install
via remote repository using minimum bootable image.
http://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/iso/
I don't think it is not a essential for you to resolve troubles
related to
On Thursday 12 February 2009 11:50:26 Joshua D. Drake wrote:
On Thu, 2009-02-12 at 11:47 -0500, Andrew Dunstan wrote:
Joshua D. Drake wrote:
On Thu, 2009-02-12 at 11:32 -0500, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
The implementation is actually different across
It would be very useful if there were an option to have ts_headline append
ellipses before or after a result fragement based on the position of the
fragment in the source document. For instance, when running ts_headline(doc,
query) it will correctly return a fragment with words highlighted,
I think we currently do that. We add ellipses only when we encounter a
new fragment. So there should not be ellipses if we are at the end of
the document or if that is the first fragment (includes the beginning of
the document). Here is the code in generateHeadline, ts_parse.c that
adds the
Interesting, it could be that you already do it, but the documentation makes
no reference to a fragment delimiter, so there's no way that I can see to
add one. The documentation for ts_headline only lists StartSel, StopSel,
MaxWords, MinWords, ShortWord, and HighlightAll, there appears to be no
Sushant Sinha sushant...@gmail.com writes:
I think we currently do that.
... since about four months ago.
2008-10-17 14:05 teodor
* doc/src/sgml/textsearch.sgml, src/backend/tsearch/ts_parse.c,
src/backend/tsearch/wparser_def.c, src/include/tsearch/ts_public.h,
The documentation in 8.4dev has information on FragmentDelimiter
http://developer.postgresql.org/pgdocs/postgres/textsearch-controls.html
If you do not specify MaxFragments 0, then the default headline
generator kicks in. The default headline generator does not have any
fragment delimiter. So it
Yes, you are correct in your assumption that I'm looking for a single
fragment to also have the option to add a fragment delimiter based on its
position in the document.
-Original Message-
From: Sushant Sinha [mailto:sushant...@gmail.com]
Sent: Saturday, February 14, 2009 4:41 PM
To:
No worries, I'm going to start playing around with the dev branch now, but
in any case, your previous response is still applicable, and the question
regarding the fragment delimiter for the first fragment is still applicable.
It seems that without that, I would still have the same problem with the
Sorry ... I thought you were running the development branch.
-Sushant.
On Sat, 2009-02-14 at 16:34 -0500, Tom Lane wrote:
Sushant Sinha sushant...@gmail.com writes:
I think we currently do that.
... since about four months ago.
2008-10-17 14:05 teodor
*
On Sat, Feb 14, 2009 at 12:46 AM, KaiGai Kohei kai...@kaigai.gr.jp wrote:
Now I checked the repository of Ubuntu, however, I can find
several matters to build/run SE-PostgreSQL.
- The default security policy is quite old.
Is does not contain SE-PostgreSQL support which is merged
at the
14 matches
Mail list logo
