On Jun14, 2011, at 07:15 , Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian br...@momjian.us wrote:
No, it does not. Under what circumstances should I issue a suggestion
to reindex, and what should the text be?
It sounds like GIN
On Tue, Jun 14, 2011 at 1:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I'm not sure that pg_upgrade is a good vehicle for dispensing such
advice, anyway. At least in the Red Hat packaging, end users will never
read what it prints, unless maybe it fails outright and they're trying
to debug why.
Robert Haas wrote:
On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug f...@phlo.org wrote:
Note that this restriction was removed in postgres 9.1 which
is currently in beta. However, GIT indices must be re-created
with REINDEX after upgrading from 9.0 to leverage that
improvement.
Does
On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug f...@phlo.org wrote:
Note that this restriction was removed in postgres 9.1 which
is currently in beta. However, GIT indices must be re-created
with
Robert Haas wrote:
On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug f...@phlo.org wrote:
Note that this restriction was removed in postgres 9.1 which
is currently in beta. However, GIT indices must
Robert Haas robertmh...@gmail.com writes:
On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian br...@momjian.us wrote:
No, it does not. Under what circumstances should I issue a suggestion
to reindex, and what should the text be?
It sounds like GIN indexes need to be reindexed after upgrading from
I am using pg_trgm for spelling correction as prescribed in the
documentation. But I see that it does not work for unicode sring. The
database was initialized with utf8 encoding and the C locale.
Here is the table:
\d words
Table public.words
Column | Type | Modifiers
Hi
Next time, please post questions regarding the usage of postgres
to the -general list, not to -hackers. The purpose of -hackers is
to discuss the development of postgres proper, not the development
of applications using postgres.
On Jun12, 2011, at 13:33 , Sushant Sinha wrote:
I am using
On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug f...@phlo.org wrote:
Note that this restriction was removed in postgres 9.1 which
is currently in beta. However, GIT indices must be re-created
with REINDEX after upgrading from 9.0 to leverage that
improvement.
Does pg_upgrade know about this?