Skip site navigation (1) Skip section navigation (2)

Re: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: pgadmin-support(at)postgresql(dot)org
Cc: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>, "Allen Vachon" <avachon(at)e-djuster(dot)com>, "Mark Rollins" <mrollins(at)e-djuster(dot)com>, "Dave Sugden" <dsugden(at)e-djuster(dot)com>, "Benoit Rouleau" <brouleau(at)e-djuster(dot)com>
Subject: Re: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0
Date: 2009-11-16 18:14:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-support
Le vendredi 13 novembre 2009 à 17:09:33, Jean-Pierre Pelletier a écrit :
> To reverse engineer the definition of a text search configuration, pgAdmin
> uses a query with an incomplete ORDER BY such as:
>    (SELECT t.alias FROM pg_catalog.ts_token_type(cfgparser) AS t WHERE
> t.tokid = maptokentype) AS tokenalias,
>    dictname
>    pg_ts_config_map
>    LEFT OUTER JOIN pg_ts_config
>    ON mapcfg=pg_ts_config.oid
>    LEFT OUTER JOIN pg_ts_dict
>    ON mapdict=pg_ts_dict.oid
>    mapcfg = 3743899::oid
>    1;
> The ORDER BY is missing column "mapseqno" from catalog "pg_ts_config_map".
> As explained before, in our case, the problem was only exposed after
> reloading the text search configuration using pg_restore.

Sorry that I didn't find the time to work on this till today. You're right on 
the bug and the fix. I commited your fix, thanks a lot.


In response to

pgadmin-support by date

Next:From: Olivier BouironDate: 2009-11-17 11:02:51
Subject: Autocompletion and Table cell edition problems
Previous:From: Little, DouglasDate: 2009-11-16 18:08:29
Subject: feture request

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group