On Wednesday 23 May 2007 1:04 pm, George Pavlov wrote:
> Hoping to resurrect this thread. I am seeing more and more of
> this as the database gets more usage and it really messes up
> query log analysis.
>
>
> A quick summary: When I posted this was getting corrupted
> query log entries. I still am
On Friday May 20 2005 10:20 am, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I asked this on general, but got no answer on this
> > particular point, maybe someone here knows. Are blobs are
> > stored in the shared memory cache upon retrieval?
I asked this on general, but got no answer on this particular
point, maybe someone here knows. Are blobs are stored in the
shared memory cache upon retrieval?
I ask because we're trying to decide whether to store an enormous
number of images in PostgreSQL, and I'd be concerned that
frequen
On Wednesday March 23 2005 5:14, Mark Kirkwood wrote:
> - decide on a snapshot interval (e.g. 30 seconds)
> - capture pg_stat_activity every interval and save the results
> in a timestamped copy of this view (e.g. add a column
> 'snap_time')
That might serve for some purposes, but log-parsing soun
On Wednesday March 23 2005 3:34, Tom Lane wrote:
>
> This is going to fall down on exactly the same objections that
> have been made to putting the log messages themselves into
> tables. The worst one is that a failed transaction would fail
> to make any entry whatsoever. There are also performanc
On Wednesday March 23 2005 4:11, Mark Kirkwood wrote:
> Is enabling the various postgresql.conf stats* options and
> taking regular snapshots of pg_stat_activity a possible way to
> get this?
I don't see how; the duration is the key measurement I'm after,
and I don't believe it is available anywh
Hackers,
I'd like to pose a problem we are facing (historical query time
profiling) and see if any of you interested backend gurus have
an opinion on the promise or design of a built-in backend
solution (optional built-in historical query time stats), and/or
willingness to consider such a pat
I asked this on general, but didn't receive any responses. Is it possible
via SQL to identify the time of the last stat reset (or pg_stat_reset()
call)? This is what I'm lacking to be able to measure query activity
volume over time via SQL. Maybe a function similar to the fictitious
pg_stat
Wow. First, thanks again for all your efforts, Jan. Second, I'm
disappointed to hear the slony author and lead developer is leaving the
slony leadership. When is that going to happen? And what does that mean
with respect to your future involvement in slony?
Ed
On Friday October 22 2004 7:
On Friday April 4 2003 2:17, scott.marlowe wrote:
>
> OK, So I tried putting the 2>&1 before the | and all. No matter what I
> try, every from the | on is ignored. ps doesn't show it, and neither
> does pg_ctl status. Both show a command line of
> /usr/local/pgsql/bin/postmaster as the only inpu
On Friday April 4 2003 11:58, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > rotatelogs is in my path and all, it just never sees it.
>
> You mean the command fails? Or just that it doesn't capture output?
>
> > "$po_path" ${1+"$@"} > 2>&1 &
>
> Most if not all of the postmaste
On Friday April 4 2003 10:24, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > When a sequence is created in 7.3.2, it appears you get a new table for
> > each sequence object. Is it ever possible for the sequence_name in a
> > sequence relation
On Friday April 4 2003 10:19, Tom Lane wrote:
>
> I feel we really ought to have *some* rotator included in the standard
> distro, just so that the Admin Guide can point to a concrete solution
> instead of having to arm-wave about what you can get off the net.
> If someone can offer a better altern
On Friday April 4 2003 10:04, Ed L. wrote:
> By way of feature ideas, one very convenient but not widely used feature
> of Apache's log rotator is the ability to specify a strftime() format
> string for the file extension. For example, if I want to have my logs
> rollover ever
On Friday April 4 2003 9:16, scott.marlowe wrote:
>
> That said, a log rotation capability built right into pg_ctl or
> thereabouts would be a very nice feature. I.e. 'pg_ctl -r 86400 -l
> $PGDATA/logs/pgsql start'
>
> where -r is the rotation period in seconds. If it's an external program
> that
When a sequence is created in 7.3.2, it appears you get a new table for each
sequence object. Is it ever possible for the sequence_name in a sequence
relation not to match the name of the relation itself?
For example, suppose I create a table:
CREATE TABLE t1(id serial);
A new relat
On Monday March 31 2003 3:54, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> >> I am seeing this same problem on two separate machines, one brand new,
> >> one older. Not sure yet what is causing it, but seems pretty unlikely
> >> that it
On Monday March 31 2003 3:38, Ed L. wrote:
> On Feb 13, 2003, Tom Lane wrote:
> > Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > > This is the error in the pgsql log:
> > > 2003-02-13 16:21:42 [8843] ERROR: Index external_signstops_pkey is
> > > not
On Feb 13, 2003, Tom Lane wrote:
>
> Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > This is the error in the pgsql log:
> > 2003-02-13 16:21:42 [8843] ERROR: Index external_signstops_pkey is
> > not a btree
>
> This says that one of two fields that should never change, in fixed
> positions in
19 matches
Mail list logo