Also adding the pgsql-admin alias.
Regards...
On Mon, May 20, 2013 at 3:57 PM, Kasia Tuszynska wrote:
> Hi Everybody,
>
> Has anyone ran into issues running pg_restore?
>
> It seems that between 8.3.8 and 9.0.5, 9.1.3 the behavior of pg_restore
> has changed.
>
> ** **
>
> Previously I was able to have several data owners with
Hi Everybody,
Has anyone ran into issues running pg_restore?
It seems that between 8.3.8 and 9.0.5, 9.1.3 the behavior of pg_restore has
changed.
Previously I was able to have several data owners with their own schemas and
running a pg_restore as one superuser was able to restore the objects in
Hi again,
We've got a production cluster running Postgres 9.2.3(-1.30.amzn1 using the
exact Amazon package version).
I'd like to inspect the buffer_cache usage on this machine but can't get
the exact -contrib version from the Amazon repos.
I've got a different cluster running 9.2.4 with the cont
On Mon, May 20, 2013 at 3:11 PM, Tom Lane wrote:
> Armand du Plessis writes:
> > The autovacuum completed (after many hours) however it didn't seem to
> have
> > frozen any old pages as it just kicks off again right away with the same
> > reason (VACUUM ANALYZE public.messages (to prevent wrapar
Armand du Plessis writes:
> The autovacuum completed (after many hours) however it didn't seem to have
> frozen any old pages as it just kicks off again right away with the same
> reason (VACUUM ANALYZE public.messages (to prevent wraparound))
I suspect it's unable to move the table's min XID for
On Sun, May 19, 2013 at 6:12 PM, Armand du Plessis wrote:
> On Sun, May 19, 2013 at 6:08 PM, Simon Riggs wrote:
>
>> On 19 May 2013 13:54, Armand du Plessis wrote:
>>
>> > We started seeing 1000s of messages like the ones below in our logs
>> starting
>> > last night. There's been no changes but
