Thank you, all, for your help. It appears that everything is in
schema "public". I found a number of functions that have very similar
names to the ones in his tables so I think he probably dropped these
after he created the tables.
Carol
On Feb 6, 2009, at 2:42 PM, Plugge, Joe R. wrote:
Does your user have their own SCHEMA, if so you will have to :
set search_path to SCHEMA_NAME
-Original Message-
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Joshua D. Drake
Sent: Friday, February 06, 2009 1:36 PM
To: Carol Walter
Cc: pgsql
On Fri, 2009-02-06 at 14:30 -0500, Carol Walter wrote:
> Hello,
>
> Should all functions be visible when I issue the command
> citesrch=# select * from pg_proc;
> including those that are user defined?
> My user has several functions in his database that I don't see there.
> I don't know if I'm
Hello,
Should all functions be visible when I issue the command
citesrch=# select * from pg_proc;
including those that are user defined?
My user has several functions in his database that I don't see there.
I don't know if I'm looking in the wrong place or he dropped them
after the table was
On Fri, 2009-02-06 at 13:29 -0500, Mark Steben wrote:
> Thanks for quick response.
>
> I should have added that the 'recovery' site is really no more than a
> Second copy where reporting and ETL work is to be done - so we need
> The database to be available at least 6 -8 hours during the day.
> I
Thanks for quick response.
I should have added that the 'recovery' site is really no more than a
Second copy where reporting and ETL work is to be done - so we need
The database to be available at least 6 -8 hours during the day.
I've tried to wrestle with PG_STANDBY to allow daily availability
A
>>> "Mark Steben" wrote:
> currently creating about 2GB of logs every hour. Is there a config
> parameter to reduce the amount that Xlog takes up?
We pipe ours through gzip as part of our archive script. There was a
"gotcha", though -- an xlog is reused without clearing it first for
performan
On Fri, 2009-02-06 at 12:52 -0500, Mark Steben wrote:
> Hello listers,
>
> I'm designing a PITR backup / recovery scenario where I'm log-shipping to
> another location and recovering using a tar backup and log roll forward.
> The plan is to save a week's worth of logs and restore nightly using the
Hello listers,
I'm designing a PITR backup / recovery scenario where I'm log-shipping to
another location and recovering using a tar backup and log roll forward.
The plan is to save a week's worth of logs and restore nightly using the
accumulated logs to that point. A daily full backup is too
exp
Yes, it seems like I can do anything to this database except run
pg_dump against it. When this first happened, I copied all the data
out of the tables. I've just finished manually rebuilding the tables
in schema and copying the data into most of the tables in a test
database. I was able
10 matches
Mail list logo
