On 12/26/2015 01:36 PM, Sébastien Boutté wrote:
> Honestly, not enough information to make a determination. So:
>
> 1) Is the order you show above the actual order you did the restores?
> No, i have made multiples tests but it's always the same order of nature.
>
> 2) Are the above timings from one run for each setup or multiple runs?
> Multiple runs.
>
> 3) Just to be clear, this is all on the same machine, correct? Yes
> Core i5 2500K
> 16G RAM
> SSD 256Go
>
>
> Is a problem with :
> User Space / Kernel Space ?
> Compilations options ?
> LD Library ?
> Missing something ?
>
>
> To see how each installation is set up you can:
>
> 1) Run the pg_config for each installation, so for instance, on a
> compiled version on my machine:
>
> /usr/local/pgsql/bin/pg_config
>
> i've attached config files for :
>
> Ubuntu Default : pgconfig.ubuntu & pg_controldata.ubuntu
> Compiled Version : pg_config.compiled & pg_controldata.compiled
>
>
> 2) Run each installations pg_controldata against the installation data
> directory:
>
> /usr/local/pgsql/bin/pg_controldata /usr/local/pgsql/data/
Hmm, the Ubuntu configuration sets a lot of *FLAGS. Unfortunately I am
not well versed enough to offer any guidance on whether they matter or
not. That will depend on someone more capable than I.
So, you are interested in only the Ubuntu and compiled versions of the
databases, not the EDB version, or am I missing some attachments?
Something else came to mind, when you ran the pg_restore command did you
run the one specific to each installation or whichever was first on the
PATH?
Lastly, are there any errors in the respective Postgres logs that might
shed light. I ask because the Ubuntu Postgres is compiled with a lot of
extras built in, '--with-python' '--with-pam' '--with-openssl', etc,
whereas the self compiled version is not. Just wondering if there are
objects in your backup that need those extras?
>
>
>
>
>
>
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
