On Mon, Mar 4, 2013 at 8:31 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Mon, Mar 4, 2013 at 9:18 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>>> And yes, the cache purging appears to be broken *as well*. The reason
>>> for that one seems to be that I forgot to update the port number for
>>> cache invalidation when I moved it into production. Oops. That should
>>> start working on the next commit that someone does.
>>
>> Seemed to work when I pushed the tm2timestamp fix just now --- the
>> front page updated almost immediately after the next top-of-minute.
>> Thanks.
>
> Great, thanks for confirming.
>
> Now I just need to get Dave to stop unintentionally purgning the cache
> every 5 minutes...
Meh. It's on my list.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
