On Wednesday, April 10, 2013, Nik Tek wrote:
> Hi Bambi,
>
> Thank you the prompt reply.
>
> This table is very volatile, lot of inserts/updates happen on this
> tables(atleast 20~30 inserts/min).
>
That number of inserts per minute is not all that many. I suspect that you
have sessions which ar
Julian Glass wrote:
> You might want to explicitly reference tables (and alias).
I agree. I find that the best defense against several classes of
silent misbehavior is to alias all table references and qualify all
column references with the alias -- or use a tool which does this
for you.
--
Ke
Tom Lane wrote:
> However I've got to say that both of those side-effects of
> exclusive-lock abandonment seem absolutely brain dead now that I
> see them. Why would we not bother to tell the stats collector
> what we've done? Why would we think we should not do ANALYZE
> when we were told to?
Jeff Janes writes:
> I believe the rationale was so that an autovacuum would still look like it
> was needed, and get fired again the next naptime, so that it could continue
> with the truncation attempts. (Rather than waiting for 20% turnover in the
> table before trying again). I'm not convinc
On 12/04/13 10:17, Craig James wrote:
> Hmmm the subselect is invalid, but not rejected. The outer select
> returns every row in the customer_order_matches table. This seems
> pretty wrong. This is PG 9.2.1 running on Ubuntu.
>
>
> db=> select count(1) from customer_order_matches where
> cust
On Thursday, April 11, 2013, Tom Lane wrote:
>
> [ pokes around ... ] You certain 9.2.3 didn't do this too? This
> appears to be an intentional behavior of the 9.2.3 patch that made it
> cancel truncation when there were conflicting lock requests:
>
> /*
> * Report results to the stats
Craig James writes:
> Hmmm the subselect is invalid, but not rejected. The outer select
> returns every row in the customer_order_matches table. This seems pretty
> wrong. This is PG 9.2.1 running on Ubuntu.
> db=> select count(1) from customer_order_matches where
> customer_order_item_id i
Hmmm the subselect is invalid, but not rejected. The outer select
returns every row in the customer_order_matches table. This seems pretty
wrong. This is PG 9.2.1 running on Ubuntu.
db=> select count(1) from customer_order_matches where
customer_order_item_id in (select customer_order_item_
Mike Broers writes:
> After patching to 9.2.4 I am noticing some mysterious behavior in my
> nightly vacuumdb cron job.
> I have been running vacuumdb -avz nightly for a while now, and have a
> script that tells me the next day if all the tables in pg_stat_user_tables
> have been vacuumed and ana
Keith Ouellette writes:
> I am realatively new to PostgreSQL. I have two servers in a Master/Slave
> relationship using WAL as the replication method. I have what I hope to be an
> easy question. If the Master goes down and before the slave is promoted,
> there may be a case where a log file ma
I am realatively new to PostgreSQL. I have two servers in a Master/Slave
relationship using WAL as the replication method. I have what I hope to be an
easy question. If the Master goes down and before the slave is promoted, there
may be a case where a log file may not have been shipped to the sl
After patching to 9.2.4 I am noticing some mysterious behavior in my
nightly vacuumdb cron job.
I have been running vacuumdb -avz nightly for a while now, and have a
script that tells me the next day if all the tables in pg_stat_user_tables
have been vacuumed and analyzed in the last 24 hours.
Si
*Would you mind providing more insights on type of replication that is in
use as email states that switch performed from slave to master ?*
*
*
*Initial glance points towards catalog corruptions however would like to
understand the replication methodology used here..*
*Thanks & Regards,*
*** *
*Pr
I'm sorry,I forgot to attach the log info:
WARNING: pgstat wait timeout
SELECTWARNING: pgstat wait timeout
SELECTWARNING: corrupted statistics file "pg_stat_tmp/pgstat.stat"
VACUUMWARNING: pgstat wait timeout
-- Original --
From: "Vasilis Ventirozos";
Dat
>
> 2) we can go with single instance of PostgreSQL service which would
> then contain 30.000 database tables.
>
> So, consider this purely theoretical discussion - does anyone here have
> experience of running PostgreSQL service with large number of database
> tables (couple of thousands up to
Dear all,
Please help me.
I know this is postgres-admin mail list, it is not for the discussion of
pgpool.
I'm sorry to post questions related to pgpool.
I have a problem like this:
<<
I have a temporary table is used as a literal in View objects.
in Master/Slave Mode (Pgpool): how to detec
16 matches
Mail list logo
