Re: pg_dump and search_path

2019-07-10 Thread Ryan Lambert
I had a similar problem and was able to being the command with the
search_path to work around it.  I did this on Linux and it looks like you
are on Windows but I maybe you can do something similar that will work?

PGOPTIONS='-c search_path=staging, transient, pg_catalog'


*Ryan Lambert*
RustProof Labs


>


Re: pg_dump and search_path

2019-07-10 Thread Ryan Lambert
My exact situation was a deployment via sqitch,  It appears that uses psql
under the hood based on the error message I get.

Running just "sqitch deploy" I  get an error due to a non-fully qualified
name and a missing search path (my mistakes).  The error I get:

 + 004 .. psql:deploy/004.sql:72: ERROR:  relation "vobservations" does not
exist
LINE 11:FROM vobservations
 ^
not ok
"psql" unexpectedly returned exit value 3

Reverting all changes


Running the following works for me in this case and allows it to find the
view in the proper schema.

PGOPTIONS='-c search_path=piws,public' sqitch deploy

Ryan


Re: migrating from Oracle to PostgreSQL 11

2019-07-11 Thread Ryan Lambert
On Thu, Jul 11, 2019 at 1:28 AM Hitesh Chadda 
wrote:

> Hello,
> The target is PostgreSQL 10.1. I would like to know possible approach that
> can be followed for doing the migration.
>
> Regards
> H.kumar
>
>
10.9 is the current release in Pg10 and contains multiple security fixes
over 10.1. There is no good reason to start a new project on an outdated
minor release with known security issues.
https://why-upgrade.depesz.com/show?from=10.1&to=10.9&keywords=

As Gavin asked, why not start on Pg11 with 11.4 being the current release?

Ryan Lambert