Andreas Gaab wrote:
> Dear all,
>
> after an WAL-restore of our Postgres DB, we observe seemingly wrong values of
> our sequences.
This is normal. The reason is that sequences are WAL-logged in chunks,
not single values (otherwise they'd be too slow). So after recovery,
the values jump to the
Hi,
This is more of a general schema design, any advice is much
appreciated.
I have a Organization table. Nearly every other table in the schema
is related to this Org table in some way. So, some tables may be 3 or
4 tables 'away' from the Org table. In order to filter by the org_id,
I need to
You can avoid stemming by using 'simple' instead of 'english' as the
language of the words in to_tsvector (which is a little more awkward
than the cast).
"There are no stop words for the simple dictionary. It will just
convert to lower case, and index every unique word.
SELECT to_tsvector(
On Thu, Apr 29, 2010 at 01:13:40PM -, sandeep prakash dhumale wrote:
> Hello All,
>
> I am trying to get tsearch working for my application but I am facing a
> problem when alphabet 'Y' is the in the tsquery.
>
> can anyone please share some light on it.
>
>
> # SELECT 'hollywood'::tsvector
Andreas Gaab writes:
> after an WAL-restore of our Postgres DB, we observe seemingly wrong values of
> our sequences.
> We have two postgres server (8.4) with pgpool in replication mode.
> Recently we tested our restore procedure and played our WAL-files into the
> second server after an old f
Dear all,
after an WAL-restore of our Postgres DB, we observe seemingly wrong values of
our sequences.
We have two postgres server (8.4) with pgpool in replication mode.
Recently we tested our restore procedure and played our WAL-files into the
second server after an old file-system backup was
