[ADMIN] refreshing prepared statements after index rebuild

Hi, we have a corrupt index (size=20GB) and are about to create a new index parallel to the corrupted index. the index is running on a heavyly used online database with oltp character. The question is what's the softest way to switch to the new index. there are several application servers, webapp

[ADMIN] analyze anomalie

Hi, today i found an anomalie running analyze verbose the output was simply "ANALYZE", which tells me that analyze was running successfully. but there was no verbose output. and in the statistics table was no updated last_analyze column. I run that automaticly in the background or manually in a

Re: [ADMIN] analyze anomalie

Hi Tom, I was running the command as user postgres (default). The "vacuum anlyze" and the "analyze" I run as the same user. client_min_messages is still set to default in the server config. reagrds, Uwe 2009/6/29 Tom Lane > Uwe Bartels writes: > > toda

[ADMIN] feature in 8.3 - Automatically re-plan cached queries when table definitions change or statistics are updated

Hi, today i run into an issue with postgres 8.3.4 and slony 1.2.15 on solaris 10. I found hundres of errors in my postgres log file: ERROR: cache lookup failed for type 177473925 These errors came up directly after dropping a slony cluster completely. The relevant slony commmands were: drop set

[ADMIN] vacuum + autovacuum

Hi, i have some questions regarding - behavior of vacuum and autovacuum after changing configuration and - interaction between those two i change the vacuum_cost_delay parameter to 0 in postgresql.conf and reloaded the server (sighup). does that have an immediate effect on running vaccuums and au

[ADMIN] blocking automatic vacuum

e a configuration issue? best regards, Uwe Uwe Bartels Systemarchitect - Freelancer mailto: uwe.bartels at gmail.com

Re: [ADMIN] blocking automatic vacuum

Grittner wrote: > Uwe Bartels wrote: > > > last ween i've seen a blocking "automatic vacuum". > > What does SELECT version(); show? > > -Kevin >

Re: [ADMIN] blocking automatic vacuum

ystem usage: CPU 0.02s/0.01u sec elapsed 12354.51 sec other statements on that table are - delete ... where timstamp < - select * from but, that's it. If you wish i can send you the complete log for that day. best regards, Uwe On 22 June 2010 16:48, Tom Lane wrote: > Uwe

Re: [ADMIN] blocking automatic vacuum

frequented tables. what exactly happens during anti-wraparond vacuum in terms of locking and for how long? best regards, Uwe On 22 June 2010 16:48, Tom Lane wrote: > Uwe Bartels writes: > > last ween i've seen a blocking "automatic vacuum". > > as i understood,

[ADMIN] problem with rules

Hi, i'm trying to reorganize a big table without having a downtime at all. I'm trying to realize this via partitioning and rules. - step 1 preparation create table uglybloatedtable (id bigserial, textfield text, primary key(id)); INSERT INTO uglybloatedtable (textfield) values (''); INSERT INTO u

[ADMIN] docs log_executor_stats

Hi, is there any documentation about the output of "log_executor_stats=on" out there? it seems quite intuitiv on the first glance, but if you are at the point reading this output, you are already quite deep in the system and have problems. And I need to know what each of the numbers really no

[ADMIN] problem with an account name 'replication' for streaming replication

Hi, when I used the postgres login 'replication' as the account for streaming replication I get the following error message: 2011-03-28 18:06:47 CEST FATAL: could not connect to the primary server: FATAL: no pg_hba.conf entry for replication connection from host "172.16.56.122", user "replicatio

Re: [ADMIN] problem with an account name 'replication' for streaming replication

On 30 March 2011 22:43, raghu ram wrote: > > > On Thu, Mar 31, 2011 at 12:07 AM, Uwe Bartels wrote: > >> Hi, >> >> when I used the postgres login 'replication' as the account for streaming >> replication I get the following error message: >> 2

Re: [ADMIN] problem with an account name 'replication' for streaming replication

On 31 March 2011 04:53, Fujii Masao wrote: > On Thu, Mar 31, 2011 at 3:37 AM, Uwe Bartels > wrote: > > when I used the postgres login 'replication' as the account for streaming > > replication I get the following error message: > > 2011-03-28 18:06:47 CES

[ADMIN] using explain output within pgsql

Hi, I'm starting up a datawarehouse with patitioning. my etl processes write directly into the corresponding partitions instead of using triggers. The reports I run in the datawarehouse are stored in a cache within the same database. Now I'd like to store besides the results the dependencies to t

Re: [ADMIN] [SQL] using explain output within pgsql

Hi Adrian, yes. but this is not the cause for the syntax error. thanks, Uwe On 10 July 2011 21:20, Adrian Klaver wrote: > On Sunday, July 10, 2011 11:54:10 am Uwe Bartels wrote: > > Hi, > > > > I'm starting up a datawarehouse with patitioning. > > my etl p

Re: [ADMIN] [SQL] using explain output within pgsql

Hi Pavel, I don't believe it. the second answer on sunday evening within half an hour. and it works. excellent!!! best regards, Uwe On 10 July 2011 21:20, Pavel Stehule wrote: > Hello > > > > 2011/7/10 Uwe Bartels : > > Hi, > > > > I'm starting

Re: [ADMIN] [SQL] using explain output within pgsql

Hi Pavel, is it posible to get this running even with dynamic sql? I didn't write that. I'm using execute to run this create table best regards, Uwe On 10 July 2011 21:20, Pavel Stehule wrote: > Hello > > > > 2011/7/10 Uwe Bartels : > > Hi, > > >

[ADMIN] enterprisedb package and pam on debian

Hiho, I'm running the package 9.0.7 from enterprisedb and have some problems getting the pam module to work on debian. pam basically works - i just configured a more secure password policy. the enterprisedb package has pam support included. at least i see with ldd that i knows the pam library.