On 06/22/2017 10:05 AM, Jim Longwill wrote:
Ok. Thank you for the input. I do see the 'Description' of plpgsql
there. So, if I can determine the source table(s) of this information
perhaps I could delete that particular value.I tried the following
as per documentation:
COMMENT
On 06/21/2017 05:30 PM, Adrian Klaver wrote:
On 06/21/2017 05:06 PM, Jim Longwill wrote:
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill
wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object |
On 06/21/2017 05:06 PM, Jim Longwill wrote:
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill
wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object | Description
+--++-
(0
On 06/21/2017 01:21 PM, David G. Johnston wrote:
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
rdev1=# \dd
Object descriptions
Schema | Name | Object | Description
+--++-
(0 rows)
Nothing user created has comments by
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
> rdev1=# \dd
> Object descriptions
> Schema | Name | Object | Description
> +--++-
> (0 rows)
Nothing user created has comments by default. \dd only shows a very
limited subset
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill wrote:
> Given this, I wonder how we can avoid this 'error' situation .. short of
> giving SUPERUSER
> role to rradmin? I tried just removing the '-v' flag from pg_restore,
> but the error is
> still put in the log file
On 06/21/2017 11:05 AM, Jerry Sievers wrote:
Jim Longwill writes:
We have a (Linux CentOS) server, and one Postgres installation (v9.5).
We have long been experiencing an error when doing a 'pg_restore'
database build from a tar
file. Our procedure is as follows (err.
Jim Longwill writes:
> We have a (Linux CentOS) server, and one Postgres installation (v9.5).
>
> We have long been experiencing an error when doing a 'pg_restore'
> database build from a tar
> file. Our procedure is as follows (err. is just after start of
> restoring our