On 20.1.2012 19:47, Matt Dew wrote:
> On 01/13/2012 02:49 PM, Tomas Vondra wrote:
>> On 13.1.2012 22:20, Tom Lane wrote:
>>> Matt Dew writes:
An interesting sidenote we realized. the nice system shutdown script
/etc/init.d/postgres doesn't actually wait for the db to be down, it
ju
On 01/13/2012 02:49 PM, Tomas Vondra wrote:
On 13.1.2012 22:20, Tom Lane wrote:
Matt Dew writes:
An interesting sidenote we realized. the nice system shutdown script
/etc/init.d/postgres doesn't actually wait for the db to be down, it
just waits for pg_ctl to return.
By default, "pg_ctl sto
On 13.1.2012 22:20, Tom Lane wrote:
> Matt Dew writes:
>> An interesting sidenote we realized. the nice system shutdown script
>> /etc/init.d/postgres doesn't actually wait for the db to be down, it
>> just waits for pg_ctl to return.
>
> By default, "pg_ctl stop" does wait for the server to s
Matt Dew writes:
> An interesting sidenote we realized. the nice system shutdown script
> /etc/init.d/postgres doesn't actually wait for the db to be down, it
> just waits for pg_ctl to return.
By default, "pg_ctl stop" does wait for the server to shut down ...
regards
On 01/12/2012 01:21 PM, Tom Lane wrote:
Matt Dew writes:
On 01/11/2012 04:29 PM, Tom Lane wrote:
What exactly is your definition of a "clean shutdown"?
Is a reboot command considered a clean shutdown? It's a redhat box
which called /etc/init.d/postgresql stop, which does: pg_ctl stop -D
'$P
On 01/12/2012 01:21 PM, Tom Lane wrote:
Matt Dew writes:
On 01/11/2012 04:29 PM, Tom Lane wrote:
What exactly is your definition of a "clean shutdown"?
Is a reboot command considered a clean shutdown? It's a redhat box
which called /etc/init.d/postgresql stop, which does: pg_ctl stop -D
'$P
Matt Dew writes:
> On 01/11/2012 04:29 PM, Tom Lane wrote:
>> What exactly is your definition of a "clean shutdown"?
> Is a reboot command considered a clean shutdown? It's a redhat box
> which called /etc/init.d/postgresql stop, which does: pg_ctl stop -D
> '$PGDATA' -s -m fast
Well, a fast
On 01/11/2012 04:29 PM, Tom Lane wrote:
Matt Dew writes:
I have a database that was shut down, cleanly, during an 'reindex
table' command. When the database came back up, queries against that
table started doing sequential scans instead of using the indexes as
they had been up until that
Matt Dew writes:
> I have a database that was shut down, cleanly, during an 'reindex
> table' command. When the database came back up, queries against that
> table started doing sequential scans instead of using the indexes as
> they had been up until that point.
What exactly is your def
On 01/11/2012 11:07 AM, Scott Marlowe wrote:
On Wed, Jan 11, 2012 at 10:42 AM, Matt Dew wrote:
Hello all,
I have a database that was shut down, cleanly, during an 'reindex table'
command. When the database came back up, queries against that table
started doing sequential scans instead of
On Wed, Jan 11, 2012 at 10:42 AM, Matt Dew wrote:
> Hello all,
> I have a database that was shut down, cleanly, during an 'reindex table'
> command. When the database came back up, queries against that table
> started doing sequential scans instead of using the indexes as they had been
> up un
Hello all,
I have a database that was shut down, cleanly, during an 'reindex
table' command. When the database came back up, queries against that
table started doing sequential scans instead of using the indexes as
they had been up until that point.
We tried:
1) vacuuming the table (vacu
12 matches
Mail list logo
