On 4/08/2011 12:36 AM, Kevin Grittner wrote:
"Snehad Agrekar" wrote:
the server doesen't accept connections: the connection library
report could not connect to server: connection
refused(0x274D/10061) is the server running on host
"localhost" and accepting tcp/ip connection on port 5432?
On 3/08/2011 7:20 AM, Craig Ringer wrote:
On 2/08/2011 8:01 PM, Steve Boyd wrote:
"could not open process token: error code 5"
The service account is in the local administrators group and has full
control over the data directory.
AFAIK PostgreSQL service account should *NOT* be part of the l
On 3/08/2011 9:23 PM, Steven Boyd wrote:
Craig,
Good morning!
Working in IT, I understand how hard it is to troubleshoot an issue
with an incomplete picture. I wanted to tell you that your suggestion
worked! I removed the postgres account from the local administrators
group, restarted the VM
The following bug has been logged online:
Bug reference: 6146
Logged by: Matthias Kurz
Email address: m.k...@irregular.at
PostgreSQL version: 9.1beta3
Operating system: Ubuntu 11.04 64 bit
Description:COLLATE in ORDER BY not working with column names
defined with "AS"
"Gary Durbin" writes:
> The following bug has been logged online:
> Bug reference: 6145
> Logged by: Gary Durbin
> Email address: hac...@synchsource.com
> PostgreSQL version: 8.4
> Operating system: Linux
> Description:Drop View hangs on lock
> Details:
> Drop view
The following bug has been logged online:
Bug reference: 6145
Logged by: Gary Durbin
Email address: hac...@synchsource.com
PostgreSQL version: 8.4
Operating system: Linux
Description:Drop View hangs on lock
Details:
Drop view tries to get an exclusive lock on a view
"Snehad Agrekar" wrote:
> the server doesen't accept connections: the connection library
> report could not connect to server: connection
> refused(0x274D/10061) is the server running on host
> "localhost" and accepting tcp/ip connection on port 5432?
This is not a bug. It would be more a
The following bug has been logged online:
Bug reference: 6144
Logged by: Eduard Kracmar
Email address: eduard.krac...@gmail.com
PostgreSQL version: 8.4.8
Operating system: Debian/testing
Description:Postgres ignores locale's p_cs_precedes and
n_cs_precedes settings
De
The following bug has been logged online:
Bug reference: 6143
Logged by: Snehad Agrekar
Email address: snehadagre...@gmail.com
PostgreSQL version: 9.0.1 windows
Operating system: windowsxp 2
Description:connection problem
Details:
the server doesen't accept connecti
The following bug has been logged online:
Bug reference: 6142
Logged by: Snehad
Email address: snehadagre...@gmail.com
PostgreSQL version: 9.0.1 windows
Operating system: win-xp-2
Description:error while opening pdadmin
Details:
after opening pgadminIII i tried doub
Exactly so :-) (Seems simpler and I wouldn't have thought it would be a
problem to just remove the one, very small, file after the copy)
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Postgres-running-but-no-postmaster-pid-tp4662510p4662780.html
Sent from the PostgreSQL
Excerpts from simon.marshall's message of miƩ ago 03 11:56:55 -0400 2011:
> In fact, looking at it further, we stop the database (only continuing if this
> succeeds), copy our backup data over, remove the copied over postmaster.pid,
> make some config. changes and then (again, only if all this succ
In fact, looking at it further, we stop the database (only continuing if this
succeeds), copy our backup data over, remove the copied over postmaster.pid,
make some config. changes and then (again, only if all this succeeds), start
the database again, which should surely recreate postmaster.pid?
-
Thanks for your speedy response Tom. Seems like that is indeed what happens
elsewhere in the convoluted mess that are our backup scripts. Am
disappointed I didn't think of grepping for that myself! Too high a view of
my colleagues, now going downhill ;-)
Thanks,
Simon
--
View this message in cont
"simon.marshall" writes:
> When I came to stop my postgres instance (in particular, a replication
> database using postgres version 9.0.3 running on port 5442) today it failed
> to stop because the postmaster.pid instance wasn't present, despite the
> process still running (seen by running ps -eaf
Hi guys,
When I came to stop my postgres instance (in particular, a replication
database using postgres version 9.0.3 running on port 5442) today it failed
to stop because the postmaster.pid instance wasn't present, despite the
process still running (seen by running ps -eaf | grep post and noting
16 matches
Mail list logo