Re: [BUGS] WARNING: 01000: could not dump unrecognized node type: 928
On Fri, Nov 12, 2010 at 9:29 PM, Tom Lane wrote: > Jon Nelson writes: >> I get this whenever debug_print_rewritten = on >> WARNING: 01000: could not dump unrecognized node type: 928 >> LOCATION: _outNode, outfuncs.c:2787 >> right before >> LOG: 0: rewritten parse tree: > >> PostgreSQL 8.4.5 on Linux x86-64 > > Hm, do you use CREATE TABLE LIKE a lot? During development, yes. -- Jon -- 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] WARNING: 01000: could not dump unrecognized node type: 928
Jon Nelson writes: > I get this whenever debug_print_rewritten = on > WARNING: 01000: could not dump unrecognized node type: 928 > LOCATION: _outNode, outfuncs.c:2787 > right before > LOG: 0: rewritten parse tree: > PostgreSQL 8.4.5 on Linux x86-64 Hm, do you use CREATE TABLE LIKE a lot? 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 #5752: installer does not give proper os privileges on folders
The following bug has been logged online: Bug reference: 5752 Logged by: Kasia Tuszynska Email address: ktuszyn...@esri.com PostgreSQL version: 9.0.1 Operating system: Windows 2008 R2 (64bit) Description:installer does not give proper os privileges on folders Details: Tested: The one click Postgres 64bit installer for 9.0.0 and 9.0.1 Tested on: windows 2008 64bit windows 2008 R2 - which is only 64bit UAC was turned off password strength was disabled Problem: crying to create a tablespace gives error: could not set permissions on directory C:\.\tablespace_name" Permission denied work around: grant the users group full control privileges on the tablespace folder Locations tried: under the data folder - failed with permissions denied under the C drive - failed with permissions denied ways of creating ta tablespace, tried: programatically calling a postgres function creating folder manually, using pgAdminiii for tbsp creation creating folder manually, using psql to create the tablespace Compared the result: pg 8.3.8 msi on win2003 32bit, win 2008 R2 to pg 9.0.0 and 9.0.1 one click installer on win 2008 R2 I compared the privileges granted on the PostgreSQL, 8.3/9.0, data and tablespace folders and found the following differences: PostgreSQL folder - same privs given by both versions Privs present on the 8.3.8 folder but missing on the 9.0 folder deny postgres special allow postgers read&execute - all others are the same between both versions Priv differences on the data folder 8.3.8 had: allow postgres modify not inherited this folder and subfolders 9.0 had: allow postgres special not inherited this folder only allow kasiaspecial not inherited this folder only - all others are the same between both versions Privs listed on the folder data\tablespace_name 8.3.8: allow trustedinstaller special - appears twice allow system special - appears twice allow administrators special - appears twice allow usersspecial - appears twice allow creator ownerspecial allow postgres modify this folder, subfolders 9.0: allow trustedinstaller special allow system full control allow administrators full control allow usersread&write allow creator ownerspecial Conclusion: postgres os user and the users windows group are missing privileges on folders granted inside the data folder layed down by the postgres 9.0 one click installer. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] WARNING: 01000: could not dump unrecognized node type: 928
I get this whenever debug_print_rewritten = on WARNING: 01000: could not dump unrecognized node type: 928 LOCATION: _outNode, outfuncs.c:2787 right before LOG: 0: rewritten parse tree: PostgreSQL 8.4.5 on Linux x86-64 Does this sound familiar? -- Jon -- 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 #5751: pg_restore does not work correctly with BLOBs
"Michael Feldmann" writes: > [ pg_dump -c doesn't delete BLOBs ] This appears to be fixed in 9.0. I fear it's impractical to do anything about it before that, because pg_dump didn't treat BLOBs as first-class objects before 9.0. 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 #5751: pg_restore does not work correctly with BLOBs
The following bug has been logged online: Bug reference: 5751 Logged by: Michael Feldmann Email address: michael.feldm...@uni-muenster.de PostgreSQL version: 8.4.5 Operating system: Ubuntu Description:pg_restore does not work correctly with BLOBs Details: I start with a database containing only a BLOB. Then I dump this database with pg_dump -Fc Then I create a new database testblob and restore the dump with the command pg_restore -v -c -d testblob -O blob.dump This works as expected. But if I try restore the same dump again with the same command I get the error message pg_restore: restoring BLOBS pg_restore: [archiver] could not create large object 25213 pg_restore: *** aborted because of error If I first drop the database testblob and then create it again everything works fine. It seems that pg_restore does not clean the old database completely, despite the -c flag. We ran into this problem when writing an automated mirroring script. Best Regards Michael Feldmann --- ZIV, University of Muenster, Germany -- 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 #5721: EnterpriseDB linux one-click installer missing libuuid.so.16
Excerpts from Bruce Momjian's message of vie nov 12 15:09:17 -0300 2010: > Alexia Lau wrote: > > I'm running into the same problem reported with bug #5677, but I'm > > installing on SUSE 11 and RedHat 5.5. I saw a thread below and Dave Page > > mentioned that there's a bug which didn't copy the library properly which > > has been fixed at PostgreSQL 9.0.2. What is the bug number related to this > > and when is the planned release for 9.0.2? Will EnterpriseDB fix the > > one-click installer for linux builds to this? > > The release of PG 9.0.2 is really under the control of the community > timetable. I am not sure when the next minor update will happen. > Sorry. Surely if there's a packaging mistake, the packager could release a new version of the package, even if the underlying release does not change. This is standard practice in any Linux distribution. It seems saner to install RPM packages in RedHat anyway. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- 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 #5721: EnterpriseDB linux one-click installer missing libuuid.so.16
Alexia Lau wrote: > > The following bug has been logged online: > > Bug reference: 5721 > Logged by: Alexia Lau > Email address: a...@esri.com > PostgreSQL version: 9.0.1 > Operating system: SUSE 11/RHEL 5.5 32-bit & 64-bit > Description:EnterpriseDB linux one-click installer missing > libuuid.so.16 > Details: > > Hi, > > I'm running into the same problem reported with bug #5677, but I'm > installing on SUSE 11 and RedHat 5.5. I saw a thread below and Dave Page > mentioned that there's a bug which didn't copy the library properly which > has been fixed at PostgreSQL 9.0.2. What is the bug number related to this > and when is the planned release for 9.0.2? Will EnterpriseDB fix the > one-click installer for linux builds to this? The release of PG 9.0.2 is really under the control of the community timetable. I am not sure when the next minor update will happen. Sorry. --- > > Thank you, > Alexia > > > http://archives.postgresql.org/pgsql-general/2010-10/msg00311.php > > On Thu, Oct 7, 2010 at 3:56 AM, Tom Lane wrote: > > Mike Christensen writes: > >> On Wed, Oct 6, 2010 at 7:38 PM, Tom Lane wrote: > >>> If you have a libossp-uuid.so.16, you might try symlinking > libuuid.so.16 > >>> to that instead of carrying a separate file. > > > >> So now what you're saying is if it's not broke, fix it till it is :) > > > > Well, it's hard to argue with that position ;-). But I'll try anyway: > > the platform-provided version of the library will be updated for bug > > fixes, compatibility rebuilds, etc. Your private copy won't be, unless > > you remember to do it. Eventually that's gonna bite ya. > > > > Of course the best fix would be for EDB to ship a build of Postgres > > that actually follows the platform-standard naming convention for this > > library. I'm still wondering why they're linking to libuuid.so. > > Dave? > > Because that's what comes with ossp-uuid 1.6.2, and I assume is what > configure chooses when we use --with-ossp-uuid: > > [buildf...@bf2-linux ~]$ uuid-config --libs > -luuid > > FYI, there was also a bug in the installer which didn't copy the > library properly, which has been fixed for 9.0.2. > > > -- > Dave Page > PostgreSQL Core Team > http://www.postgresql.org/ > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- 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 #5750: dropping objects owned by user fails
On 12.11.2010 15:06, Chetan wrote: postgres=# create user t; CREATE ROLE postgres=# create foreign data wrapper wrap123; CREATE FOREIGN DATA WRAPPER postgres=# grant usage on foreign data wrapper wrap123 to t; GRANT postgres=# drop owned by t; ERROR: unexpected object class 2328 postgres=# Fixed. Of course, foreign data wrappers and servers don't do anything interesting yet, but since we have them, might as well make them work correctly. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- 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 #5750: dropping objects owned by user fails
The following bug has been logged online: Bug reference: 5750 Logged by: Chetan Email address: chetan.suttra...@enterprisedb.com PostgreSQL version: 9.0.1 Operating system: Ubuntu 9.10 Description:dropping objects owned by user fails Details: steps to reproduce: psql (9.0.1) Type "help" for help. postgres=# create user t; CREATE ROLE postgres=# create foreign data wrapper wrap123; CREATE FOREIGN DATA WRAPPER postgres=# grant usage on foreign data wrapper wrap123 to t; GRANT postgres=# drop owned by t; ERROR: unexpected object class 2328 postgres=# -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
