[BUGS] BUG #4242: Not able to open the Postgre sql
The following bug has been logged online: Bug reference: 4242 Logged by: vidhya Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 Operating system: linux(ubuntu) Description:Not able to open the Postgre sql Details: when i am installing the open bravo its not accepting the password for postgres admin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] initdb bug report
Hello. I'm Hamaguchi. now I use PostgreSQL8.2 on WindowsServer2003(SP2). I did execute "initdb -D c:\test" in CommandLine. But, it didn't initialize. This is Bug? How to initialize on WindowsServer2003(SP2)? C:\Program Files\PostgreSQL\8.2\bin>initdb -D c:\testThe program "postgres" is needed by initdb but was not found in thesame directory as "C:\Program Files\PostgreSQL\8.2\bin/initdb".Check your installation. C:\Program Files\PostgreSQL\8.2\bin> _ Live Search 地図検索で東京の都心部が3D表示に！ドコをみてみる？ http://maps.live.com/
Re: [BUGS] initdb bug report
2008/6/16 Joo HyunSik <[EMAIL PROTECTED]>: > Hello. I'm Hamaguchi. > now I use PostgreSQL8.2 on WindowsServer2003(SP2). > I did execute "initdb -D c:\test" in CommandLine. > But, it didn't initialize. > This is Bug? > > How to initialize on WindowsServer2003(SP2)? > > > C:\Program Files\PostgreSQL\8.2\bin>initdb -D c:\test > The program "postgres" is needed by initdb but was not found in the > same directory as "C:\Program Files\PostgreSQL\8.2\bin/initdb". > Check your installation. > C:\Program Files\PostgreSQL\8.2\bin> What is the full version number of PostgreSQL you are using? -- Dave Page EnterpriseDB UK: 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
Re: [BUGS] initdb bug report
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joo HyunSik Sent: 16 June 2008 14:54 To: pgsql-bugs@postgresql.org Subject: [BUGS] initdb bug report Hello. I'm Hamaguchi. now I use PostgreSQL8.2 on WindowsServer2003(SP2). I did execute "initdb -D c:\test" in CommandLine. But, it didn't initialize. This is Bug? How to initialize on WindowsServer2003(SP2)? C:\Program Files\PostgreSQL\8.2\bin>initdb -D c:\test The program "postgres" is needed by initdb but was not found in the same directory as "C:\Program Files\PostgreSQL\8.2\bin/initdb". Check your installation. C:\Program Files\PostgreSQL\8.2\bin> Is the command is run with an administrator account? If so try INITDB with a non administrative account. It may work. Anoo S Visit our Website at http://www.rmesi.co.in This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. Internet communications are not secure; therefore, RMESI does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of RMESI. If this email has come to you in error, please delete it, along with any attachments. Please note that RMESI may intercept incoming and outgoing email communications. Freedom of Information Act 2000 This email and any attachments may contain confidential information belonging to RMESI. Where the email and any attachments do contain information of a confidential nature, including without limitation information relating to trade secrets, special terms or prices these shall be deemed for the purpose of the Freedom of Information Act 2000 as information provided in confidence by RMESI and the disclosure of which would be prejudicial to RMESI's commercial interests. This email has been scanned for viruses by Trend ScanMail.
[BUGS] UUIDs generated using ossp-uuid on windows not unique
Hi all, This may not be the appropriate list to discuss this on (since it looks like the bug is in the underlying library), but as the win32 port was done because of postgresql (as far as I can tell), I wanted to see if anyone had run into this and/or had any workarounds: As best as I can tell, the problem is caused because generation of v1 UUIDs uses GetSystemTimeAsFileTime which is stated to have a resolution of 100 nanoseconds but in practice has a resolution of around 15ms (http://www.ddj.com/showArticle.jhtml?documentID=win0305a&pgno=17). Here's a snippet from log of id creation from a java app using Hibernate on 32-bit Windows Vista Home Premium: 17:59:50,007 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 400770c0-3bbd-11dd-9dcb-bfe9e8f8c4e3 17:59:50,016 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 4008d050-3bbd-11dd-bcfd-efd9d1bca81a 17:59:50,017 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 4008f760-3bbd-11dd-86d8-3b7fffcb1fd0 17:59:50,018 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 40091e70-3bbd-11dd-a129-c3ff008d4230 17:59:50,019 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 40094580-3bbd-11dd-91d4-3f3c34e3d932 17:59:50,020 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 40094580-3bbd-11dd-91d4-3f3c34e3d932 17:59:50,101 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 4015a190-3bbd-11dd-9639-9b73321c2f74 17:59:50,109 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 4016da10-3bbd-11dd-91d7-df8cd7608cfc 17:59:50,118 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 401860b0-3bbd-11dd-8ff9-5f0d982e530e 17:59:50,129 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 4019e750-3bbd-11dd-8e23-2315e240bab8 17:59:50,130 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 401a3570-3bbd-11dd-9af2-8350eef5ace8 17:59:50,131 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 401a5c80-3bbd-11dd-b91d-1fb0760aeab8 17:59:50,132 DEBUG [main][org.hibernate.id.GUIDGenerator] GUID identifier generated: 401a5c80-3bbd-11dd-b91d-1fb0760aeab8 Thoughts? Has anyone run into this before? Worked around it? Thanks, Meetesh
Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique
Meetesh Karia <[EMAIL PROTECTED]> writes: > As best as I can tell, the problem is caused because generation of v1 > UUIDs uses GetSystemTimeAsFileTime which is stated to have a resolution > of 100 nanoseconds but in practice has a resolution of around 15ms > (http://www.ddj.com/showArticle.jhtml?documentID=win0305a&pgno=17). Well, any real-time clock reading is going to have finite resolution. If your app is expecting that version-1 UUIDs generated in rapid succession will be distinct, I think your app is broken. It's just a little more obvious on Windows :-(. Perhaps the v4 generation method would work better for you? 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
Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique
Tom Lane wrote: Meetesh Karia <[EMAIL PROTECTED]> writes: As best as I can tell, the problem is caused because generation of v1 UUIDs uses GetSystemTimeAsFileTime which is stated to have a resolution of 100 nanoseconds but in practice has a resolution of around 15ms (http://www.ddj.com/showArticle.jhtml?documentID=win0305a&pgno=17). Well, any real-time clock reading is going to have finite resolution. If your app is expecting that version-1 UUIDs generated in rapid succession will be distinct, I think your app is broken. It's just a little more obvious on Windows :-(. Perhaps the v4 generation method would work better for you? actually this has been reported before and seems to be an issue in the windows port of the ossp-uuid library: http://archives.postgresql.org/pgsql-bugs/2008-05/msg00059.php Stefan -- 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] UUIDs generated using ossp-uuid on windows not unique
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Perhaps the v4 generation method would work better for you? > actually this has been reported before and seems to be an issue in the > windows port of the ossp-uuid library: > http://archives.postgresql.org/pgsql-bugs/2008-05/msg00059.php Oh, so that doesn't work either :-(. However, at least it's been fixed upstream: http://archives.postgresql.org/pgsql-bugs/2008-05/msg00070.php http://cvs.ossp.org/pkg/lib/uuid/ChangeLog 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
Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique
Hi. Sorry, late the information. My patch was applied after the review of Ralf-san. However, The timing of a release was different. Then, patch is only current CVS-HEAD. http://cvs.ossp.org/chngview?cn=6001 I thought that this problem was very important. It was sufficient reason to apply to 8.3.3 of pginstaller. Therefore, It should return the result of a wish. Regards, Hiroshi Saito - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes: Tom Lane wrote: Perhaps the v4 generation method would work better for you? actually this has been reported before and seems to be an issue in the windows port of the ossp-uuid library: http://archives.postgresql.org/pgsql-bugs/2008-05/msg00059.php Oh, so that doesn't work either :-(. However, at least it's been fixed upstream: http://archives.postgresql.org/pgsql-bugs/2008-05/msg00070.php http://cvs.ossp.org/pkg/lib/uuid/ChangeLog 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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
