Hello,
I am new to this list and hope I have chosen the appropriate group to
ask this question.
We are running version 8.2.6 of postgres and I am trying to run a full
vacuum on a single table in our database. I started the vacuum about 24
hours ago and it is still running. Within 2-3 hrs o
Hello,
I am new to this list and hope I have chosen the appropriate group to
ask this question.
We are running version 8.2.6 of postgres and I am trying to run a full
vacuum on a single table in our database. I started the vacuum about 24
hours ago and it is still running. Within 2-3 hrs o
Simon - thanks for the response. I checked all the processes and
nothing appears to be holding it up. Any other advice?
Simon Riggs said the following on 7/15/2011 12:21 PM:
On Fri, Jul 15, 2011 at 5:10 PM, David Ondrejik wrote:
Since then, the process has continued to run (for about 20
takes on the
vacuum process?
Thanks,
Dave
Tom Lane said the following on 7/15/2011 1:12 PM:
Simon Riggs writes:
On Fri, Jul 15, 2011 at 5:10 PM, David Ondrejik wrote:
Since then, the process has continued to run (for about 20 hrs) without any
additional information being returned.
Probably
Thanks to everyone for their response and help. I still have some
more questions that hopefully someone can help me with as I have not yet
been able to solve my vacuumdb problem.
The posting of data to the table in question is extremely
slow...yesterday I saw that it took over 6 min to post
I think I see a (my) fatal flaw that will cause the cluster to fail.
From the info I received from previous posts, I am going to change
my game plan. If anyone has thoughts as to different process or
can confirm that I am on the right track, I would appreciate your
input.
1. I am going to ru
In Linux you can setup and use the "sudo" option. For those whom you don't
wish to have root access, simply make them sudousers, then change the root
password. This will force those users to simply type "sudo" (w/o quotes) at
the beginning of each command they want to run (i.e. sudo psql db_name
"i
That unadvertised command...if issued...would also
be logged and lists the userid of the person who used the command. So there
is some trail to track back to the original user.
Dave
On Wed, Mar 14, 2012 at 11:14 AM, Scott Ribe wrote:
> On Mar 14, 2012, at 9:01 AM, David Ondrejik wrote:
>
>
on't give it to them.
Dave
On Wed, Mar 14, 2012 at 11:46 AM, Scott Ribe wrote:
> On Mar 14, 2012, at 9:28 AM, David Ondrejik wrote:
>
> > So there is some trail to track back to the original user.
>
> Yes, but once he has root shell, the trail ends there, and impersonation
&g
