On Wed, Mar 2, 2016 at 4:25 PM, Tom Lane wrote:
> "David G. Johnston" writes:
> > The fact that the first two are only LOG level and not WARNING would
> seems
> > like the easiest improvement to make.
>
> Unfortunately, that would be a disimprovement, because in many common
> configurations WAR
"David G. Johnston" writes:
> âThe fact that the first two are only LOG level and not WARNING would seems
> like the easiest improvement to make.
Unfortunately, that would be a disimprovement, because in many common
configurations WARNING messages don't appear in the postmaster log at all.
In f
On 03/02/2016 02:49 PM, Tom Lane wrote:
Or maybe the problem was that when we forced track_counts off because of
no stats collector, we didn't emit any bleat noting that, which if we had
might have led you to realize that the above messages were the direct
cause of the next one:
2016-03-02 14:
On Wed, Mar 2, 2016 at 3:49 PM, Tom Lane wrote:
> Derek Elder writes:
> > That was indeed the root cause. The /etc/hosts file on the server had
> > incorrect permissions which caused localhost to not resolve.
>
> It strikes me that this should not have been so hard to solve. The
> stats collect
Derek Elder writes:
> That was indeed the root cause. The /etc/hosts file on the server had
> incorrect permissions which caused localhost to not resolve.
It strikes me that this should not have been so hard to solve. The
stats collector was trying to tell you what was wrong, but evidently
you c
The root cause ended up being an /etc/hosts file with incorrect
permissions, but I'll file this command away in the knowledge base.
Thanks for the assist Alvaro!
Derek
On Wed, Mar 2, 2016 at 1:36 PM, Alvaro Herrera
wrote:
> Derek Elder wrote:
>
> > From what I had read, this setting should be
That was indeed the root cause. The /etc/hosts file on the server had
incorrect permissions which caused localhost to not resolve.
Going to file this away in the knowledge base. Thank you so much for the
help David!
Derek
On Wed, Mar 2, 2016 at 1:37 PM, David G. Johnston <
david.g.johns...@gmail
On Wed, Mar 2, 2016 at 2:29 PM, Derek Elder wrote:
>
> 2016-03-02 14:58:09 EST [14366]: [8-1] LOG: could not resolve
> "localhost": Name or service not known
> 2016-03-02 14:58:09 EST [14366]: [9-1] LOG: disabling statistics
> collector for lack of working socket
>
I'm reasonably certain the abo
Derek Elder wrote:
> From what I had read, this setting should be on by default. When I checked
> our other servers I see that track_counts is on and the autovacuum process
> is working correctly on them. Indeed we don't even have the setting
> explicitly listed in our postgresql.conf on these ser
Good day,
(I apologize if this isn't the right place for this, I haven't used the
mailing list before and I'm not a Postgres expert.)
We've run into an issue where autovacuum is not running on one of our
servers using 9.4.5.
We discovered that track_counts appears to be off:
2016-03-02 14:58:09
10 matches
Mail list logo
