directory')||'/base' when
> 'pg_global' then (select setting from pg_settings where name =
> 'data_directory')||'/global' else spclocation end from pg_tablespace;
>
>
>
>
> ---
> Regards,
> Raghavendra
> EnterpriseDB
I have not defined my default tablespace:
show default_tablespace ;
default_tablespace
However, I have tables with null tablespaces values in pg_tables:
pg_dw=# select * from pg_tables where tablename = 'source_prev';
schemaname | tablename | tableowner | tab
I'm testing out various pg_dump scenarios using the -n switch and I have
a few questions:
- When using the -n switch, is the whole schema locked from all non-read
DML/DDL operations?
- If the whole schema is locked, once each table is dumped, is it then
released for non-read DML/DDL operations?
BINGO!
Thanks everyone. That did the trick!
On Thu, 2011-11-03 at 12:56 -0700, Ioana Danes wrote:
>
> >
> > pg_dump newdb > /DUMPDIR/newdb.dmp -n dev -T corgi -w -v -F c 2>
> > /DUMPDIR/newdb.log
> >
>
> Try: -T dev.corgi instead of -T corgi
>
>
--
Sent via pgsql-general mailing list
I'm using 9.0.3. I've tried several permutations of this script and
still I get a dump of the entire schema. The corgi table is still
included when I need it excluded.
On Thu, 2011-11-03 at 12:02 -0700, Adrian Klaver wrote:
> On Thursday, November 03, 2011 8:16:42 am Tony Cap
When I issue:
pg_dump newdb > /DUMPDIR/newdb.dmp -n dev -T corgi -w -v -F c 2>
/DUMPDIR/newdb.log
I get a dump of the entire dev schema. My goal is to dump the dev
schema minus the corgi table. How can I adjust my script to perform
this function?
Thanks.
--
Sent via pgsql-general mailing l
I'm running pgloader 2.3.2 and Postgres 9. Is there an upgraded version
of pgloader on the PgFoundry site?
On Mon, 2011-08-15 at 20:34 +0200, Dimitri Fontaine wrote:
> Tony Capobianco writes:
> > Has anyone experienced the behavior of pgloader hanging when the .conf
> > f
Has anyone experienced the behavior of pgloader hanging when the .conf
file has an incorrect filename?
When I execute with the correct filename, everything works just fine.
However, when I use an incorrect filename, I get the below:
PG_DB> pgloader -c hangs.pgload.conf -v
pgloader INFO Log
