On 11/13/2015 09:56 AM, db042190 wrote:
I looked at event viewer in both Application and System. Neither shows
anything unusual around that time, just Volume Shadow Copy service stopping.
Hmm, is something trying to run a backup over your Postgres data
directory at the same time you are runni
ok, I poked around and see a reload config option in pg admin iii. I guess
i'm ready to go.
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-no-data-tp5873720p5873846.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent
I looked at event viewer in both Application and System. Neither shows
anything unusual around that time, just Volume Shadow Copy service stopping.
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-no-data-tp5873720p5873841.html
Sent from the PostgreSQL -
run this on pg admin III to reload SELECT pg_reload_conf() ?
Also, I now see the format for multiple log line prefixes...blank after
each choice including last. I will try that once i'm comfortable with how
I'll be reloading postgres.
--
View this message in context:
http://postgresq
On 11/13/2015 08:39 AM, db042190 wrote:
currently, log line prefix is log_line_prefix = '%t '.
Not sure what the blank following the t does.
The blank is so this happens:
2015-11-10 00:55:11 EST HINT
^
It is a literal space to separate the log prefix from the log messa
a couple of these say cant be changed after session start. Is that the same
as reload? Can I change it back if I do a reload?
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-no-data-tp5873720p5873832.html
Sent from the PostgreSQL - general mailing list
currently, log line prefix is log_line_prefix = '%t '.
Not sure what the blank following the t does.
u probably want me to change it to log_line_prefix = '%t%a%u%d%r%h%p% ' or
something like that?
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-no-data
On 11/13/2015 07:56 AM, db042190 wrote:
pls remember that since the switches didn't run, this all (or mostly) could
be related to an unknown process. My bad component appears to have started
around 54 seconds into nov 10. The overall job appears to have ended around
Actually 54 minutes, which
it looks like a lot of the log attributes ion the config are defaulting,
probably to NOTICE. I see a # in front of many. If the community can
advise on better choices and how bad the footprint would be for me to change
these, pls let me know. I'm guessing the log excerpt I posted isn't telling
u
pls remember that since the switches didn't run, this all (or mostly) could
be related to an unknown process. My bad component appears to have started
around 54 seconds into nov 10. The overall job appears to have ended around
01:01:44 which makes me wonder if a lot of the EOFs are related to som
On 11/12/2015 11:49 AM, db042190 wrote:
I see "unexpected eof...could not receive data..target
machine actively refused it.".
That sounds like the same error message as discussed here:
http://www.postgresql.org/message-id/4d75289d.9020...@techbaza.pl
Could it be a problem of too many open con
On 11/12/2015 12:54 PM, db042190 wrote:
there is something i need to correct. Coming out of one of the 3 switches
are two branches that cause updates to the same "interaction log" table in
postgres. Not text files like the other 2 switches.
Could you show a sample of the actual log error mess
On 11/12/2015 12:07 PM, Venkata Balaji N wrote:
Around that time I just see a bunch of "checkpoints are occurring too
frequently...". About a minute later and coincidentally around the
time the
pentaho job ends, I see "unexpected eof...could not receive data..target
machine actively refused it
there is something i need to correct. Coming out of one of the 3 switches
are two branches that cause updates to the same "interaction log" table in
postgres. Not text files like the other 2 switches.
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-n
thx, the fact that the query runs under pentaho at least half of the time
(used to be most of the time) makes me think it will run on the db. I'll try
to get a handle on the cpu/handle info u requested.
--
View this message in context:
http://postgresql.nabble.com/postgres-sometimes-returns-no-
thx both for responding.
Because the checkpoint settings probably haven't changed in a long long time
and we see as many of those warnings on good nights as bad I'm going to make
those priority 2. Unless there is a cause and effect u can explain between
checkpointing and what we are experiencin
On Fri, Nov 13, 2015 at 6:49 AM, db042190
wrote:
> Hi. We have a postgres 9.1 query in a pentaho job (table input component
> contains the query and is followed by various switches) that runs nightly.
> More and more frequently (about half the time now), the query returns no
> data (or appears t
On 11/12/2015 11:49 AM, db042190 wrote:
Hi. We have a postgres 9.1 query in a pentaho job (table input component
contains the query and is followed by various switches) that runs nightly.
More and more frequently (about half the time now), the query returns no
data (or appears to return no data,
Hi. We have a postgres 9.1 query in a pentaho job (table input component
contains the query and is followed by various switches) that runs nightly.
More and more frequently (about half the time now), the query returns no
data (or appears to return no data, see last paragraph) when there is
clearl
19 matches
Mail list logo
