Re: [BUGS] BUG #2269: cannot connect to postgres database on Linux
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ken > Sent: 16 February 2006 17:47 > To: pgsql-bugs@postgresql.org > Subject: [BUGS] BUG #2269: cannot connect to postgres > database on Linux > > > The following bug has been logged online: > > Bug reference: 2269 > Logged by: Ken > Email address: [EMAIL PROTECTED] > PostgreSQL version: 7.3.4 > Operating system: Linux > Description:cannot connect to postgres database on Linux > Details: > > I just downloaded pgAdminIII for Windows to use to connect to > our postgres > databases on Linux. The problem I have is that when I enter > the password, I > get this error: > > Error has occurred > Error connecting to the server: missing "=" after """ in > connection info > string. > > The passwords to our databases contain the characters ; and > ', which is what > is probably causing this problem. Can this be resolved or is > there a temp > fix to get around this problem? I've committed fixes to pgAdmin which was incorrectly escaping single quotes with another single quote (in the same way as we do for string values in SQL). Thanks for the report. Regards, Dave. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #2265: CREATE TABLE when AUTOCOMMIT is OFF
Please copy the pgsql-bugs mailing list on replies. Also, if you've submitted multiple bug reports then please keep the discussion of each bug in their respective threads. I'm replying only to 2265 because I'm not as familiar with the other problems. On Fri, Feb 17, 2006 at 03:09:48PM +0100, [EMAIL PROTECTED] wrote: > Now I configured query logging and I saw what was wrong. > First I executed > > SELECT rel FROM versions > > but the 'versions' table didn't exist. So I thought that I can create this > 'versions' table in the > same transaction. In PostgreSQL 8.0.4 this worked, but in 8.1.3 I got the > error message. When you say that "this" worked in 8.0.4 but not in 8.1.3, what exactly do you mean by "this"? If the SELECT failed then any subsequent command in the same transaction should also have failed; 8.0 and 8.1 shouldn't differ in that respect, at least not in the backend. If you can demonstrate otherwise then please post a repeatable test case (i.e., a set of SQL statements that can be run against an empty database in a new session or a new transaction). Try running tests with psql as well as with ODBC to see if they behave differently. > When executing COMMIT after the SELECT statement, I was able to do the > CREATE TABLE. > I think that this behaviour is desired in 8.1.3, am I right? It surely has > to do with the two-phase commit. Are you using two-phase commit? Why do you think it's "surely" involved? Let's see a complete test case before jumping to conclusions. -- Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG #2270: not accepted user and password
The following bug has been logged online: Bug reference: 2270 Logged by: Elias Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Windows XP Home Description:not accepted user and password Details: when it enters in the screen of service configuration the usuario and password always present the following message: Logon failure. unknown user name or bad password. already I reinstalled and I removed the register keys but nao advances when I go to create a usuar for windows, it informs that usuar exists, but does not show it I do not obtain to install ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
