-- Forwarded message --
From: Sam Stearns
Date: Tue, May 3, 2011 at 6:32 PM
Subject: Re: [ADMIN] Unable to Insert Row
To: Adarsh Sharma
Thanks, Adarsh.
I don't see any references to a repair command in the 8.3 doco.
On Tue, May 3, 2011 at 5:06 PM, Adarsh Sharma wrote:
> Try a
Respected Committers,
It may be a silly question, still out of curiosity I want to know, is there
any possible way to flush the Postgres Shared Memory without restarting the
cluster.
In Oracle, we can flush the SGA, can we get the same feature here..
Thanks in Advance.
Regards
Raghu Ram
Enterpr
On Tue, May 3, 2011 at 11:54 AM, raghu ram wrote:
> It may be a silly question, still out of curiosity I want to know, is there
> any possible way to flush the Postgres Shared Memory without restarting the
> cluster.
> In Oracle, we can flush the SGA, can we get the same feature here..
> Thanks i
On Tue, May 3, 2011 at 5:37 PM, Simon Riggs wrote:
> On Tue, May 3, 2011 at 11:54 AM, raghu ram
> wrote:
>
> > It may be a silly question, still out of curiosity I want to know, is
> there
> > any possible way to flush the Postgres Shared Memory without restarting
> the
> > cluster.
> > In Oracl
2001/3/19 Grant
> Hello, I have written a backup script that will vacuum, analyze and backup
> every postgresql database.
>
> (1) Modify logfile and backup_dir variables to suite your needs.
> (2) I have a trust relationship so I am never prompted for a password on
> connection.
> (3) Add an entr
On Tue, May 3, 2011 at 6:01 PM, Raghavendra <
raghavendra@enterprisedb.com> wrote:
>
> On Tue, May 3, 2011 at 5:37 PM, Simon Riggs wrote:
>
>> On Tue, May 3, 2011 at 11:54 AM, raghu ram
>> wrote:
>>
>> > It may be a silly question, still out of curiosity I want to know, is
>> there
>> > any
On Tue, May 3, 2011 at 8:30 AM, raghu ram wrote:
> On Tue, May 3, 2011 at 6:01 PM, Raghavendra
> wrote:
>>
>> On Tue, May 3, 2011 at 5:37 PM, Simon Riggs wrote:
>>>
>>> On Tue, May 3, 2011 at 11:54 AM, raghu ram
>>> wrote:
>>>
>>> > It may be a silly question, still out of curiosity I want to k
> On Tue, May 3, 2011 at 6:01 PM, Raghavendra <
> raghavendra@enterprisedb.com> wrote:
>
>>
>> On Tue, May 3, 2011 at 5:37 PM, Simon Riggs
>> wrote:
>>
>>> On Tue, May 3, 2011 at 11:54 AM, raghu ram
>>> wrote:
>>>
>>> > It may be a silly question, still out of curiosity I want to know, is
>>>
2011/5/3 Merlin Moncure :
> On Tue, May 3, 2011 at 8:30 AM, raghu ram wrote:
>> On Tue, May 3, 2011 at 6:01 PM, Raghavendra
>> wrote:
>>>
>>> On Tue, May 3, 2011 at 5:37 PM, Simon Riggs wrote:
On Tue, May 3, 2011 at 11:54 AM, raghu ram
wrote:
> It may be a silly questio
On Tue, May 3, 2011 at 8:55 AM, Cédric Villemain
wrote:
> 2011/5/3 Merlin Moncure :
>>
>> no it will not, or at least there is no guarantee it will be. the
>> only way to reset the buffers in that sense is to restart the database
>> (and even then they might not be read from disk, because they co
2011/5/3 Merlin Moncure :
> On Tue, May 3, 2011 at 8:55 AM, Cédric Villemain
> wrote:
>> 2011/5/3 Merlin Moncure :
>>>
>>> no it will not, or at least there is no guarantee it will be. the
>>> only way to reset the buffers in that sense is to restart the database
>>> (and even then they might not
On Tue, May 3, 2011 at 3:16 PM, Mark Johnson
wrote:
> The contents of this email may not be copied or forwarded in part or in
> whole without the express written consent of the author.
Pleased to meet you Mark.
If you post here, the above disclaimer is not effective. Right now
your words are be
Is there a particular one of Oracle's memory clearning features you want to use
in PostgreSQL? In Oracle you cannot flush the entire SGA without a restart, but
you can flush three parts of the SGA using three separate commands.
1. In Oracle you can flush the redo buffer by issuing a COMMIT or by
On Tue, May 3, 2011 at 2:30 PM, raghu ram wrote:
>>> The CHECKPOINT command will do this for you.
>>
>>
>
> According to PostgreSQL documentation, whenever you execute "CHECKPOINT" in
> the database,it will flush the modified data files presented in the Shared
> Buffers retuned to the Disk.
>
On Tue, May 03, 2011 at 08:48:19AM +0200, Guillaume Lelarge wrote:
> On 05/03/2011 05:52 AM, Tom Hartnett wrote:
> > can it be done?
> >
> > create index my_idx on my_table(col1) where col1='';
> >
> > ERROR: invalid input syntax for integer: ""
> >
> > Seems simple enough but I don't know what
Yes, understood and agreed. My mail server adds it automatically. I can
manually remove it prior to sending to the mail list.
-Mark
-Original Message-
From: Simon Riggs [mailto:si...@2ndquadrant.com]
Sent: Tuesday, May 3, 2011 10:33 AM
To: 'Mark Johnson'
Cc: 'pgsql-admin', 'pgsql-general'
I have a Postgres 8.3 system that is configured to run autovacuum. It
triggered a vacuum analyze on multiple tables and since this started, we are
getting large numbers of WAL files generated about every 15 minutes or so.
This same vacuum appears to continuing to run. Other database activity
Todd Gugler wrote:
> Should a vacuum analyze lead to large amounts of data being
> written to WAL files?
Yes, if it has to "freeze" the rows to prevent transaction
wraparound.
> We are seeing 10x the number WAL files that we would expect.
>
> Any ideas on the best approach to diagnose what
Does anyone else have any ideas on how to solve this problem besides
this mysterious repair command?
On Tue, May 3, 2011 at 6:33 PM, Sam Stearns wrote:
> -- Forwarded message --
> From: Sam Stearns
> Date: Tue, May 3, 2011 at 6:32 PM
> Subject: Re: [ADMIN] Unable to Insert Row
>
On 1st May, I saw this message in my postgres log:
May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02 SGT
ERROR: could not access status of transaction 1573786613
May 2 06:52:02 db10 postgres[3590]: [29829-2] 2011-05-02 06:52:02 SGT
DETAIL: Could not open file "pg_clog/05DC":
20 matches
Mail list logo
