same localhost?
Is there a relatively easy way to do this?
--o--o--o--o--o--o--o--o--o--o--o--o--
Jim Longwill
jlongw...@psmfc.org
--o--o--o--o--o--o--o--o--o--o--o--o--
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
Ok,
Thanks! I think the ALTER DATABASE.. commands will work well for what
I'm doing now. I want to experiment with one database (doing manual
vacuuming, etc.) while leaving the other databases undisturbed.
Regards,
--Jim Longwill
On 10/29/2015 12:36 PM, John R Pierce wrote:
On 10/29
27;postgres' database. I tried
'ddev2' also, etc. The above error is *always* the response.
I'm certain that there are no other user sessions in this database.
So.. what are the magic words? Thanks again!
--
--o--o--o--o--o--o--o--o--o--o--o--o--
Jim Longwill
jlongw...@psmf
n't turn it off per database, it may not be worth the trouble to
configure this. I plan to experiment with other parameters as well, but
this is not critical at this time.
Thanks again.
--Jim Longwill :^)
On 10/29/2015 01:52 PM, Adrian Klaver wrote:
On 10/29/2015 01:35 PM, Jim Longwill
s cause by autovacuum on that database.
Moreso, if you think the problem is autovacuum (in this case) it's
probably something else.
If I can toot my own horn, you might want to watch the recording of
http://www.pgcon.org/2015/schedule/events/829.en.html.
--
--o--o--o--o--o--o--o--o--o--o--o--
ways get this result. So, do
I need to do a new 'initdb..' operation on machine M2 + restore from M1
backups? Or is there another way to fix this?
--o--o--o--o--o--o--o--o--o--o--o--o--
Jim Longwill
PSMFC Regional Mark Processing Center
jlongw...@psmfc.org
--o--o--o--o--o--o--o--o
al (initdb.. & pg_restore
from backup files) on the new machine in order to get a roughly
equivalent installation going. One early goal I have is to get
archiving setup & working at beyond the minimal level.
Jim Longwill
On 05/31/2016 11:50 AM, Scott Mead wrote:
On Tue, May
.
So, thanks Jeff for mentioning pg_xlog. Thanks to others as well for
your input.
--Jim Longwill
On 06/01/2016 08:44 AM, Jeff Janes wrote:
On Tue, May 31, 2016 at 10:13 AM, Jim Longwill wrote:
I am trying to setup a 2nd, identical, db server (M2) for development and
I've run i
get database
(rdev1), but it might be
an issue if we tried to do more things with PL/pgSQL. Is it cancelling
the autovacuum task on a
long term basis? This same result also occurs when creating using
'template1' db.
Any thoughts on this?
--
--o--o--o--o--o--o--o--o--o--o--o--o--
Jim Lo
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. is just a
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 default. \dd only shows
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 | Description
12 matches
Mail list logo
