[BUGS] BUG #4797: Uninstall : impossible to delete some files (base...)

2009-05-08 Thread saudraix
The following bug has been logged online: Bug reference: 4797 Logged by: saudraix Email address: eric.saudr...@laposte.net PostgreSQL version: 8.3 Operating system: Vista SP1 Description:Uninstall : impossible to delete some files (base...) Details: Impossible to de

[BUGS] I used postgresql

2009-05-08 Thread root
at rpm pachage. but , I take server Xen in www.server-linux.info and postgresql install, I couldn't initdb , at www. 'Report bugs to ' you. thanks. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #4797: Uninstall : impossible to delete some files (base...)

2009-05-08 Thread Dave Page
On Fri, May 8, 2009 at 2:10 AM, saudraix wrote: > > The following bug has been logged online: > > Bug reference:      4797 > Logged by:          saudraix > Email address:      eric.saudr...@laposte.net > PostgreSQL version: 8.3 > Operating system:   Vista SP1 > Description:        Uninstall : impo

Re: [BUGS] I used postgresql

2009-05-08 Thread John R Pierce
root wrote: at rpm pachage. but , I take server Xen in www.server-linux.info and postgresql install, I couldn't initdb , at www. 'Report bugs to ' you. thats far too cryptic to answer, I cant even tell what the question is.whats www.server-linux.info, I'm getting a DNS error from that U

[BUGS] BUG #4798: BitMapAnd never works with gin

2009-05-08 Thread Alex
The following bug has been logged online: Bug reference: 4798 Logged by: Alex Email address: a...@xdcom.org PostgreSQL version: 8.3.6 Operating system: rhel5 Description:BitMapAnd never works with gin Details: CREATE TABLE foo ( id serial NOT NULL, name characte

[BUGS] 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Michal Szymanski
Hi, We call DB procedure that select rows with given ID it works as simple SELECT but for future changes we implement as DB procedure (look below for DB listing). Recently we modified columns in table cerber.cerber_accoun and after this modification procedure does not work anymore and it returns 42

[BUGS] Re: 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Michal Szymanski
We use Postgres 8.3.7 on Linux -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #4799: BitMapAnd never works with gin

2009-05-08 Thread Alex
The following bug has been logged online: Bug reference: 4799 Logged by: Alex Email address: a...@xdcom.org PostgreSQL version: 8.3.6 Operating system: rhel5 Description:BitMapAnd never works with gin Details: CREATE TABLE foo ( id serial NOT NULL, name character

[BUGS] BUG #4800: constraint_exclusion could be smarter with bool conversion

2009-05-08 Thread Alex
The following bug has been logged online: Bug reference: 4800 Logged by: Alex Email address: a...@xdcom.org PostgreSQL version: 8.3.6 Operating system: rhel5 Description:constraint_exclusion could be smarter with bool conversion Details: Table "public.foo1" Column

[BUGS] BUG #4801: Performance failure: 600 MB written to each WAL log

2009-05-08 Thread Peter Much
The following bug has been logged online: Bug reference: 4801 Logged by: Peter Much Email address: p...@citylink.dinoex.sub.org PostgreSQL version: 8.2.13 Operating system: FreeBSD 7.2 Description:Performance failure: 600 MB written to each WAL log Details: Server b

Re: [BUGS] BUG #4801: Performance failure: 600 MB written to each WAL log

2009-05-08 Thread Rafael Martinez
Peter Much wrote: > > I perceived it only during "vaccum full" yet, but then a long-running > "vacuum full" on a large table is the only significant activity on the > server. (I know that "vacuum full" may not be really necessary, but > I think it should practically function.) > [..] Hei

Re: [BUGS] 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Pavel Stehule
Hello you have to do vacuum full cerber.cerber_account regards Pavel Stehule 2009/5/8 Michal Szymanski : > Hi, > We call DB procedure that select rows with given ID it works as simple > SELECT but for future changes we implement as DB procedure (look below > for DB listing). Recently we modifie

Re: [BUGS] BUG #4797: Uninstall : impossible to delete some files (base...)

2009-05-08 Thread Dave Page
On Fri, May 8, 2009 at 2:17 PM, eric.saudraix wrote: > > Thanks for your quick reply. > > > > I know I have to be the administrator of my data. Indeed, I am the > administrator of my computer. > > On Linux it would not be a problem to find the key that leads to the > problem. > > > > In fact to ex

Re: [BUGS] 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Tom Lane
Michal Szymanski writes: > We call DB procedure that select rows with given ID it works as simple > SELECT but for future changes we implement as DB procedure (look below > for DB listing). Recently we modified columns in table > cerber.cerber_accoun and after this modification procedure does not

Re: [BUGS] BUG #4800: constraint_exclusion could be smarter with bool conversion

2009-05-08 Thread Tom Lane
"Alex" writes: > I wish constraint_exclusion to be smarter with bool conversion so that > 'select * from foo where (mask&5)::bool' can be faster; Don't hold your breath. It's tough enough deriving conclusions from ordinary btree-indexable comparison operators. regards, t

Re: [BUGS] BUG #4801: Performance failure: 600 MB written to each WAL log

2009-05-08 Thread Peter Much
Dear Rafael, I agree with You. And that is actually what I have done up to now, although for a different reason: the amount of WAL logs produced by VACUUM FULL is practically unpredictable and can be much more than the database size, and since that database belongs to the backup system, the backup

[BUGS] Re: 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Michal Szymanski
> you have to do vacuum full  cerber.cerber_account Yes I've made vacuum full - result was the same. Regards Michal Szymanski -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] Re: 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Michal Szymanski
> Exactly what modifications did you make? We have added few new columns and we delete one column. Michal Szymanski http://blog.szymanskich.net -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #4798: BitMapAnd never works with gin

2009-05-08 Thread Tom Lane
"Alex" writes: > CREATE TABLE foo > ( > id serial NOT NULL, > name character varying(32), > nick character varying(32), > gender integer > )WITH (OIDS=FALSE); > CREATE INDEX name_idx > ON foo > USING gin(to_tsvector('english'::regconfig, name)) > WHERE gender = 1; > CREATE INDEX ni

Re: [BUGS] Re: 42804: structure of query does not match error where using RETURN QUERY

2009-05-08 Thread Tom Lane
Michal Szymanski writes: >> Exactly what modifications did you make? > We have added few new columns and we delete one column. [ experiments... ] Hmm, looks like RETURN QUERY isn't too bright about dropped columns in the function result type. I'm not too sure about how hard this is to fix, but

Re: [BUGS] BUG #4801: Performance failure: 600 MB written to each WAL log

2009-05-08 Thread Simon Riggs
On Fri, 2009-05-08 at 12:26 +, Peter Much wrote: > Server becomes very slow while tremendous amounts of data are written > to WAL logs - disk activity log shows 600 MB of effective write > requests before each 16 MB WAL log is archived and recycled. VACUUM FULL does many things, most of them

Re: [BUGS] BUG #4801: Performance failure: 600 MB written to each WAL log

2009-05-08 Thread Peter Much
Dear Simon, On Fri, May 08, 2009 at 07:15:19PM +0100, Simon Riggs wrote: ! > Server becomes very slow while tremendous amounts of data are written ! > to WAL logs - disk activity log shows 600 MB of effective write ! > requests before each 16 MB WAL log is archived and recycled. ! ! VACUUM FULL