On 8/16/19 4:45 PM, Susan Hurst wrote:
> We're using the 9.5.14 in the sandbox to extract data and objects from
> the pgdump that was created in the 9.5.0 version. Hope I answered
> your question correctly. If not, let me know and I'll try again.
>
> Our biggest concern is that there may be other silent issues that we
> have not yet discovered. Thanks for the info you just provided,
> Adrian. We'll read up on the path settings to see if we can find an
> answer there.
>
> Sue
>
> ---
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Susan E Hurst
> Principal Consultant
> Brookhurst Data LLC
> Email: susan.hurst@brookhurstdata.com
> Mobile: 314-486-3261
>
> On 2019-08-16 17:29, Adrian Klaver wrote:
>> On 8/16/19 3:18 PM, Susan Hurst wrote:
>>> Production version:
>>> PostgreSQL 9.5.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7
>>> 20120313 (Red Hat 4.4.7-16), 64-bit
>>>
>>> Sandbox version:
>>> "PostgreSQL 9.5.14, compiled by Visual C++ build 1800, 64-bit"
>>>
>>
>> I going to say it has something to do with this:
>>
>> https://www.postgresql.org/docs/9.5/release-9-5-12.html
>>
>> "Avoid use of insecure search_path settings in pg_dump and other
>> client programs (Noah Misch, Tom Lane)"
>>
>> Are you using the 9.5.0 or 9.5.14 version of pg_dump to dump from the
>> production server?
>
>
In case Adrian has gone hojme I'll chime in: I believe his question is
asking which installation/version of pgdump is used in the command you
provided earlier. If it's run from the production machine it would
likely be the 9.5.0 version, but could also be the 9.5.14 version. All
depending on the PATH and host and postgres installation.
