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

Re: Regression failure on pika caused by CLUSTER rewrite

From: Rémi Zara <remi_zara(at)mac(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Regression failure on pika caused by CLUSTER rewrite
Date: 2010-02-15 12:26:45
Message-ID: 2DAC110C-5D71-45AA-9416-9F611350CBBA@mac.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Le 15 févr. 2010 à 12:52, Greg Stark <stark(at)mit(dot)edu> a écrit :

> In looking through the build farm wreckage caused by fsyncing
> directories I noticed this interesting failure on pika:
>
> ================== pgsql.13659/src/test/regress/regression.diffs
> ===================
> *** /home/pgbuildfarm/workdir/HEAD/pgsql.13659/src/test/regress/ 
> expected/cluster.out    Wed
> Feb  3 00:16:38 2010
> --- /home/pgbuildfarm/workdir/HEAD/pgsql.13659/src/test/regress/ 
> results/cluster.out    Wed
> Feb  3 19:19:06 2010
> ***************
> *** 453,455 ****
> --- 453,457 ----
>  DROP TABLE clstr_2;
>  DROP TABLE clstr_3;
>  DROP USER clstr_user;
> + ERROR:  role "clstr_user" cannot be dropped because some objects  
> depend on it
> + DETAIL:  owner of table pg_temp_9.clstr_temp
>

Hi

I think that was fixed some time ago (see "Fix timing-sensitive  
regression test result..." commit by Tom on 02/03). But pika suffered  
some connectivity issues then and is only now building current HEAD  
again.

Regards,

Rémi Zara 
  

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2010-02-15 12:45:26
Subject: Re: Listen / Notify - what to do when the queue is full
Previous:From: Tim BunceDate: 2010-02-15 12:03:13
Subject: Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl

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