Search Postgresql Archives

Re: pg_dump and search_path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: pg_dump and search_path
From: Ryan Lambert <ryan@xxxxxxxxxxxxxxxxx>
Date: Wed, 10 Jul 2019 14:19:09 -0600
Cc: "Igal @ Lucee.org" <igal@xxxxxxxxx>, pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <9660facc-0bdd-d7fd-8316-02a45a509dd5@aklaver.com>
References: <1f5111a5-e49e-e44a-67df-b367e5d31fdf@lucee.org> <94e28e8c-e5cf-f0b5-a148-43452446d9ec@aklaver.com> <fbe59d2f-79ce-1b8e-c96a-ef665f18f747@lucee.org> <126613fd-e0a9-c79f-a400-028107214439@aklaver.com> <09136454-d905-7cce-d0cd-38158482e269@lucee.org> <9660facc-0bdd-d7fd-8316-02a45a509dd5@aklaver.com>

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: pg_dump and search_path
  - From: Adrian Klaver

References:
- pg_dump and search_path
  - From: Igal @ Lucee.org
- Re: pg_dump and search_path
  - From: Adrian Klaver
- Re: pg_dump and search_path
  - From: Igal @ Lucee.org
- Re: pg_dump and search_path
  - From: Adrian Klaver
- Re: pg_dump and search_path
  - From: Igal @ Lucee.org
- Re: pg_dump and search_path
  - From: Adrian Klaver

Prev by Date: Re: DRY up GUI wiki pages
Next by Date: Re: pg_dump and search_path
Previous by thread: Re: pg_dump and search_path
Next by thread: Re: pg_dump and search_path
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux