[BUGS] windows installation
hi. this is not really an installation issue, but i read the instruction atop of the list, so here we are. ok. i succesfully installed postgresql 8 on my windows xp sp2 machine, few weeks ago. i am a newbie to sql generally, as well as to postrges i configured my server to run on localhost, everything was fine. i need to mention that the machine is part of a active directory network, corporate 350+ machines, policies, etc. the thing is that i haven't started postrges for about a week, during wich time i have not made changes to the machine, nor installed any software that could affect the performance/security/policy allready running on my machine, a p4 -3,2 HT, 512 DDR, 80 GBsata, a rather nice machine, otherwise. when i tried to connect to the database, i received an error, that i cannot connect to the database as a superuser. i have configured .\postgre to run automatically on system start, and worked just fine. i only modifyed the tmplate to logon to a custom test database, but i worked fine everytime before the pause i already mentioned. after varoius error messages, error log, etc i discovered the service to have been disabled, and set for deletion. as i could not modify it's state through "normal" procedure - mmc console, i regedit-modifyed the service's state to autimatic from disabled. the thing is, that when i attempt to start, i get an error message that the service could not start because it is eighter disabled, or has no devices attached to it. in the service's propeties box, at the start parameters box - blank. if i need start parameters can u please give me some feedback on this regard, or if there's something else, please let me know. i checked with the network admin, and there is no change lately in the pilocies. i guess it's useful to know that there is a concurrent-login prohibiton policy, and event log says Event Type: Failure Audit Event Source: Security Event Category: Logon/Logoff Event ID: 534 Date: 31.03.2005 Time: 15:44:09 User: NT AUTHORITY\SYSTEM Computer: x Description: Logon Failure: Reason: The user has not been granted the requested logon type at this machine User Name: concurrent_logins Domain: xx Logon Type: 3 Logon Process: Kerberos Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Workstation Name: - For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. help anyone? best regards, raymond -- listen. see. believe. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #4617: JDBC Drivers 8.2/8.3 return no ResultSet
Excellent.
So useful getUpdateCount(), getResultSet(), and getMoreResults() return
very detailed data about each query in a statement.
Updating driver also found place we were using ps.setString(value) for a
parameter for ID = ?, and we got error asking for proper use of
ps.setInt(value).
Kris Jurka wrote:
On Thu, 15 Jan 2009, Raymond L. Naseef wrote:
The following bug has been logged online:
Bug reference: 4617
PostgreSQL version: 8.3 & 7.4
Operating system: FreeBSD
Description:JDBC Drivers 8.2/8.3 return no ResultSet
Details:
Below is query using temporary table instead of "IN" to greatly improve
performance. This worked in older JDBC driver, but no longer does. The
following were checked, making no difference:
RESULT:
org.postgresql.util.PSQLException: No results were returned by the
query.
QUERY:
--
create temporary table lookup_username (username varchar) on commit drop;
insert into lookup_username values ('naseef');
CREATE UNIQUE INDEX lookup_username_idx
ON lookup_username
USING btree
(username);
SELECT enp.username, trim(enp.full_name)
FROM egr_nis_person as enp
JOIN lookup_username as lu
ON lu.username = enp.username
WHERE enp.start_date < now() + interval '30 seconds'
AND enp.end_date > now() + interval '30 seconds';
What's happening here is that you are actually issuing four commands,
not a single query. The newer drivers will return a status for each
command executed, and won't just give you the final select result. For
multi-command statements you should use Statement.execute() and then
getResultSet or getUpdateCount until getMoreResults is false.
Kris Jurka
--
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 #3059: psql to 'postgres' shortcut
The following bug has been logged online: Bug reference: 3059 Logged by: Raymond Naseef Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 Operating system: Windows XP Description:psql to 'postgres' shortcut Details: The shortcut to run psql.exe added to the menus is a great think to do, but when the program stops the window closes with no pause or time delay. This is a serious issue if the login fails. Sometimes I forget to start the server, but I do not know that because I cannot read text in ~0.02 seconds. BTW, I bet some of your other .bat files have the same issue. Please run it by doing 1 or other: 1. Putting a "pause" at the end of the batch file. 2. cmd.exe /K "" (just note the "" for default user name will make this fail. Sorry I do not know how to fix that unless username has no bad-for-cmd characters in it, then quotes are not needed) ---(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
Re: [BUGS] BUG #3059: psql to 'postgres' shortcut
Dear Team, I checked the shortcut and was unable to find any note about "close on exit" or anything like that. The .bat method sounds wonderful, and I would appreciate such a change to make the product a little more responsive. Thank you for your consideration and time, Raymond Naseef P.S. I apologize if my email were not being sent properly. I will pay close attention to this going forward. - Original Message From: Bruce Momjian <[EMAIL PROTECTED]> To: Magnus Hagander <[EMAIL PROTECTED]> Cc: Phil Frost <[EMAIL PROTECTED]>; Raymond Naseef <[EMAIL PROTECTED]>; pgsql-bugs@postgresql.org Sent: Tuesday, February 27, 2007 2:08:38 PM Subject: Re: [BUGS] BUG #3059: psql to 'postgres' shortcut Magnus Hagander wrote: > On Tue, Feb 27, 2007 at 09:06:17AM -0500, Phil Frost wrote: > > Hrm...I haven't used windows for a while now, but isn't there an > > option on all shortcuts to command-line programs to make the shell > > pause on exit? It is something like, right click on shortcut, select > > 'properties', uncheck 'close shell on exit'. It would seem this would > > solve the problem of not being able to see errors, while also not > > adding a pause for programs which execute psql.bat directly. > > Yes, that is exactly the point -it would be very annoying in all other > cases, as Bruce pointed out. > > I guess another option would be to add a commandline option to psql to > pause on error, but I don't think that's going to fly ;-) I just ran a test on Unix and found psql exits with '2' if the password fails. In fact, looking at the psql sources I see: #ifndef EXIT_SUCCESS #define EXIT_SUCCESS 0 #endif #ifndef EXIT_FAILURE #define EXIT_FAILURE 1 #endif #define EXIT_BADCONN 2 #define EXIT_USER 3 Notice EXIT_BADCONN. So, what if we call psql from a batch file, and check for a '2' exit status, and then issue a pause for only that case? -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/
[BUGS] Timestamp problem
I am use PostgreSQL 7.2.1 in Redhat Linux 7.2 Java 1.4.x When I do JDBC String sql = "SELECT datetime_column FROM mytable"; Timestamp ts = resultSet.getTimestamp(2); If the timestamp return format like 2003-07-15 13:20:00.20+00 then is OK. But if timestamp return like 2003-07-15 13:20:00.421+00 Then I got SQLException Bad Timestamp Format at 23 in 2003-07-14 14:45:00.421+00 What is 23? How do I resolve this problem? Thank Q! -- Raymond Chui NWS at NOAA 301-713-0640 ext 168 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] General PostgresSQL Query
PostGresSQL team: Hi, I am currently working for a small software company and we are unable to find tuning specific documentation for our servers running postgres. I know this email is for bug submission however if you could direct this email through the proper lines I would be very grateful. I have a system with 5gb ram and 2 900Mhz cpus. Would you guys be able to provide me with some tuning specific information for postgres.conf that would allow my system to run at optimium performance. No information that I know of is available on this topic. Please assist. Thanks, Raymond Henick Rebellion Web Design
[BUGS] BUG #4617: JDBC Drivers 8.2/8.3 return no ResultSet
The following bug has been logged online:
Bug reference: 4617
Logged by: Raymond L. Naseef
Email address: nas...@egr.msu.edu
PostgreSQL version: 8.3 & 7.4
Operating system: FreeBSD
Description:JDBC Drivers 8.2/8.3 return no ResultSet
Details:
Below is query using temporary table instead of "IN" to greatly improve
performance. This worked in older JDBC driver, but no longer does. The
following were checked, making no difference:
1) Removed from query:
CREATE UNIQUE INDEX lookup_username_idx
ON lookup_username
USING btree
(username);
2) Setting auto-commit (checked with false and true, and unset).
Servers:
PostgreSQL 7.4.19 on amd64-portbld-freebsd7.0, compiled by GCC cc (GCC)
4.2.1.20070719 [FreeBSD]
PostgreSQL 8.3.5 on amd64-portbld-freebsd7.0, compiled by GCC cc (GCC)
4.2.1.20070719 [FreeBSD]
JDBC Drivers:
Result Driver
== ===
WORKpg74.216.jdbc3.jar
FAILpostgresql-8.2-506.jdbc3.jar
FAILpostgresql-8.3-604.jdbc3.jar
This was tested using AutoCommit default and false, using EITHER A or B:
PreparedStatement ps = connection.prepareStatement([shown_below]);
[ A ]
ps.execute();
ResultSet rs = ps.getResultSet();
RESULT:
rs == null
[ B ]
ResultSet rs = ps.executeQuery();
RESULT:
org.postgresql.util.PSQLException: No results were returned by the
query.
QUERY:
--
create temporary table lookup_username (username varchar) on commit drop;
insert into lookup_username values ('naseef');
CREATE UNIQUE INDEX lookup_username_idx
ON lookup_username
USING btree
(username);
SELECT enp.username, trim(enp.full_name)
FROM egr_nis_person as enp
JOIN lookup_username as lu
ON lu.username = enp.username
WHERE enp.start_date < now() + interval '30 seconds'
AND enp.end_date > now() + interval '30 seconds';
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
