> From: pgsql-bugs-ow...@postgresql.org
> [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of
> miroslav.s...@fordfrog.com
> Sent: Saturday, June 30, 2012 4:28 PM
> The following bug has been logged on the website:
> Bug reference: 6712
> Logged by: Miroslav Šulc
> Email address:
Ok, we are 99% sure as for what is the reason for this situation. Let's say
we have a 1 GB of free memory. Any process (especially postgres, as it is
dedicated server) wants to allocate little more. Kernel has to look through
cached memory to determine which cache pages can be dropped and allocated
On Sat, Jun 30, 2012 at 02:37:47PM -0400, Tom Lane wrote:
> > However, surprisingly, a simple pg_dump/restore also does not preserve
> > the public schema permissions either. :-(
>
> Right. My point is that there is a whole lot of stuff that initdb
> creates but does not mark "pinned" in pg_depe
Bruce Momjian writes:
> +
> + /*
> + * We unconditionally create the extension, so we must
> drop it if it
> + * exists. This could happen if the user deleted
> 'plpgsql' and then
> + * readded it, causing its oid to be greater
On Mon, Jul 02, 2012 at 01:01:51PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > +
> > + /*
> > +* We unconditionally create the extension, so we must
> > drop it if it
> > +* exists. This could happen if the user deleted
> > 'plpgsql' and then
I looked at the logs you sent. Strangely the command
*"D:\Program Files\PostgreSQL\9.1\bin\initdb.exe" --locale=C
--encoding=UTF-8 -A md5 -U postgres -d "D:\Program
Files\PostgreSQL\9.1\data"*
*
*
produces no output in the log. Can you try to manually execute this above
command and share the outpu
