On 19.10.2010 22:40, Jeff Davis wrote:
On Tue, 2010-10-19 at 09:51 -0700, Jeff Davis wrote:
On Tue, 2010-10-19 at 12:26 +0300, Heikki Linnakangas wrote:
Excluding pg_xlog is just a recommendation at the moment, though, so we
would need a big warning in the docs. And some way to enforce that
The following bug has been logged online:
Bug reference: 5722
Logged by: Jochen Erwied
Email address: joc...@pgsql.erwied.eu
PostgreSQL version: 9.0.1
Operating system: x86_64-pc-linux-gnu
Description:vacuum full does not update last_vacuum statistics
Details:
Jochen Erwied joc...@pgsql.erwied.eu writes:
VACUUM FULL does not update statistics so display of pg_stat_user_tables is
wrong. A normal VACUUM updates the relevant information.
Hmm. This is a definitional issue: what do we really mean by last_vacuum?
I'm inclined to think that the current
Jochen Erwied joc...@pgsql.erwied.eu writes:
Monday, October 25, 2010, 4:12:39 PM you wrote:
Jochen Erwied joc...@pgsql.erwied.eu writes:
VACUUM FULL does not update statistics so display of pg_stat_user_tables is
wrong. A normal VACUUM updates the relevant information.
Hmm. This is a
Monday, October 25, 2010, 4:12:39 PM you wrote:
Jochen Erwied joc...@pgsql.erwied.eu writes:
VACUUM FULL does not update statistics so display of pg_stat_user_tables is
wrong. A normal VACUUM updates the relevant information.
Hmm. This is a definitional issue: what do we really mean by
On Mon, 2010-10-25 at 16:48 +0200, Jochen Erwied wrote:
Well, when reading
http://www.postgresql.org/docs/current/static/monitoring-stats.html
then last_vacuum contains the last time of a user-initiated vacuum.
There's no distinction made what kind of vacuum was made. And IMHO
even if
On 25 October 2010 07:36, Tom Lane t...@sss.pgh.pa.us wrote:
Brendan Jurd dire...@gmail.com writes:
I have encountered a reproducible segfault in Postgres ...
Looks like the invalItems list has been clobbered:
(gdb) p *root-glob-invalItems
$6 = {type = 2139062143, length = 2139062143, head
On Mon, 2010-10-25 at 14:44 +0300, Heikki Linnakangas wrote:
It seems we should use ReadRecord instead of the lower-level
XLogPageRead function. One difference is that ReadRecord performs a
bunch of sanity checks on the record, while XLogPageRead just reads the
raw page. Extra sanity
Brendan Jurd dire...@gmail.com writes:
On 25 October 2010 07:36, Tom Lane t...@sss.pgh.pa.us wrote:
I'm guessing it was modified in the temporary memory context and not
properly copied out to the parent context when we finished inlining
the function.
Thanks for the hint; I found that the
Brendan Jurd dire...@gmail.com writes:
This whole business of passing around global pointers while switching
memory contexts seems like an optimal breeding-ground for bugs.
Yeah. If it were to get significantly more complicated than this,
the best solution IMO would be to give up on trying to
On Mon, Oct 25, 2010 at 8:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Perhaps. The new implementation of VACUUM FULL is really more like a
CLUSTER, or one of the rewriting variants of ALTER TABLE. Should all
of those operations result in an update of last_vacuum? From an
implementation
On Mon, 2010-10-25 at 10:46 -0700, Greg Stark wrote:
Perhaps we should have another field last_table_rewrite or something?
Seems like overkill. And we don't want to make it sound like table
rewrites are expected to be a normal part of maintenance (perhaps that's
just a terminology issue,
Hi,
I tried to install postgresql-8.4 from sources on a custom Ubuntu 10.10 liveCD.
I get an error during the installation process:
[...]
Configuring postgresql.conf to use port 5432...
update-alternatives: using /usr/share/postgresql/8.4/man/man1/postmaster.1.gz
to
provide
On 10/25/10 7:50 AM, Marcus wrote:
The following bug has been logged online:
Bug reference: 5723
Logged by: Marcus
Email address: marcusboos...@mailinator.com
PostgreSQL version: 9.0.1
Operating system: Ubuntu 10.10
Description:Can not start postgres after install
On 10/26/2010 02:44 AM, VMaury wrote:
2010-10-25 08:45:56 UTC PANIC: could not open file
pg_xlog/0001 (log file 0, segment 0): Invalid
argument
This bug has been reported by someone else (in spanish):
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/658857
On 10/25/2010 10:50 PM, Marcus wrote:
The following bug has been logged online:
Bug reference: 5723
Logged by: Marcus
Email address: marcusboos...@mailinator.com
PostgreSQL version: 9.0.1
Operating system: Ubuntu 10.10
Description:Can not start postgres after
On Mon, Oct 25, 2010 at 5:43 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from VMaury's message of lun oct 25 15:44:01 -0300 2010:
This bug has been reported by someone else (in spanish):
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/658857
However, this
The following bug has been logged online:
Bug reference: 5726
Logged by: Marcus
Email address: marcusboos...@mailinator.com
PostgreSQL version: 9.0.1
Operating system: Ubuntu 10.10
Description:Re: BUG #5723: Can not start postgres after install
Details:
On
18 matches
Mail list logo
