On Fri, Nov 9, 2012 at 2:44 AM, Axel Rau wrote:
>
> Am 08.11.2012 um 18:16 schrieb Fujii Masao:
>
>> On Fri, Nov 9, 2012 at 1:13 AM, Axel Rau wrote:
>>> Hi dbas,
>>>
>>> I changed hot_standby to "on" on the standby and learned on restart:
>>> "hot standby is not possible because wal_level was not
Am 08.11.2012 um 18:16 schrieb Fujii Masao:
> On Fri, Nov 9, 2012 at 1:13 AM, Axel Rau wrote:
>> Hi dbas,
>>
>> I changed hot_standby to "on" on the standby and learned on restart:
>> "hot standby is not possible because wal_level was not set to
>> ""hot_standby"" on the master server"
>> Afte
On Fri, Nov 9, 2012 at 1:13 AM, Axel Rau wrote:
> Hi dbas,
>
> I changed hot_standby to "on" on the standby and learned on restart:
> "hot standby is not possible because wal_level was not set to ""hot_standby""
> on the master server"
> After restarting the master with "wal_level = hot_standby",
Wow thanks for the code!! I'll test it out and let you know if I get any
unexpected results.
On Wed, Nov 7, 2012 at 8:39 PM, Craig Ringer wrote:
> On 11/08/2012 04:42 AM, Mike Broers wrote:
>
> I would like to bump all sequences in a schema by a specified increment.
> Is there a stored proc o
Hi dbas,
I changed hot_standby to "on" on the standby and learned on restart:
"hot standby is not possible because wal_level was not set to ""hot_standby""
on the master server"
After restarting the master with "wal_level = hot_standby",
I'm still getting the same error message on the standby.
Th
Got it. Thanks.
于2012年11月8日 23:21:33,Albe Laurenz写到:
Rural Hunter wrote:
I'm on 9.1.3. I set auto vacuum off for some tables. I noticed one
thing: when I run manual analyze on parent table, It seems the
children
tables are also analyzed. Here is the analyze log:
INFO: analyzing "public.tabl
Rural Hunter wrote:
> I'm on 9.1.3. I set auto vacuum off for some tables. I noticed one
> thing: when I run manual analyze on parent table, It seems the
children
> tables are also analyzed. Here is the analyze log:
>
> INFO: analyzing "public.table_parent"
> INFO: "table_parent": scanned 0 of 0
Hi,
I'm on 9.1.3. I set auto vacuum off for some tables. I noticed one
thing: when I run manual analyze on parent table, It seems the children
tables are also analyzed. Here is the analyze log:
INFO: analyzing "public.table_parent"
INFO: "table_parent": scanned 0 of 0 pages, containing 0 li
Hi,
> So that an auto-ANALYZE should run each 2.5-3 hours.
>
> If it does not proceed, check that you do not have some process still doing
> manual maintenance or DDL on those tables, they might
> lock the table and kill autovacuum
>
> (check the pg_stat_activity, and set log_autovacuum_min_du
