Andres Freund writes:
> we could really do better than just wonder whether our signal to
> shutdown was received or not. There probably should be a quite short
> timeout for the server to change status, and then a much longer one for
> that shutdown to finish.
While I don't want to just raise th
On 2017-11-12 14:26:42 -0500, Tom Lane wrote:
> Christoph Berg writes:
> > The default systemd timeout seems to be 90s. I have already changed
> > the systemd timeout to infinity (start) and 1h (stop), so only the
> > default pg_ctl timeout remains (60s), which I'd rather not override
> > unilater
Christoph Berg writes:
> The default systemd timeout seems to be 90s. I have already changed
> the systemd timeout to infinity (start) and 1h (stop), so only the
> default pg_ctl timeout remains (60s), which I'd rather not override
> unilaterally.
> That said, isn't 60s way too small for shutting
Re: Tom Lane 2017-11-12 <20802.1510513...@sss.pgh.pa.us>
> Agreed, but I think Peter has a point: why is there a timeout at all,
> let alone one as short as 30 seconds? Since systemd doesn't serialize
> service starts unnecessarily, there seems little value in giving up
> quickly. And we know tha
Christoph Berg writes:
> Re: Peter J. Holzer 2017-11-12 <20171112173559.m6chmbyf4vz6f...@hjp.at>
>> Wouldn't it be better to remove the timeout?
> If you don't want to block, don't depend on the database service. That
> question is independent from the timeout.
Agreed, but I think Peter has a po
Re: Peter J. Holzer 2017-11-12 <20171112173559.m6chmbyf4vz6f...@hjp.at>
> Wouldn't it be better to remove the timeout? If some other service
> depends on PostgreSQL it probably shouldn't be startet until PostgreSQL
> is really up and services which don't need PostgreSQL (e.g. SSH or X11
> login or
On 2017-11-12 13:26:58 +0100, Christoph Berg wrote:
> Re: To Adam Brusselback 2017-11-11
> <2017205316.u56lkmkakdmcx...@msg.df7cb.de>
> > I'm investigating if it's a good idea to tell systemd to ignore the
> > exit code of pg_ctl(cluster).
>
> Telling systemd to ignore ExecStart errors seems
Re: To Adam Brusselback 2017-11-11
<2017205316.u56lkmkakdmcx...@msg.df7cb.de>
> I'm investigating if it's a good idea to tell systemd to ignore the
> exit code of pg_ctl(cluster).
Telling systemd to ignore ExecStart errors seems to be the correct
solution. The service will still be active, wi
Re: Adam Brusselback 2017-11-11
> Hey Christoph, I tried starting it with init (service postgresql
> start), and pg_ctlcluster.
>
> I modified the pg_ctl.conf and set the timeout higher so I could just
> get my cluster back up and running properly, so I can't give you the
> info on what systemct
Hey Christoph, I tried starting it with init (service postgresql
start), and pg_ctlcluster.
I modified the pg_ctl.conf and set the timeout higher so I could just
get my cluster back up and running properly, so I can't give you the
info on what systemctl status says at the moment.
On Sat, Nov 11,
Re: Tom Lane 2017-11-10 <8027.1510347...@sss.pgh.pa.us>
> > The recovery succeeds, but when I go to start the cluster on the
> > standby, it begins to replay the WAL, and does so for about 30
> > seconds. Then I get a line in my log saying:
>
> >> pg_ctl: server did not start in time
Hi Adam,
h
Adam Brusselback writes:
>> You might want to increase pg_ctl's wait timeout for this situation,
>> since the default's evidently too little. However ...
> Got it, thanks.
>> ... pg_ctl itself wouldn't decide to forcibly shut down the server
>> if the timeout expired. It merely stops waiting a
On 11/10/2017 01:01 PM, Adam Brusselback wrote:
>> You might want to increase pg_ctl's wait timeout for this situation,
>> since the default's evidently too little. However ...
> Got it, thanks.
>
>> ... pg_ctl itself wouldn't decide to forcibly shut down the server
>> if the timeout expired. It
> You might want to increase pg_ctl's wait timeout for this situation,
> since the default's evidently too little. However ...
Got it, thanks.
> ... pg_ctl itself wouldn't decide to forcibly shut down the server
> if the timeout expired. It merely stops waiting and tells you so.
> It seems like
Adam Brusselback writes:
> I am in the process of upgrading to Postgres 10, and am having trouble
> getting my streaming replica working.
> OS: Debian 9.2
> Version: 10.1
> I have my primary backed up using pgbackrest, and I restore that to my
> replica. It generates a recovery.conf which has a r
Hey all,
I am in the process of upgrading to Postgres 10, and am having trouble
getting my streaming replica working.
OS: Debian 9.2
Version: 10.1
I have my primary backed up using pgbackrest, and I restore that to my
replica. It generates a recovery.conf which has a restore command for
the WAL
On 10/16/17 03:19, Thomas Kellerer wrote:
> I don't know if this is intentional, but the Postgres 10 manual started to
> use lowercase IDs as anchors in the manual.
>
> So, if I have e.g.: the following URL open in my browser:
>
>
> https://www.postgresql.org/docs/current/static/sql-createin
On 23/10/2017, 17:17, "George Neuner" wrote:
>Doesn't GCloud provide a way to export drive images?
[He asks naively, never having used it.]
Nope – just the dd method (although this doesn’t work on VMWare, so you need to
use a VWM utility on a Win pc to get it). I’m pretty sure Google use
On Mon, 23 Oct 2017 09:14:18 +0100, Martin Moore
wrote:
>Same server. I tried a few times.
>
>I didn’t move the db separately, but did a ‘dd’ to copy the disk
>to an imagefile which was converted and loaded into VMWare.
If you copied the boot device that way while the system was running,
then yo
OK, cheers.
How can I remove the db so I can restore it properly?
From: Scott Mead
Date: Monday, 23 October 2017 at 16:35
To: Martin Moore
Cc: Michael Nolan , "pgsql-general@postgresql.org"
Subject: Re: [GENERAL] Postgres 9.6 fails to start on VMWare
On Mon, Oct 2
52
> *To: *Martin Moore
> *Cc: *rob stone , "pgsql-general@postgresql.org" <
> pgsql-general@postgresql.org>
> *Subject: *Re: [GENERAL] Postgres 9.6 fails to start on VMWare
>
>
>
>
>
>
>
> On Mon, Oct 23, 2017 at 3:14 AM, Martin Moore
> wrote:
It was running – not sure how dd handles this. Maybe badly… ☺
From: Michael Nolan
Date: Monday, 23 October 2017 at 15:52
To: Martin Moore
Cc: rob stone , "pgsql-general@postgresql.org"
Subject: Re: [GENERAL] Postgres 9.6 fails to start on VMWare
On Mon, Oct 23, 2017
On Mon, Oct 23, 2017 at 3:14 AM, Martin Moore
wrote:
> Same server. I tried a few times.
>
> I didn’t move the db separately, but did a ‘dd’ to copy the disk to an
> imagefile which was converted and loaded into VMWare.
>
> I ‘believed’ that this should keep the low level disk structure the same,
Same server. I tried a few times.
I didn’t move the db separately, but did a ‘dd’ to copy the disk to an
imagefile which was converted and loaded into VMWare.
I ‘believed’ that this should keep the low level disk structure the same, but
if this has corrupted the files I can drop, dump and resto
On Sun, 2017-10-22 at 15:13 +0100, Martin Moore wrote:
> 2017-10-22 14:08:28 UTC [2479-1] LOG: 0: database system
> shutdown was interrupted; last known up at 2017-10-22 14:07:20 UTC
There is something missing here. Last shutdown at 2017-10-22 14:07:20
UTC on which server?
Then attempting t
On Sun, Oct 22, 2017 at 11:13 PM, Martin Moore wrote:
> I’ve migrated a running Debian Jessie system from a Google Compute instance
> to a VMWare ESXi 6.5 system.
How did you actually do this migration? It is really easy to finish
with a corrupted instance if not doing things correctly in this w
I’ve migrated a running Debian Jessie system from a Google Compute instance to
a VMWare ESXi 6.5 system.
Postgres won’t start, although returns [ok] :
/etc/init.d/postgresql start 9.6
[ ok ] Starting postgresql (via systemctl): postgresql.service.
2017-10-22 14:08:28 UTC [2479-1] LOG: 0:
On 10/17/2017 10:39 AM, Dillon Tang wrote:
***Must sit onsite in Cypress,CA or Eden Prairie, MN***
This is the wrong list. Please use pgsql-jobs.
Thank you,
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and dev
***Must sit onsite in Cypress,CA or Eden Prairie, MN***
What is the specific title of the position?
Senior posgreSQL Database Administrator Consultant
What Project/Projects will the candidate be working on while on assignment?
The candidate will be working on the EDSS to Documentum migration pro
I don't know if this is intentional, but the Postgres 10 manual started to use
lowercase IDs as anchors in the manual.
So, if I have e.g.: the following URL open in my browser:
https://www.postgresql.org/docs/current/static/sql-createindex.html#sql-createindex-concurrently
I cannot simply s
But what is your problem or error ? github's project doesn't support docker
images that enable and configure logical replication.
2017-09-19 10:33 GMT+02:00 Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com>:
> ++ Forwarding query to appropriate mail group.
>
>
> On Tue, Sep 19, 2017 at 3:00
++ Forwarding query to appropriate mail group.
On Tue, Sep 19, 2017 at 3:00 AM, guedim wrote:
> Hi guys
>
> I am working with Postgres9.6 with a Master/Slave cluster replication using
> Streaming replication.
> I would like to add a new Slave server database but this database with
> logical rep
On 14/09/17 16:11, Yogesh Sharma wrote:
>>What you could do is copying its contents to a large disk, and then
allow it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any comma
On 9/13/2017 9:11 PM, Yogesh Sharma wrote:
>>What you could do is copying its contents to a large disk, and then
allow it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any co
>>What you could do is copying its contents to a large disk, and then allow
it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any command is require to execute please let me know.
On Thu, Sep 14, 2017 at 12:44 PM, John R Pierce wrote:
> prior to that error, something else catastrophic must have happened to the
> system, that error is more of a side effect. recovering a database server
> that far gone which is running such an obsolete version will likely be an
> expensive pr
Dear all,
As current situation, i can not upgrade on higher version.
Is there any recovery command available?
Regards,
Yogesh
On Thursday, September 14, 2017, Gavin Flower
wrote:
> On 14/09/17 15:29, Yogesh Sharma wrote:
>
>> Dear All,
>>
>> Thanks in advance.
>>
>> We are using Postgres 8.1.
On 9/13/2017 8:29 PM, Yogesh Sharma wrote:
We are using Postgres 8.1.18 version.
In Postgres log, we found below logs.
–-
CONTEXT:writing block 0 of relation 1664/0/1260
ERROR: could not write block 0 of relation 1664/0/1260: Bad address
Due to this
On 14/09/17 15:29, Yogesh Sharma wrote:
Dear All,
Thanks in advance.
We are using Postgres 8.1.18 version.
In Postgres log, we found below logs.
–-
CONTEXT:writing block 0 of relation 1664/0/1260
ERROR: could not write block 0 of relation 1664/0/1260: Bad address
--
Dear All,
Thanks in advance.
We are using Postgres 8.1.18 version.
In Postgres log, we found below logs.
–-
CONTEXT:writing block 0 of relation 1664/0/1260
ERROR: could not write block 0 of relation 1664/0/1260: Bad address
Due to this pglog_Xlog dire
On Wed, Sep 6, 2017 at 1:16 AM, Vijay Chaudhery wrote:
> Ok is it possible to release the lock? or it is just a warning messages
> only?
> thanks
>
The message starts with "ERROR" so it is an error, not a warning. The
command failed. The only way to release the lock is to have the other
connecti
Ok is it possible to release the lock? or it is just a warning messages only?
thanks
-Original Message-
From: Tatsuo Ishii [mailto:is...@sraoss.co.jp]
Sent: 06 September 2017 10:31 AM
To: Vijay Chaudhery
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Postgres logs showing error
> Ok thank you,
>
> I have promoted slave server as master in postgres streaming replication ,
> howerver application is working fine after promotion , but getting some error
> messages in the postgres log (slave which promoted to master)
>
> what does it mean?
>
>
>>ERROR: could not obtain
t;."modified", "main_instance"."version",
"main_instance"."capacity" FROM "main_instance" LIMIT 1 FOR UPDATE NOWAIT
-Original Message-----
From: Tatsuo Ishii [mailto:is...@sraoss.co.jp]
Sent: 06 September 2017 10:02 AM
To: Vijay Chaud
> I am not sure if the sending email is the right way to get the forum help.
> Could you please let me know how to open forum query to ask postgres
> questions.
Sending email to this mailing list regarding your questions is the
perfect way to get help.
Other than this, there's an IRC channel fo
Hi,
I am not sure if the sending email is the right way to get the forum help.
Could you please let me know how to open forum query to ask postgres questions.
Thanks
vijay
::DISCLAIMER::
---
On Sun, Aug 20, 2017 at 7:19 AM, Enis Inan wrote:
>
> Hello,
>
> Is there a way I can access the ".po" files containing the English -> Foreign
> language translations of postgres' log messages? I only need the translations
> from English to Japanese for a project I'm working on.
>
> Thank you!
>
Hello,
Is there a way I can access the ".po" files containing the English ->
Foreign language translations of postgres' log messages? I only need the
translations from English to Japanese for a project I'm working on.
Thank you!
-Enis
Hi David, thank you for your reply.
David G Johnston wrote
> As the comment there says your config and your output seem at odds.
What I showed was the output present in the csv log, the output in the text
file log has the prefix that I indicated in the configration file.
Either way, I managed t
It is customary to indicate when you've posted the same question to other
forums - in this case SO.
https://dba.stackexchange.com/questions/180263/postgres-log-query-and-command-tag-to-csv
As the comment there says your config and your output seem at odds. Though
I think your confusion is still
I am trying to log executed queries into a csv file.
My main objective is to log the command tag and query. For that I enabled
logging in the postgresql.conf, my configs are the following:
#--
# ERROR REPORTING AND LOGGIN
You're right I have forgotten to say, the OS is RHEL 7.
Actually I'm reading about.
Thanks!
-
Dame un poco de fe, eso me bastará.
Rozvo Ware Solutions
--
View this message in context:
http://www.postgresql-archive.org/postgres-dbname-dbuser-9-9-9-9--PARSE-waiting-tp5968923p5969564.
On Fri, Jun 30, 2017 at 11:36 AM, DrakoRod wrote:
> > Do you control the app?
>
> Nop Just I know how it's developed.
>
> > The app has a pooling component and you still are having problems, have
> > you looked at what the pooler is actually doing?
>
> As far as I know, the wildfly's jdbc pool. N
> Do you control the app?
Nop Just I know how it's developed.
> The app has a pooling component and you still are having problems, have
> you looked at what the pooler is actually doing?
As far as I know, the wildfly's jdbc pool. No really I don't know what are
doing. I suspect that problem i
On Thu, Jun 29, 2017 at 7:30 PM, Adrian Klaver
wrote:
> On 06/29/2017 10:03 AM, DrakoRod wrote:
>
>> To expand information, the application are written in Grails on wildfly
>> with
>> pool connections.
>>
>
> Do you control the app?
>
> The app has a pooling component and you still are having pro
On 06/29/2017 10:03 AM, DrakoRod wrote:
To expand information, the application are written in Grails on wildfly with
pool connections.
Do you control the app?
The app has a pooling component and you still are having problems, have
you looked at what the pooler is actually doing?
I didn't
On Thu, Jun 29, 2017 at 10:03 AM, DrakoRod wrote:
> I can't close connections on the application side. How I close connections
> on the database side? With pg_terminate_backend, pg_cancel_backend or
> exists
> other function? I didn't want terminate backends because all connections
> state was ac
To expand information, the application are written in Grails on wildfly with
pool connections.
I didn't have time to check pg_locks with detail, I'll configure the
connections logs to monitoring those.
I can't close connections on the application side. How I close connections
on the database side
On Tue, 27 Jun 2017 16:16:53 -0700 (MST)
DrakoRod wrote:
> Yep, the real problem was all connections are used up. A ps command showed
> this:
>
> postgres 1172 23340 1 13:00 ?00:01:23 postgres: dbsomething
> dbsomething 8.8.8.1[34024] PARSE waiting
> postgres 1527 23340 3 13:07 ?
On 06/27/2017 04:16 PM, DrakoRod wrote:
Yep, the real problem was all connections are used up. A ps command showed
this:
postgres 1172 23340 1 13:00 ?00:01:23 postgres: dbsomething
dbsomething 8.8.8.1[34024] PARSE waiting
postgres 1527 23340 3 13:07 ?00:02:47 postgres: dbsome
Yep, the real problem was all connections are used up. A ps command showed
this:
postgres 1172 23340 1 13:00 ?00:01:23 postgres: dbsomething
dbsomething 8.8.8.1[34024] PARSE waiting
postgres 1527 23340 3 13:07 ?00:02:47 postgres: dbsomething
dbsomething 8.8.8.2[49193] PARSE wai
On Tue, Jun 27, 2017 at 3:41 PM, Melvin Davidson
wrote:
> *His problem is NOT 'idle in transaction' per se. It is all connections
> are used up.*
> *Hence the need for pg_bouncer for connection pooling.*
>
>
Whether pg_bouncer provides a viable solution is just as big an unknown as
whether "idle
On 06/27/2017 03:41 PM, Melvin Davidson wrote:
On Tue, Jun 27, 2017 at 6:32 PM, Adrian Klaver
*His problem is NOT 'idle in transaction' per se. It is all connections
are used up.*
Not following. The 'idle in transaction' queries are coming in through a
connection so having them around is
On Tue, 27 Jun 2017 18:41:25 -0400
Melvin Davidson wrote:
> On Tue, Jun 27, 2017 at 6:32 PM, Adrian Klaver
> wrote:
>
> > On 06/27/2017 01:10 PM, DrakoRod wrote:
> >
> >> Hi folks.
> >>
> >> Today I had a problem with production's database PostgreSQL version
> >> 9.4.4.9.
> >> The server have m
On Tue, Jun 27, 2017 at 6:32 PM, Adrian Klaver
wrote:
> On 06/27/2017 01:10 PM, DrakoRod wrote:
>
>> Hi folks.
>>
>> Today I had a problem with production's database PostgreSQL version
>> 9.4.4.9.
>> The server have max_connections set to 200, but today I reviewed
>> pg_stat_activity and saw 199
On 06/27/2017 01:10 PM, DrakoRod wrote:
Hi folks.
Today I had a problem with production's database PostgreSQL version 9.4.4.9.
The server have max_connections set to 200, but today I reviewed
pg_stat_activity and saw 199 active connections, obviously the server
rejected any new connection and th
On Tue, Jun 27, 2017 at 1:10 PM, DrakoRod wrote:
> postgres 9741 23340 9 14:55 ?00:00:47 postgres: dbname user
> 8.8.8.8[54286] idle in transaction
>
> Any suggestions?
>
There is a serious lack of information provided here but "idle in
transaction" sessions are generally problematic
On Tue, Jun 27, 2017 at 4:10 PM, DrakoRod wrote:
> Hi folks.
>
> Today I had a problem with production's database PostgreSQL version
> 9.4.4.9.
> The server have max_connections set to 200, but today I reviewed
> pg_stat_activity and saw 199 active connections, obviously the server
> rejected any
Hi folks.
Today I had a problem with production's database PostgreSQL version 9.4.4.9.
The server have max_connections set to 200, but today I reviewed
pg_stat_activity and saw 199 active connections, obviously the server
rejected any new connection and the production stopped.
I saw another posts
On 06/19/2017 12:40 AM, Scott Marlowe wrote:
On Sun, Jun 18, 2017 at 2:20 PM, Condor wrote:
What I should expect, what is good and bad things that can be happened.
I've run Postgres on a LUKS volume for a few years now and it's all been
pretty quiet. One challenge is you need to supply the p
On Sun, Jun 18, 2017 at 2:20 PM, Condor wrote:
> Hello ppl,
>
> a few years ago I asked the same question but did not receive valued answers
> and we use different way to realize the project.
> Today I wanna ask did some one do it and most important for me, can some one
> share his experience ?
>
Hello ppl,
a few years ago I asked the same question but did not receive valued
answers and we use different way to realize the project.
Today I wanna ask did some one do it and most important for me, can some
one share his experience ?
What I should expect, what is good and bad things that ca
Adrian Klaver schrieb am 28.05.2017 um 17:51:
After I finally found the EnterpriseDB Beta binaries (they are pretty well
hidden) I tested with those, and everything works fine there.
For those following along, where would that be?
Here they are:
https://www.enterprisedb.com/products-service
Thomas Kellerer writes:
> Tom Lane schrieb am 26.05.2017 um 20:18:
>>> The error message reported in the logfile is:
>>> pg_dump: unrecognized collation provider: p
>> Ugh :-( ... seems like a rather obvious typo in dumpCollation().
>> Thanks for finding it!
> When I drop that collation from the
On 05/28/2017 08:41 AM, Thomas Kellerer wrote:
Tom Lane schrieb am 26.05.2017 um 20:18:
Apparently BigSQL forgot to include contrib/xml2 in their distribution;
you should ping them about that one.
I can confirm that it's a BigSQL problem.
After I finally found the EnterpriseDB Beta binaries
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/po
Thomas Kellerer writes:
> Interesting enough, the same error message appears when I run "create
> extension xml2;" on Postgres 10.
Sure, that no doubt is exactly the command getting issued during the
pg_upgrade attempt.
> It somehow looks as if there is a DLL dependency between XML2 and whateve
Adrian Klaver schrieb am 26.05.2017 um 23:41:
If that's coming from port/dynloader/win32.c, as I think it must be
because the non-conformant-to-message-style-guidelines phrase "unknown
error" appears nowhere else in our tree, then that's an error code that
FormatMessage doesn't recognize. Anybod
Adrian Klaver schrieb am 26.05.2017 um 23:16:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/postgres-10/pgsql/lib/postgresql/pgxml.dll": unknown error 126
Apparently BigSQL forgot to include contrib/xml2 in their distribution;
you should ping them abo
On 05/26/2017 02:30 PM, Tom Lane wrote:
Adrian Klaver writes:
Well Thomas is using pg_upgrade from a BigSQL 10beta1 install to upgrade
from a 9.6 instance of unknown provenance. pg_upgrade is complaining
that the 9.6 cluster has pgxml.dll whereas the 10beta1 cluster does not
even though xml2 is
Adrian Klaver writes:
> Well Thomas is using pg_upgrade from a BigSQL 10beta1 install to upgrade
> from a 9.6 instance of unknown provenance. pg_upgrade is complaining
> that the 9.6 cluster has pgxml.dll whereas the 10beta1 cluster does not
> even though xml2 is installed on both clusters. The
On 05/26/2017 01:58 PM, Alvaro Herrera wrote:
Thomas Kellerer wrote:
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load
Thomas Kellerer wrote:
> Tom Lane schrieb am 26.05.2017 um 20:18:
> > > I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
> > > distribution) to upgrade a 9.6 cluster.
> > > pg_upgrade --check fails with the following messages:
> >
> > > could not load library "$libdir/pgxml
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/po
Thomas Kellerer writes:
> I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
> distribution) to upgrade a 9.6 cluster.
> pg_upgrade --check fails with the following messages:
>could not load library "$libdir/pgxml":
>ERROR: could not load library
> "d:/etc/postgres-10/
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
Performing Consistency Checks
-
Checking cluster versions ok
Checking d
Vamsi Patchipulusu writes:
> Error: psql.bin: could not connect to server: Cannot assign
> requested address
> Is the server running on host "abchost.corp.xyz.com"
> (xxx.xxx.xxx.xxx) and accepting
> TCP/IP connections on port 5432?
Googling suggests that this could oc
On Monday, May 15, 2017, Vamsi Patchipulusu
wrote:
>
> Error: psql.bin: could not connect to server: Cannot assign
> requested address
>
> Is the server running on host "abchost.corp.xyz.com"
> (xxx.xxx.xxx.xxx) and accepting
>
> TCP/IP connections on port 5432?
>
> Jmete
Hi All,
We are receiving below intermittent connection error during performance testing
on postgres.
Thanks in advance for any suggestion or pointers on how we can troubleshoot
this issue.
Error: psql.bin: could not connect to server: Cannot assign requested
address
Is the se
On Thu, Apr 27, 2017 at 6:38 PM, basti wrote:
> Hello,
>
> is there a recomment to set max_worker_processes and
> max_parallel_workers_per_gather per cpu core or thread?
>
This largely depends on what type of processing is done by parallel
workers, e.g. if the task is I/O bound then having workers
De : pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] De la part de Mark Watson
Envoyé : Monday, April 24, 2017 3:39 PM
À : David G. Johnston
Cc : (pgsql-general@postgresql.org)
Objet : Re: [GENERAL] Postgres 9.6.2 and pg_log
De : David G. Johnston
On Thu, Apr 27, 2017 at 6:18 AM, basti wrote:
> Hallo, we have a Postgres database Server and around that there are 8
> clients get data from it.
>
> All servers are the the same datacenter i think (traceroute only 4-5 hops)
>
> Now we plan to move the server to an other hoster/datacenter.
>
> I h
Hello,
is there a recomment to set max_worker_processes and
max_parallel_workers_per_gather per cpu core or thread?
Best regards
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hallo, we have a Postgres database Server and around that there are 8
clients get data from it.
All servers are the the same datacenter i think (traceroute only 4-5 hops)
Now we plan to move the server to an other hoster/datacenter.
I have done simple test with ping and traceroute.
Is there a wa
De : David G. Johnston [mailto:david.g.johns...@gmail.com]
Envoyé : Monday, April 24, 2017 3:15 PM
À : Mark Watson
Cc : (pgsql-general@postgresql.org)
Objet : Re: [GENERAL] Postgres 9.6.2 and pg_log
On Mon, Apr 24, 2017 at 11:27 AM, Mark Watson
mailto:mark.wat...@jurisconcept.ca>>
On Mon, Apr 24, 2017 at 11:27 AM, Mark Watson
wrote:
>
> log_destination = 'stderr' # Valid values are
> combinations of
>
>
> # stderr, csvlog, syslog, and eventlog,
>
>
> # depending on platform. csvlog
>
>
> # requires logging_collector to be on.
>
>
>
> # This is
De : David G. Johnston [mailto:david.g.johns...@gmail.com]
Envoyé : Monday, April 24, 2017 2:18 PM
À : Mark Watson
Cc : (pgsql-general@postgresql.org)
Objet : Re: [GENERAL] Postgres 9.6.2 and pg_log
On Mon, Apr 24, 2017 at 10:58 AM, Mark Watson
mailto:mark.wat...@jurisconcept.ca>> wrote
On Mon, Apr 24, 2017 at 10:58 AM, Mark Watson
wrote:
>
> The lines log_rotation_age and log_rotation_size are commented, and
> currently are:
>
> #log_rotation_age = 1d # Automatic
> rotation of logfiles will
>
>
> # happen after that time. 0 disables.
>
> #log_ro
De : David G. Johnston [mailto:david.g.johns...@gmail.com]
Envoyé : Monday, April 24, 2017 1:34 PM
À : Mark Watson
Cc : (pgsql-general@postgresql.org)
Objet : Re: [GENERAL] Postgres 9.6.2 and pg_log
On Mon, Apr 24, 2017 at 8:43 AM, Mark Watson
mailto:mark.wat...@jurisconcept.ca>> wrote
De : David G. Johnston [mailto:david.g.johns...@gmail.com]
Envoyé : Monday, April 24, 2017 1:34 PM
À : Mark Watson
Cc : (pgsql-general@postgresql.org)
Objet : Re: [GENERAL] Postgres 9.6.2 and pg_log
On Mon, Apr 24, 2017 at 8:43 AM, Mark Watson
mailto:mark.wat...@jurisconcept.ca>> wrote
1 - 100 of 2994 matches
Mail list logo
