[BUGS] Windows 8.0 beta on Server 2003 Installer problem
Title: Windows 8.0 beta on Server 2003 Installer problem This may not be a bug but I only have one Windows 2003 Server to try it on. The package installed fine on Windows XP Professional and Windows 2000 professional. Launching the installer it looks fine until it gets to the screen where you can select which options to install and which directories to use. Then it crashes with the error: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2819." Anyone experiencing this problem? Is there a service patch or fix I need to apply to Windows? My current version is 5.2 (Build 3790.srv03_rtm.030324-2048) Cheryl Bender
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
Cheryl, you can learn more about the problem by doing some logging... msiexec /Lv c:\\temp\\nase2.txt /i postgresql-8.0-beta2-dev3.msi "c:\\temp\\nase2.txt" is the file wereto the logging is done. You can read there more about the exact error ... what was done last. Best go from the end, where there is all that "removing " Harald - Original Message - From: Bender, Cheryl <[EMAIL PROTECTED]> Date: Wed, 15 Sep 2004 09:51:02 -0500 Subject: [BUGS] Windows 8.0 beta on Server 2003 Installer problem To: [EMAIL PROTECTED] This may not be a bug but I only have one Windows 2003 Server to try it on. The package installed fine on Windows XP Professional and Windows 2000 professional. Launching the installer it looks fine until it gets to the screen where you can select which options to install and which directories to use. Then it crashes with the error: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2819." Anyone experiencing this problem? Is there a service patch or fix I need to apply to Windows? My current version is 5.2 (Build 3790.srv03_rtm.030324-2048) Cheryl Bender -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
Cheryl, I digged through you log, and stumbled: ### MSI (c) (B0:94): Product: PostgreSQL 8.0-beta2-dev3 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2819. The arguments are: Service_Dialog, esvcacct, ### MSI (c) (B0:94): Database string pool is corrupted. ### For me this looks like a corrupted installer package - or some other reading problems. Did you check the validity of that particular installer package, to avoid "corrupted .msi file"? Are you logged in locally to the server? Local Administrator? There are various reports about problems with remote-console-installation (but they do usually appear later :)) ) Harald -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(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
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
I wondered about the corrupt installer problem (since I cannot download files here I downloaded it at home and put on CD), but it installed fine on Windows XP Professional. Perhaps this is a corruption that XP forgives but 2003 does not. I've had some problems with 2003 on this box (Dell GX260) reading certain ISO CDs, but I copied the file locally to run the program. I logged in as local administrator to run the program. One of our IT admin guys said I could test it on his server 2003 so I'll try it out and see how it goes. Thanks Cheryl Bender -Original Message- From: Harald Armin Massa [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 15, 2004 10:57 AM To: Bender, Cheryl; [EMAIL PROTECTED] Subject: Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem Cheryl, I digged through you log, and stumbled: ### MSI (c) (B0:94): Product: PostgreSQL 8.0-beta2-dev3 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2819. The arguments are: Service_Dialog, esvcacct, ### MSI (c) (B0:94): Database string pool is corrupted. ### For me this looks like a corrupted installer package - or some other reading problems. Did you check the validity of that particular installer package, to avoid "corrupted .msi file"? Are you logged in locally to the server? Local Administrator? There are various reports about problems with remote-console-installation (but they do usually appear later :)) ) Harald -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(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
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
> I digged through you log, and stumbled: > > ### > MSI (c) (B0:94): Product: PostgreSQL 8.0-beta2-dev3 -- The > installer has encountered an unexpected error installing this > package. This may indicate a problem with this package. The > error code is 2819. The arguments are: Service_Dialog, esvcacct, > > ### MSI (c) (B0:94): Database string pool is corrupted. > ### > > For me this looks like a corrupted installer package - or > some other reading problems. Did you check the validity of > that particular installer package, to avoid "corrupted .msi file"? It could also be a corrupt database on the machine itself, in the system databases. I have no idea what to do about that, thoguh :-) But if it succeeds on all other machines (with *the same download*), and consistently fails on this one, that sounds like it could be it. Can you install other MSI based packages on this machine? //Magnus ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] character and text comparison
Hello, When I run SELECT ' '::character = ' '::text; on PostgreSQL 7.4 the result is `false' while on 7.3 and 7.2 instalations result is `true' Is this an intentional change? regards, Jacek Rembisz ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
<> Yes--just to make sure I installed another MSI-based package and it worked fine. Cheryl Bender -Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 15, 2004 11:14 AM To: Harald Armin Massa; Bender, Cheryl; [EMAIL PROTECTED] Subject: RE: [BUGS] Windows 8.0 beta on Server 2003 Installer problem > I digged through you log, and stumbled: > > ### > MSI (c) (B0:94): Product: PostgreSQL 8.0-beta2-dev3 -- The > installer has encountered an unexpected error installing this > package. This may indicate a problem with this package. The > error code is 2819. The arguments are: Service_Dialog, esvcacct, > > ### MSI (c) (B0:94): Database string pool is corrupted. > ### > > For me this looks like a corrupted installer package - or > some other reading problems. Did you check the validity of > that particular installer package, to avoid "corrupted .msi file"? It could also be a corrupt database on the machine itself, in the system databases. I have no idea what to do about that, thoguh :-) But if it succeeds on all other machines (with *the same download*), and consistently fails on this one, that sounds like it could be it. Can you install other MSI based packages on this machine? //Magnus ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] character and text comparison
Jacek Rembisz <[EMAIL PROTECTED]> writes: > When I run SELECT ' '::character = ' '::text; > on PostgreSQL 7.4 the result is `false' > while on 7.3 and 7.2 instalations result is `true' > Is this an intentional change? Yes. We now strip trailing blanks when converting a char(n) value to text. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] BUG #1252: Optimization of SELECT for NOT NULL case
On Tue, Sep 14, 2004 at 00:57:07 +0100, PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote: > > Description:Optimization of SELECT for NOT NULL case > > Details: > > CREATE TABLE x (id int4 NOT NULL); > Populate table, for instance, 10M rows; > SELECT count(*) from x WHERE x IS NULL; > Optimizator should rewrite "x IS NULL" to simple "false" Based on responses to other optimization requests I have seen, I think the answer to this one is going to be that it isn't worth paying the cost for every query to check for this case, since no one is going to write a query like this except by mistake. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] character and text comparison
On Wed, Sep 15, 2004 at 12:43:11PM -0400, Tom Lane wrote: > Jacek Rembisz <[EMAIL PROTECTED]> writes: > > When I run SELECT ' '::character = ' '::text; > > on PostgreSQL 7.4 the result is `false' > > while on 7.3 and 7.2 instalations result is `true' > > > Is this an intentional change? > > Yes. > > We now strip trailing blanks when converting a char(n) value to text. Thank you for a quick answer. I have changed my application to use text type instead of character type. best regards, Jacek Rembisz ---(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
Re: [BUGS] BUG #1252: Optimization of SELECT for NOT NULL case
Bruno Wolff III <[EMAIL PROTECTED]> writes: > On Tue, Sep 14, 2004 at 00:57:07 +0100, >> CREATE TABLE x (id int4 NOT NULL); >> SELECT count(*) from x WHERE x IS NULL; >> Optimizator should rewrite "x IS NULL" to simple "false" > Based on responses to other optimization requests I have seen, I think the > answer to this one is going to be that it isn't worth paying the cost > for every query to check for this case, since no one is going to write > a query like this except by mistake. There's been some speculation about making the optimizer aware of table constraints in general (eg, CHECK constraints) but I tend to agree that doing this only for NOT NULL isn't very exciting. regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem
I was able to install on a another 2003 server, so it must be a problem with my machine. Although I sure wish I knew what the problem is, since the other server is almost identical. It's a good thing in the end though because that server is a much better test platform. Thanks all for your suggestions. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bender, Cheryl Sent: Wednesday, September 15, 2004 11:27 AM To: Magnus Hagander; Harald Armin Massa; [EMAIL PROTECTED] Subject: Re: [BUGS] Windows 8.0 beta on Server 2003 Installer problem <> Yes--just to make sure I installed another MSI-based package and it worked fine. Cheryl Bender -Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 15, 2004 11:14 AM To: Harald Armin Massa; Bender, Cheryl; [EMAIL PROTECTED] Subject: RE: [BUGS] Windows 8.0 beta on Server 2003 Installer problem > I digged through you log, and stumbled: > > ### > MSI (c) (B0:94): Product: PostgreSQL 8.0-beta2-dev3 -- The installer > has encountered an unexpected error installing this package. This may > indicate a problem with this package. The error code is 2819. The > arguments are: Service_Dialog, esvcacct, > > ### MSI (c) (B0:94): Database string pool is corrupted. > ### > > For me this looks like a corrupted installer package - or some other > reading problems. Did you check the validity of that particular > installer package, to avoid "corrupted .msi file"? It could also be a corrupt database on the machine itself, in the system databases. I have no idea what to do about that, thoguh :-) But if it succeeds on all other machines (with *the same download*), and consistently fails on this one, that sounds like it could be it. Can you install other MSI based packages on this machine? //Magnus ---(end of broadcast)--- TIP 8: explain analyze is your friend ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] BUG #1252: Optimization of SELECT for NOT NULL case
On 15 Sep 2004, at 12:21, Bruno Wolff III wrote: > On Tue, Sep 14, 2004 at 00:57:07 +0100, > PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote: > > > > Description:Optimization of SELECT for NOT NULL case > > > > Details: > > > > CREATE TABLE x (id int4 NOT NULL); > > Populate table, for instance, 10M rows; > > SELECT count(*) from x WHERE x IS NULL; > > Optimizator should rewrite "x IS NULL" to simple "false" > > Based on responses to other optimization requests I have seen, I think > the answer to this one is going to be that it isn't worth paying the > cost for every query to check for this case, since no one is going to > write a query like this except by mistake. > Regarding your point of view possible exist reason for remove optimization for case like below SELECT count(*) from x where id>1 AND id<0 I basically don't see any significant difference in optimization for "id IS NULL" and "id>1 AND id<0" >From other point of view not always well know NOT NULL a case for some columns, especially in case JOIN and complex subselects or dynamic SQL. Main reason to include this optimization, don't need any a scan of table in optimized case as result well know before any work with data from tables. >From last point of view optimization in DB servers need for make work for application developer (not always with serious knowledge in mathematics and relational databases) more easy and for customer more swiftly. And latest point of view: DB server developer have way for enhance for instance EXPLAIN statement by displaying hint for static SQL. In any case thank you for postgreSQL 8, particularly for background disk writer and improving using of shared buffers. Good DB engine have more knowledge about information in shared buffers and using her, that any disk cache system of OS, plus avoiding or minimize using cache remove don't need "moving" between cache and buffers. Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] Pb with ecpg and include file on PG 8.0.0
>Date: Tue, 14 Sep 2004 09:27:41 +0200 >From: Michael Meskes <[EMAIL PROTECTED]> >To: Valerie Schneider DSI/DEV <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Subject: Re: [BUGS] Pb with ecpg and include file on PG 8.0.0 >Mime-Version: 1.0 >Content-Disposition: inline >User-Agent: Mutt/1.5.6+20040722i >X-Provags-ID: kundenserver.de [EMAIL PROTECTED] auth:da5cff6069dd6897c77170232368d0ba > >On Fri, Sep 10, 2004 at 08:09:55AM +, Valerie Schneider DSI/DEV wrote: >> I installed PG 8.0.0beta2 : >> [EMAIL PROTECTED] SrcLib]$ ecpg --version >> ecpg (PostgreSQL 8.0.0beta2) 3.2.0 > >This works nicely for me with ecpg 3.2.0. It may be that ecpg >does not find the include file. But then it should also print that. But why ecpg found it in the 7.4 version ? Following a remark I removed the semi-colon at the end of each exec sql define xx (I had : exec sql define xx ; ) in the include file. No result. Someone from the pgsql-fr-generale list seems to have the same problem. Thanks for your reply, Valerie. > >I had the file in "." where ecpg found it and the constant was correctly >translated. > >Michael >-- >Michael Meskes >Email: Michael at Fam-Meskes dot De >ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] >Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! *Les points de vue exprimes sont strictement personnels et * * n'engagent pas la responsabilite de METEO-FRANCE. * * Valerie SCHNEIDER Tel : +33 (0)5 61 07 81 91 * * METEO-FRANCE / DSI/DEVFax : +33 (0)5 61 07 81 09 * * 42, avenue G. CoriolisEmail : [EMAIL PROTECTED] * * 31057 TOULOUSE Cedex - FRANCE http://www.meteo.fr* ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] Cannot install properly on WinXP...
Hello! I have some problems when installing postgresql-8.0-beta2-dev3 on my WinXP system. During the installation process, after the DOS batch process, I get the following error messages: "Failed to connect to database. Procedural languages files are installed, but are not activated in any databases." "server closed the connection unexpectedly This probably means the server terminated abnormally before or while the request." "Failed to connect to database. Contrib files are installed, but are not activated in any databases." "server closed the connection unexpectedly This probably means the server terminated abnormally before or while the request." Then, the installation finishes. Later, when I open pgAdmin III, I right clic on ... and get the following error: "An error has occured: couldo not receive server response to SSL negotiation packet: Connection reset by peer (0x2746/10054)" So, I cannot see the database server. I tried checking and resetting the system service, but I got no response. Please tell me what the problem is, what I may be dogin wrong or please fix the bug :) God bless you! Luis Tama Luis Antonio Tama Wong Ayudante LAB-FIEC - ESPOL Teléfono: 2269268 e-mail: [EMAIL PROTECTED] ¡No tengáis miedo de ser santos! --- S.S. Juan Pablo II ---(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] Bug in boolean columns on win2k
RE-POST: This is a repost. Our mailserver was out of order when sending
this report yesterday, and I can't find the post on the buglist yet.
Sorry for any inconvenience.
BUG:
I have a table with the following column, from "psql \d":
showemail| boolean |
When I try to insert data data into this through jdbc, I get the
following error:
java.sql.SQLException: ERROR: column "showemail" is of type boolean but
expression is of type text
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryEx
ecutorImpl.java:1130)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor
Impl.java:933)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja
va:139)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Stat
ement.java:346)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(Abstract
Jdbc2Statement.java:294)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdb
c2Statement.java:249)
-
My environment:
postgreSQL 8.0-beta2-dev3
Win2k sp4 professional
jdbc driver: pgdev.305.jdbc3
java version: 1.4
The error also occured in beta1.
The following statement executed from psql works as expected:
insert into mytable (showemail) values ('true');
--
Thanks
Mads Peter Henderson
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
[BUGS] Bug in boolean columns on win2k
I have a table with the following column,
from psql \d:
showemail| boolean |
When I try to insert data data into this through jdbc, I get the
following error:
java.sql.SQLException: ERROR: column "showemail" is of type boolean but
expression is of type text
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryEx
ecutorImpl.java:1130)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor
Impl.java:933)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja
va:139)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Stat
ement.java:346)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(Abstract
Jdbc2Statement.java:294)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdb
c2Statement.java:249)
-
My environment:
postgreSQL 8.0-beta2-dev3
Win2k sp4 professional
jdbc driver: pgdev.305.jdbc3
java version: 1.4
The error also occured in beta1.
The following statement executed from psql works as expected:
insert into mytable (showemail) values ('true');
--
Thanks
Mads Peter Henderson
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Re: [BUGS] Bug in boolean columns on win2k
On Wed, 15 Sep 2004, Mads Peter Henderson wrote: > I have a table with the following column, from "psql \d": > showemail| boolean | > > When I try to insert data data into this through jdbc, I get the > following error: > java.sql.SQLException: ERROR: column "showemail" is of type boolean but > expression is of type text Are you using something like PreparedStatement.setString to compose this query? You should be using setBoolean instead I imagine. Kris Jurka ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Cannot install properly on WinXP...
Luis, sad sad story. PostgreSQL on Windows is very challenged by LSP-Applications running on the same machine. LSP = Layered Service Provider That my be Antivir Software, or on my machine it was "CoolSpot personal ID", an age verification system to see adult content. Please check the extensive FAQ of the installer to also find a link to a tool to check, if this may be the prob. on your computer. Harald > "Failed to connect to database. Contrib files are installed, but are not > activated in any databases." > "server closed the connection unexpectedly -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
