, Rhhh Lin wrote:
[...]
> where timestamp BETWEEN 150667656 AND 150875022
[...]
> *Also, as a sidenote - can someone please expand on why one (I was not
> involved
> in the creation of this DB/schema definition) would choose to have the
> definition of the timestamp column as a
Thanks for the explanation Kevin!
Regards,
Ruan
From: pgsql-general-ow...@postgresql.org
on behalf of K. Brannen
Sent: 03 November 2017 14:35
To: pgsql-general@postgresql.org
Subject: [GENERAL]
Rhhh Lin wrote:
> *Also, as a sidenote - can someone ple
art the server, implement a vacuum
execution and see where I am at then.
Regards,
Ruan
From: Justin Pryzby
Sent: 03 November 2017 21:33
To: Rhhh Lin
Cc: Tom Lane; pgsql-general@postgresql.org
Subject: Re: [GENERAL] EXPLAIN command just hangs...
On Fri, Nov 03,
y repercussions...
Regards,
Ruan
From: Justin Pryzby
Sent: 02 November 2017 21:49
To: Rhhh Lin
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] EXPLAIN command just hangs...
On Thu, Nov 02, 2017 at 09:13:05PM +, Rhhh Lin wrote:
> Yes, it may be an issue with the index, but I&
ot;timestamp", but right now I cannot
check and verify because it just hangs...
Regard,
Ruan
From: Tom Lane
Sent: 02 November 2017 21:40
To: Rhhh Lin
Cc: Justin Pryzby; pgsql-general@postgresql.org
Subject: Re: [GENERAL] EXPLAIN command just hangs.
: Justin Pryzby
Sent: 02 November 2017 21:02
To: Rhhh Lin
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] EXPLAIN command just hangs...
On Thu, Nov 02, 2017 at 08:51:23PM +, Rhhh Lin wrote:
> However, this query will run for days without completing. I suspect it has to
> do w
Hi all,
version = Postgres 9.3.10
I have a table with approx. 5 million rows. It is defined something like the
below.
col: type:
timestamp bigint
measurement_id integer
value numeric(24,5)
minval numeric(24,5)
maxval numeric(24,5)
There are two BTree indexes in place on the PK ("timestamp", "me
ng called upon again for restartpoints/checkpoints.
That is, where is my absolute point (or file) of archival using something along
the lines of 'pg_current_xlog_location'.
Regards,
Ruan
From: Stephen Frost
Sent: 30 October 2017 16:41:11
Thanks very much for your reply Michael.
I note that it looks like pgbarman employs pg_receivexlog; I will check it out.
Regards,
Ruan
From: Michael Paquier
Sent: 22 October 2017 22:17:01
To: Rhhh Lin
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL
Hi,
Version 9.4...
Per the PG docs, to facilitate continuous WAL archiving and PITR recovery...
"To enable WAL archiving, set the wal_level configuration parameter to archive
(or hot_standby), archive_mode to on, and specify the shell command to use in
the archive_command configuration paramet
10 matches
Mail list logo
