ven specifically says this is so it fixes the deadlock issues and
not just statement_timeout :-)
//Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Title: Meddelande
This
is almost certainly the "pid file does nto go away" issue. Manually remove the
.pid file in the data directory, and start the service.
I
beleive this bug is fixed in beta-2.
//Magnus
-Ursprungligt meddelande-Från: Mike Hornick
[mai
right
now, and I think I have tracked down the location of the problem. We'lll
put out a new version of the installer as soon as it's fixed.
You acn track this issue on pgfoundry at
http://pgfoundry.org/tracker/?func=detail&atid=126&aid=195&group_id=
107
//Magnus
--
Then let me rephrase - it's fixed in the MSI installers released after
beta-2, because we waited for a couple of specific fixes before we made
those (that's why they were aclled beta2-dev1 etc, and not plain beta-2)
//Magnus
---(end of broadcast)--
it. (Just disabling
it may not be enough). also, see the specific question about this
problem on http://pginstaller.projects.postgresql.org/FAQ_windows.html
for tip on a tool that might help you to determine what is wrong.
//Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
n 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
It should be enabled by default in the pginstaller installation.
//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
expect the installer to know about them all. We
can help a bit, though :-)
> Installer should be changed to check/grant the two other
> needed permissions, and should also add postgres user to
> 'Users' group when creating the postgres account to run as a
>
ropean Daylight Time LOG:
>could not receive
>data from client: An operation was attempted on something that is not a
>socket.
This sounds a lot like FAQ item 3.2 on
http://pginstaller.projects.postgresql.org/FAQ_windows.html. Check those
instructions as a first step.
//Magnus
--
ostgresql.org/FAQ_windows.html, please
check the contents of your PU and Adm groups. They may contain other
nested groups.
//Magnus
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
etLimiter is known to cause problems with PostgreSQL (along with some
other apps). It is just the kind of LSP that often breaks things.
//Magnus
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
>from examining errno. Using GetLastError() on those socket calls might
>help reducing support requests.
Nope. The error is exactly the one stated. "Socket operation attempted
on something that is not a socket". This is what's returned from
GetLastError().
//Magnus
---
7;t work, which is not a good start :-)
Yes, if this ia default in a bunch of installations, we certainly
should. I've added a tracker to the installer to check for htis, and
we'll try toget it in there before release. I will also add it to the
installer/windows FAQ.
//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
> it, it wasn't there.
See above about required rights (they're even in the FAQ). You definitly
do *not* need Act as part of the OS - that is a *very* sensitive right
that's not even granted to Administrators by default.
Yes, it's certainly a bit unpolished so far. B
there, but it should look for that file under
> Program Files/PostgreSQL/8.0-beta2-dev3/share/contrib.
Hello.
This has been fixed in the pginstaller cvs and will be included in the
next beta release.
//Magnus
---(end of broadcast)--
will run initdb
with the account specifeid as the service user. If you need to run
initdb manually, you should do this with that same account, which must
not be an administrator.
//Magnus
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
no problem using a domain account instead of a local account. If you get the
new installer (released yesterday - beta3dev1), it defaults to this on Domain
Controllers.
Just make sure the account is *not* an administrator. You can use any Domain
Administrator account to start the installation, but the se
omething has changed there, that could be the reason.
That said, I haven't noticed these symptoms myelf, so I'd check the
other suggestions first.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unre
tor) on win32, you will se the unix like
behaviour.
Not sure if we want to add a workaround for that? It'd be needed for
every single command, so I personally don't think it's a good idea.
//Magnus
---(end of broadcast)---
T
>> No bug; these objects exist in the template1 database -
>someone created
>> them there - so they get copied into every new database. This is a
>> _feature_. It lets you ensure that every new database
>contains certain
>> objects.
>>
>
>I believe
e request"
>
> can you help me to solve this problem?
> is there any patch for windows 2003?
Please see the pginstaller FAQ on
http://pginstaller.projects.postgresql.org/FAQ_windows.html,
specifically questions 3.1 and 3.2. Remember to check your server log
(it's in the pg_log sub
is DOA in version 8.
Please register your bug with the pginstaller project on pgfoundry.org.
This is a clear installer issue, not a backend issue. Thanks.
//Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
icting version of LIBEAY32.dll in your system32
directory. What version do you have there? ANd do you know where it
comes from?
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
ort if the problem has already been fixed.
Please download and try beta4. There used to be issues with XP Home, but
I beleive they have all been fixed.
//Magnus
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
e time, and I've had zero problems with this. Just input the
same username and password and it shuold be picked up and used without any
problems.
What errors are you seeing exactly?
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
rror is
>always the same. The
>> error message returned to the client is "SSL error: sslv3
>alert handshake
>> failure". The log reports: "could not accept SSL connection: 1".
>
>The only SSL changes between beta3 and beta4 were Magnus'
tream, and it doesn't have a versioninfo tag...
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
when you try the
install. If it doesn't, try enabling logging from Windows Installer by
running:
msiexec /l*v logfile.txt /i postgresql-8.0.0-beta5-en.msi
and then check the contents of logfile.txt.
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
erything else went into
>
>C:\Program Files\PostgreSQL\8.0.0-beta5\*
This sounds like you changed the target path only of the "Development"
sub-feature, and not the "root" item in the feature tree. The installer
supports both setting on the "root" item to move the
libraries in the
MSI build. Dave - we do this for some other package already, don't we?
//Magnus
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 30, 2004 8:49 PM
> To: Tom O'Connell
> Cc: [EMAIL PROTECTED]
>
Users or Authenticated Users or similar to the
Power Users or Administrators group, perhaps with indirection. Or some
other evil along that line.
//Magnus
> -Original Message-
>
> Hi,
>
> I and my colleagues are clearly able to install the beta 5
> version on Windows
e the FAQ with this.
(Previously we checked for Users, Authenticated Users and Everyone).
//Magnus
> -Original Message-
> From: Mehul Doshi-A20614 [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 02, 2004 9:45 AM
> To: Magnus Hagander; [EMAIL PROTECTED]
> Subject: RE: [BUGS
g locally)
> by changing the postgresql.conf from:
> listen_addresses = '*'
> to:
> listen_addresses = '127.0.0.1'
You're saying this only happens if listen_addresses='*'? *very*
interesting.
Are you running this off the console or through a RDP sessio
staller or the installed
version of PostgreSQL to either hang or crash. Remove the cygwin\bin
directory from your path before running the installer!
Unless you have some further information on which libraries would be
missing? We have had no other reports of that...
//Magnus
-
dard security products, or done any
lockdown from the standard level of the system? So that perhaps the
postgres account doesn't have access to required DLL files?
Also, when this happens, can you check the contents of
8.0.0-rc2\tmp\initdb.bat and see if the paths entered there are correct?
Fi
staller to the pginstaller-devel list.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Pit Müller
> Sent: Monday, December 27, 2004 1:06 PM
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] German Win32 Setup (V8 RC2)
&
es, and it's because the
detection code in the installer is not working as it's supposed to. It's
based on an environment variable :-)
Log in using /console, start a cmd.exe prompt, run "set
SESSIONNAME=Console", and then start the installer. That shoul
7'.
>
>The database is created with UNICODE encoding. The problem is
>present with
>version 8.0.0-rc2.
UNICODE encoding is not properly supported on Win32 at this time.
//Magnus
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
ry (first, then the ecpg dir that is failing).
//Magnus
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of T.J.
>Sent: den 2 januari 2005 03:26
>To: pgsql-bugs@postgresql.org
>Subject: [BUGS] BUG #1369: RC3 Compilation fails on mingw
if (!SHGetSpecialFolderPath(NULL, tmppath, CSIDL_APPDATA,
FALSE)) {
return FALSE;
strcat(tmppath,"/.postgresql/");
if (strlen(tmppath) > bufsize)
return FALSE; /* Better than returning a chopped-off
path */
strcpy(buf, tmppath);
return TRUE;
}
You're going to have to add #include to the file as well.
//Magnus
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
adable from http://www.hagander.net/pgsql/postgres_shmem.zip.
Replace your postgres.exe from this file, and then copy postgres.exe
over postmaster.exe (they should be identical). I wouldn't recommend
this solution for long, but if you're still in a testing environment it
mi
y broken when you fiddle with certificates. Unless
something broke fairly recently. Sometime back around beta2 or beta3 I
sent a patch to make it compile and work on win32. But I only touched
the server side of things. It worked in my simple tests using psql, but
I did nothing fancy with certificates.
//Ma
to RC4 that's out now. This handling has not
changed, but there are multiple other fixes.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
while to add a notice to the installation instructions
and/or FAQ about this. Will look into that.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Christoph Becker
> Sent: Wednesday, January 12, 2005 11:14 AM
> To: pgsql
a feature request on the pgFoundry page for this so it's not
forgotten. It won't be there in time for 8.0, but it shouldn't be too
much work to add it in a followon release.
//Magnus
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
#x27;m not 100% sure on that. It currently supports Python23, which is also
in the installation instructions. If someone can confirm that we need
only the DLL, we can definitly include it in our distribution.
So - can someone who knows enoughh aboyt plpython speak up on that one?
//Magnus
---
or it. See the FAQ question 3.6.
//Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> Magnus Hagander wrote:
> >This information is still in the documentation, it has moved to a
> >different location. It's in the docmentation for the psql tool now.
> >(It's under Client Application)
>
> Yes it is, but the message in the source code h
o we can try to determine why it's not working as expected.
> By this there will be an new directory for every release,
> which seems reasonable.
That's why it's the default. But it's by no means required.
//Magnus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ry to create a database with chars > 127,
but I'm not 100% sure on that. I would *guess* that psql is the only one
where people will actually care...
//Magnus
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an ap
Never seen this one. Can you run it with debugging enabled (-d option to
initdb) and see if it gives you any more data.
Are you doing something different as compared to the initdb the MSI did?
Different encoding or such?
//Magnus
>-Original Message-
>From: [EMAIL PROTECTED]
&g
ecause it clearly replaced it with an older version.
(Now granted the openssl DLL files don't contain version information -
something I'm in contact with the openssl guys about - but that's not an
excuse for the installer to downgrade it. It just makes life a lot
harder for th
as above. If that' not right, please post the exact
error message. Also, if the above does not solve the problem, exactly
which RC version is this?
//Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ing
>the current registry set.
The beta is seen as a completely different version, intended to be
capable of side-by-side installation. If we defaulted to where the other
one is installed, there is a risk of conflicting files.
That said, for 8.0.1 we are hoping to have a better upgrade path
are uninstalled. I have tested this several times,
and it has always worked in my tests.
Do you ahve any other software installed that may have provided a
libpq.dll`?
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
ve". Then expand the node. None of the
>sub-features have been selected for installation.
>
>At least one of those sub-features should have been enabled for
>installation.
This is not a bug. You need to select "Entire feature will be installe
gt;
>When the installer try to initialize the database cluster the following
>message is visualized:
>"Failed to run initdb: 1!
> Please see the logfile in
> \tmp\initdb.log
> Note You must read/copy this logfile before you click
> OK, or it will be a
ssage says it will not install in TS and requires a console terminal.
>
>We usually do not have monitors on the servers themselves.
>
>Can this be changes?
Please see the FAQ at
http://pginstaller.projects.postgresql.org/FAQ_windows.html#3.5 for a
workaround.
//Magnus
, you *must* remove them manually before you install 8.0.1,
because they will *NOT* be upgraded by the installer.
Another workaround is to back out to a previous RC which does not
contain this functionality at all.
//Magnus
---(end of broadcast)
gt; I have tested this problem many times.
You need to look in your server logs (in the pg_log directory) for hints
about what's wrong.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
r while processing sql-command'
>
>
>I hope you can help me.
You need to look in your server logs (in the pg_log directory) for hints about
what's wrong. The above output is only from the client.
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
would have saved me a lot of grief if the tool was
>mentioned in the
>instalation FAQ (as some posts referred to, but the FAQ must have been
>changed). Should the tool be mentioned in the FAQ?
Yes. It was there during RC, but it was beleived that we had a
workaround in place th
a socket in a way forbidden by
> its access permissions."
I'd put my bet down on a host based firewall, antivirus or similar
software that's not permitting the opening of network server sockets.
You will need to disable that protection and/or uninstall the software
that's pr
, or anonymous SMB (which
you *really* should have turned off)
*) use psql's \copy command. This one will write the file from the
client, and using your own windows account, so it shuold work fine with
mapped drives. This is what I'd recommend if you're doing one-off
nstalling PostgreSQL 8 and choose folder for
> installation different from default any way it's installed to
> default path
See http://pginstaller.projects.postgresql.org/FAQ_windows.html#3.6
//Magnus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
eported, no logs generated.
Did you check both eventlog and the pg_log directory? If so, try setting
the log_destibation parameter to log to eventlog only, in case there is
a problem starting the logger process, and see if you get something in
the eventlog then.
//Magnus
--
ile (for visual C++) in CVS and apply
corresponding changes to the Borland files.
//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
ermissions are normal. They are set on all directories
except the data directory, as a security precaution. There is no need
whatsoever for postgresql to be able to write to its own .EXE and .DLL
files.
//Magnus
---(end of broadcast)---
TIP 2: you can g
sure the postgres service account has read permissions on all the
files in the TCL directories.
If things look right, please run depends.exe (it's in the windows
support tools) on pltcl.dll to see exactly what breaks.
//Magnus
---(end of broadcast)
printf(stderr, "%s", buf.data) in
send_message_to_server_log should probably be a write_stderr, shouldn't
it? Or will that break the redirect_stderr stuff?
On another note, is it really good for guc to be calling ereport()
before it has loaded the config options for ereport, or are
ts be set to the result of a function? If so we could use the
service checking function to change the default value,perhaps?
//Magnus
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining
changed de characters enconding from UNICODE to ASCII
> and the problem still happens.
>
> Is this a bug or am I doing something wrong.
UNICODE is not supported on Win32.
ASCII does not know how to handle those characters.
You need to pick the correct encoding
You need to look a bit earlier in the logfile to
determine where the error is - the log you have here is only from the MSI
rollback.
How far into the installation do you get befoer it
fails?
//Magnus
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
JuuSent
is readable etc.)
What are the permissions on c:\pgtest and what are they on c:\? For the
postgres service account, of course.
//Magnus
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Title: Message
Yes,
those are not related at all to the actual error.
Can
you zip up the full log and send it to me off-list? It's still missing the
important part :-) Either that, or windows installer isn't telling us the
important part...
//Magnus
-Original Messag
gt; "Please use the main MSI file to install PostgreSQL"
>
> Thank you!
You are probably clicking on postgresql-8.0-int.msi. You need to use
postgresql-8.0.msi.
//Magnus
---(end of broadcast)---
TIP 9: the planner will i
are no connections at all?
If you connect to the server with psql and do a "select * from
pg_stat_activity", do they show up?
Do you get anything in the log, either in the pg_log directory or in the
eventlog?
//Magnus
---(end of broadcast)--
than one location. The number of locations depends on which features you
installed and where).
When
this is done, delete the files in SYSTEM32 (all three) and copy back the
original DLL files.
//Magnus
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Beh
ta directory "D:/E-NetAware-Data/db"
Are you by any chance running this through terminal services? This looks
just like the error message you get if you try that.
//Magnus
---(end of broadcast)---
TIP 8: explain analyze is your friend
rong service account password (one that
you will not be logging in as regularly) is now up to 31, but the
installer will warn you at 14.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
to server: Connection refused (0x274D/10061)
>Is the server running on host "???" and accepting TCP/IP
>connections on port
>5432?
>
>After the installation a few days ago of PostgreSQL 8.0
>everything works
>fine, but now the service does not start.
You'll need
>Joerg,
>
>I had this problem MANY times. Most often it was:
>
> - the service account lost it privilege to log on as a service
>
>we suspect it were some interfering group policies.
...
>that is NOT a postgreSQL problem, as long talks with magnus revealed
>... the rig
rs" interactive /delete
//Magnus
-Ursprungligt meddelande-Från:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
För Mehul Doshi-A20614Skickat: den 29 mars 2005
18:14Till: pgsql-bugs@postgresql.orgKopia: Mehul
Doshi-A20614Ämne: [BUGS] Enhancement: Remove NT/Interactive
s
quite a bit of time between account creation and the setting of
permissions.
//Magnus
-Ursprungligt meddelande-Från:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
För Mehul Doshi-A20614Skickat: den 29 mars 2005
18:20Till: pgsql-bugs@postgresql.orgKopia: Mehul
Doshi-
(use it for swedish chars all the time). Make sure you really switched the
server side encoding (new initdb), and not just the client side.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
st)
>i guess it's useful to know that there is a concurrent-login
>prohibiton policy, and event log says
As long as you only run one service, Windows only makes one login for
the user, so this shouldn't be the problem. Do you get this error every
time you try to start the service?
Note : There is no problem with the username,p/w and
>privileges as it is
>the same given to both /qr and /qn option.
>Please let me know how to correct this.
That should work - very interesting. Can you run it with logging enabled
and see what error you get in the log j
r specifically enable postgresql to listen and
communicate on tcp port 5432 (unless you changed the port, of course).
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
tracting postgre from the archive to no
>avail. Thanks.
The installer will reset all its information if you restart it (unless
you completed the install in which case some information is retained. To
lose all there, uninstall the product).
To solve your problem, though, I think you just need to d
SAStartup in makeEmptyPGconn?
>If we have
>one in DLL attach, isn't that sufficient?
Not if you link libpq as a static lib...
I *think* that's why it was added. In the beginning it was only in the
DLL attach code, and if you were using the library as a static lib you
had to cal
. If you're
downloading the no-installer version, you will need to get these files
from the OpenSSL distribution, it's linked from www.openssl.org.
//Magnus
---(end of broadcast)---
TIP 2: you can get off all lists at once with the
this an install from the official MSI? If so it really should've
found it out and alerted you :-( If it's source or some other packagnig,
you'll have to deal with it on your own.
//Magnus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
stion me if there is anything I can
> do to help with.
> Thank you.
Whare are your database encoding and locale in the two different
installations?
//Magnus
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
tp://www.postgresql.org/docs/faqs.FAQ_MINGW.html
and finally
http://www.postgresql.org/docs/8.0/static/installation.html
Those combined should give you what you need.
//Magnus
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
sql-hackers/2005-05/msg00662.php
//Magnus
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
irror did you download this file from? If you've always tried the
same, please try another one.
A bad version of this file was initially uploaded at the 8.0.3 release,
but it was replaced with a correct one a long time ago. Perhaps there is
a mirror out there that h
Please see the FAQ and the archives of the mailing lists. This has come
up before. It's permissions issues on your D: drive or subdirectories.
//Magnus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Paolo Petranzan
> Sent: Tuesd
s (äöü), but it seems like
> convert() does NOT convert the german "ß" / sharp s / ß...
PostgreSQL 8.0 does not support UTF8 on Win32. You will need to convert the
file before you load it into the database - look at for example the GNU iconv
program to do this.
//Magnus
ersion should work the same on all platforms,
> shouldn't it?
I thought that was also handled in the locale code. But now that you say
it, it's probably not - it should be the same.
I'll withdraw my comment then, clearly wrong. Thanks for clearing that
up.
//Magnus
*replace* what's there now.
//Magnus
---(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
301 - 400 of 556 matches
Mail list logo
