[ADMIN] Upgrade from 9.0.5 to 9.1.1 - Problems with citext indexes

for your help. Rudolf van der Leeden Scoreloop, Germany A subsidiary of Research in Motion (RIM)

Re: [ADMIN] Upgrading DBs with type=citext from 9.0.5 to 9.1.1 using pg_upgrade and create extension

Hi Tom, This patch seems to fix the case for me: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=94bdb198813b079467d7ed07c6f72ac896da7161 YES. This patch fixes the citext upgrade problem. With the modified share/extension/citext--unpackaged--1.0.sql file just run: CREATE

[ADMIN] Upgrading DBs with type=citext from 9.0.5 to 9.1.1 using pg_upgrade and create extension

Hi, we are running into a problem with the following upgrade scenario: Current DB (9.0.5, 300G) is using a table with 2 citext columns and indexes on both columns. Using pg_upgrade to move from 9.0.5 to 9.1.1 works OK and is done (without the ANALYZE) in 30s. Because we are using the citext

[ADMIN] How to find the primary server of a hot standby server?

Hi, quick question to the PG 9 community. I can query a hot standby server if recovery is still active using the administration function pg_is_in_recovery(). Is there also a way to query for the 'primary server', i.e. which server is delivering the WAL records? I'd like to monitor a bunch of

Re: [ADMIN] Create Index Performance Issue

Tom, your hint was 100% correct. BINGO! The setting of lc_locale and lc_ctype was 'en_us' instead of 'C' as on the other machine. Now it works perfectly OK and with identical execution times on both machines. Thanks for your help and best regards, Rudolf VanderLeeden Am 04.06.2008 um

[ADMIN] Create Index Performance Issue

Hi, I'm currently testing a 25G Postgres 8.3.0 database on Apple Xserve/ Intel with Mac OSX 10.5 (Leopard). There are two identical machines with identical configurations (hw and sw). Running a pg_restore of a binary backup file (3.8 GB) on both machines gives the following results: