Re: [BUGS] BUG #7740: Installation cannot fine msi file
Hi Do you see this on Win7 32bit or 64bit? Can you please send the installation logs from your temp folder? On Sat, Dec 8, 2012 at 4:35 AM, wrote: > The following bug has been logged on the website: > > Bug reference: 7740 > Logged by: Al Chirico > Email address: al_chir...@hotmail.com > PostgreSQL version: 9.2.2 > Operating system: Win 7 Pro > Description: > > I am getting the following Stack Builder error message during installation: > > "Failed to open > > http://ftp.postgresql.org/pub/projects/pgFoundry/stackbuilder/PgOleDB-1.0.0.20.msi > " > > > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- Sandeep Thakkar Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91.20.30589514 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
On Sun, Dec 9, 2012 at 11:13 PM, Alvaro Herrera wrote: > Tom Lane wrote: >> >> spam_ea...@gmx.net writes: >> > postgres=# create user testuser with password 'secret'; >> > CREATE ROLE >> > postgres=# create database testdb owner testuser; >> > CREATE DATABASE >> > testdb=> drop owned by testuser; >> > ERROR: unrecognized object class: 1262 >> >> I can reproduce this in all versions back to 8.3. In 8.2, the role's >> ownership of the database is silently ignored, which I think was the >> design intention. I doubt that we want DROP OWNED dropping whole >> databases. At most maybe we should raise a NOTICE? > > I broke it recently: fe3b5eb08 > whatever is the right way to solve this... shouldn't we do something similar in shdepReassignOwned() in which we are still ignoring shared objects? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- 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 #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Tom Lane wrote: > > spam_ea...@gmx.net writes: > > postgres=# create user testuser with password 'secret'; > > CREATE ROLE > > postgres=# create database testdb owner testuser; > > CREATE DATABASE > > testdb=> drop owned by testuser; > > ERROR: unrecognized object class: 1262 > > I can reproduce this in all versions back to 8.3. In 8.2, the role's > ownership of the database is silently ignored, which I think was the > design intention. I doubt that we want DROP OWNED dropping whole > databases. At most maybe we should raise a NOTICE? I broke it recently: fe3b5eb08 Got a one day old guy at home, can't look at this for at least a week, sorry. -- Álvaro Herrerahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- 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] init_htab causes SIGFPE (or worse) due to miscalculation for large nbuckets
Jeff Davis writes: > If nbuckets is around 2^30+1, which can happen if work_mem is very high, > then: > nbuckets = 1 << my_log2(lnbuckets); > ends up as 1 << 31, which is negative, leading to a SIGFPE on my > machine, but I think it can also lead to an infinite loop or a crash > (after corrupting the HASHHDR). > ... > I think we should just cap nbuckets at 1 << 30 in init_htab. Yeah. After looking at other uses of my_log2, it seems like hash_estimate_size and hash_select_dirsize probably should also bound their inputs to avoid overflow of 1 << my_log2() calculations. Alternatively, maybe we should hack my_log2 to do that bounding. As-is, it seems like trouble waiting to happen. This won't protect init_htab, which needs the shift result to fit in int not long. But my_log2 is just plain broken for inputs larger than LONG_MAX/2, anyway. regards, tom lane -- 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: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Tom Lane wrote on 09.12.2012 17:43: spam_ea...@gmx.net writes: postgres=# create user testuser with password 'secret'; CREATE ROLE postgres=# create database testdb owner testuser; CREATE DATABASE testdb=> drop owned by testuser; ERROR: unrecognized object class: 1262 I can reproduce this in all versions back to 8.3. In 8.2, the role's ownership of the database is silently ignored, which I think was the design intention. I doubt that we want DROP OWNED dropping whole databases. At most maybe we should raise a NOTICE? Just for clarification, this is how it worked in 9.1 (and I'm pretty sure in 9.2.1 as well): First I create a testuser and the database: C:\>psql -X -U postgres postgres psql (9.1.3) postgres=# create database testdb owner testuser; ERROR: role "testuser" does not exist postgres=# create user testuser with password 'secret'; CREATE ROLE postgres=# create database testdb owner testuser; CREATE DATABASE postgres=# \q Then I log in as the testuser, create a table and drop all objects again: C:\>psql -X -U testuser testdb Password for user testuser: psql (9.1.3) testdb=> create table foobar (id integer); CREATE TABLE testdb=> drop owned by testuser; DROP OWNED testdb=> -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] init_htab causes SIGFPE (or worse) due to miscalculation for large nbuckets
If nbuckets is around 2^30+1, which can happen if work_mem is very high, then: nbuckets = 1 << my_log2(lnbuckets); ends up as 1 << 31, which is negative, leading to a SIGFPE on my machine, but I think it can also lead to an infinite loop or a crash (after corrupting the HASHHDR). The only simple way I can reproduce this is with gdb: 1. attach gdb to a session 2. set a breakpoint in ExecInitRecursiveUnion and continue 3. execute in session: set work_mem='100GB'; with recursive r (i) as (select 1 union select i+1 from r where i < 10) select * from r; 4. (gdb) set node->numGroups = (1 << 30) + 1 5. (gdb) continue I think we should just cap nbuckets at 1 << 30 in init_htab. There was a previous fix here: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=299d1716525c659f0e02840e31fbe4dea3 But it assumed that init_htab could deal with INT_MAX. In practice, work_mem will usually be the limiting factor anyway, but not if it's set high. Regards, Jeff Davis -- 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: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Tom Lane wrote on 09.12.2012 17:43: spam_ea...@gmx.net writes: postgres=# create user testuser with password 'secret'; CREATE ROLE postgres=# create database testdb owner testuser; CREATE DATABASE testdb=> drop owned by testuser; ERROR: unrecognized object class: 1262 I can reproduce this in all versions back to 8.3. In 8.2, the role's ownership of the database is silently ignored, which I think was the design intention. I doubt that we want DROP OWNED dropping whole databases. At most maybe we should raise a NOTICE? I don't want to drop the database, just all objects that are created by that user (tables, schemas, ...) (In my example I first create a table) And this has definitely worked before, otherwise my unit tests would have failed all the time. Regards Thomas -- 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 #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
spam_ea...@gmx.net writes: > postgres=# create user testuser with password 'secret'; > CREATE ROLE > postgres=# create database testdb owner testuser; > CREATE DATABASE > testdb=> drop owned by testuser; > ERROR: unrecognized object class: 1262 I can reproduce this in all versions back to 8.3. In 8.2, the role's ownership of the database is silently ignored, which I think was the design intention. I doubt that we want DROP OWNED dropping whole databases. At most maybe we should raise a NOTICE? regards, tom lane -- 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 #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
The following bug has been logged on the website: Bug reference: 7748 Logged by: Thomas Kellerer Email address: spam_ea...@gmx.net PostgreSQL version: 9.2.2 Operating system: Windows XP, 32bit Description: Using "drop owned by someuser" in 9.2.2 fails with the error "unrecognized object class: 1262" This is what happens on the commandline. The PostgreSQL cluster was initialized right before running these steps using the command: initdb -D pgdata --lc-messages=English -U postgres -E UTF8 -A md5 This is what happens when using "drop owned by": c:\etc\postgres-9.2>psql psql (9.2.2) Type "help" for help. postgres=# create user testuser with password 'secret'; CREATE ROLE postgres=# create database testdb owner testuser; CREATE DATABASE postgres=# \q c:\etc\postgres-9.2>psql -U testuser testdb psql (9.2.2) Type "help" for help. testdb=> create table foobar (id integer); CREATE TABLE testdb=> drop owned by testuser; ERROR: unrecognized object class: 1262 postgres=# select version(); version - PostgreSQL 9.2.2, compiled by Visual C++ build 1600, 32-bit (1 row) Dropping the objects manually works without problems. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
