To clarify on the rules...I was using rules for the tables that are
the entry point for the insertion into the database.
On Sat, Jun 5, 2010 at 7:19 AM, Anj Adu wrote:
> We run a similar system with very large volumes
>
> I had similar queue build ups (not related to pg_stat_timeouts though)
>
>
We run a similar system with very large volumes
I had similar queue build ups (not related to pg_stat_timeouts though)
I was using Rules for my partition management instead of triggers.
Changing from rules to triggers fixed the problem. (rules were extremely slow)
Hope this helps you.
On Wed,
"Gnanakumar" wrote:
> I couldn't able to get this particular step clearly: "One trick
> would be to temporarily change your archive_command to 'true',
> delete all files from your archive, and then change the command
> back ". Can you please clarify and explain on this?
Based on other statemen
On Fri, Jun 4, 2010 at 10:24 PM, mnavahan wrote:
>
>
>
> Scott Marlowe-2 wrote:
>>
>> On Wed, May 19, 2010 at 10:38 AM, mnavahan wrote:
>>>
>I think so. Look up "SECURITY DEFINER"
>>>
>>> seems goods i need try to it ...
>>>
>>>
>Not that I know of. You're talking connect / disconn
On Fri, Jun 4, 2010 at 10:34 PM, mnavahan wrote:
>
> Hi
>
> (windows :: pg8.4.4 ::pgadmin 1.10)
>
> in old pc i had 3 different tablespace and each tablespace had one database
>
> Now i dont have old pc ! but i have copy of each tablespace .
>
> now in new pc i have installed the same versio
Hi Kevin,
> It is generally unsafe to delete any WAL files from pg_xlog. If
> they are there because your archive command has been failing, you
> need to turn off archiving or (probably more convenient) allow the
> archive script to return success until things clear. One trick
> would be to temp
On Thu, Jun 3, 2010 at 2:14 AM, Kevin Grittner
wrote:
> Manohar Bhattarai wrote:
>
> > FATAL: password authentication failed for user "postgres"
>
> > But the password is the same that i use to login postgres user in
> > the terminal.
> > What could be the problem?
>
> When you say "postgres user
Hi Florian,
Thanks for your valuable suggestion and a detailed step on common way to use
PITR. Things are very clear now except that I've some other question in
connection to this.
> The correct way to clean out pg_xlog therefore is to either disable WAL
archiving, or to make sure your archive_c
