On Thu, Sep 29, 2016 at 3:20 PM, Thomas Munro wrote:
> On Fri, Sep 30, 2016 at 8:17 AM, Kevin Grittner wrote:
> > On Thu, Sep 29, 2016 at 2:06 PM, Melvin Davidson
> wrote:
> >
> >> I am using PostgreSQL 9.4.0 (Yes, I know
On Fri, Sep 30, 2016 at 8:17 AM, Kevin Grittner wrote:
> On Thu, Sep 29, 2016 at 2:06 PM, Melvin Davidson wrote:
>
>> I am using PostgreSQL 9.4.0 (Yes, I know 9.4.9 is most recent but
>> it's out of my control)
>
> As long as the decision-maker is aware
Hi Melvin:
On 09/29/2016 12:06 PM, Melvin Davidson wrote:
I list the creation time for a WAL file and it shows:
/home/mdavidson/dba$ ls -l --time=ctime
/d-log/pg_xlog/0001000D00C9
-rw--- 1 postgres postgres 16777216 Sep 29 07:14
/d-log/pg_xlog/0001000D00C9
ctime
On Thu, Sep 29, 2016 at 2:06 PM, Melvin Davidson wrote:
> I am using PostgreSQL 9.4.0 (Yes, I know 9.4.9 is most recent but
> it's out of my control)
As long as the decision-maker is aware that 9.4.0 has known bugs
(fixed in later minor releases) that can render the
At 14:34 +0300 on 12/7/98, Andy wrote:
We use Prostgres 6.3.2 for our production system, but the Postgres
tables is growing when the data updated (time travel?). Could any one
help me to stop this time travel problem, since it make our system slow,
and data corrputed frequently, our table
We use Prostgres 6.3.2 for our production system, but the Postgres
tables is growing when the data updated (time travel?). Could any one
help me to stop this time travel problem, since it make our system slow,
and data corrputed frequently, our table size is about 150 MB (after
vacuum), and