o, but those are the ones reported so far). I have not
> been able to reproduce the failures in 8.0 but I think it may have
the
> same issue in a weaker form. We need a quick re-release I'm afraid.
Should the existing source and binaries be pulled in the meantime?
--
Thomas F
ms like it would make
sense to update the docs for 8.1...
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
-
On Aug 29, 2005, at 10:37 PM, Tom Lane wrote:
"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
After restarting, I have:
# sysctl -a | grep shm
kern.sysv.shmmax: 134217728
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024
, I have:
# sysctl -a | grep shm
kern.sysv.shmmax: 134217728
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024
Of course, this still doesn't seem to be enough to let postgres play
nicely with the iSight...
--
Thomas F. O'Connell
Co-Founder, Information
UFS was the filesystem on the Solaris 9 box.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
On Aug 11, 2005, at 4:
l see what I can do.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
On Aug 8, 2005, at 4:44 PM, Bruce Momjian wrote:
Great! Is background writer clogging worthy? That's the one that put
postgres in a nearly unusable state after this bug was tripped.
Thanks!
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 3
On Jul 21, 2005, at 1:22 PM, Bruce Momjian wrote:
Thomas F. O'Connell wrote:
I'm switching the aftermath of this thread -- http://
archives.postgresql.org/pgsql-general/2005-07/msg00501.php -- to -
hackers since it raised issues of potential concern to developers.
At various poi
-initdb.html
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Jul 20, 2005, at 8:35 PM, Jamie Deppeler wrote:
Hi,
Having an issue
heritance list --- but I don't see anything in the code implementingthat, so it evidently didn't get done yet."I don't immediately see TODO items correpsonding to these. Should there be some? Or do these qualify as bugs and should they be submitted to that queue? -- Thomas F. O
's no way to configure PostgreSQL to restrict access to the system catalogs in any meaningful way. I'm not really sure how to search for discussions on this topic in the archives, and I'm also not sure whether the forthcoming roles features will go any way toward eliminating t
r and the first user used to access any
database.
Just throwing out another suggestion.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
61
m is going to be put on hold indefinitely
after this discussion.
Anyway, just wanted to throw out some food for thought for the
practicality of a tool like pg_autovacuum.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http:
learly creates issues for the
developers.
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On May 11, 2005, at 11:35 AM, Josh Berkus wr
Does auto_vacuum vacuum the system tables?
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Feb 16, 2005, at 5:42 PM, Matthew T. O'Connor wrote:
Tom Lane wro
So why not have VACUUM FULL FREEZE just do what you propose: VACUUM
FULL then VACUUM FREEZE.
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On N
You also need to use -L to specify a location for the log file. By
default pg_autovacuum just logs to STDERR, so if you daemonize the
process (via -D), you won't be able to recover the output easily unless
you explicitly select a log file location.
-tfo
On Sep 22, 2004, at 2:29 AM, Iulia Pacura
pg_autovacuum will still be in contrib as of 8.0. It did not make
integration with the core distribution.
-tfo
On Sep 9, 2004, at 11:09 AM, Hervé Piedvache wrote:
Hi,
I was thinking that new things will appear in v8.0 about pg_autovacuum
??
But I find nothing new in README and/or Version Histor
So what is the thinking of HACKERS?
Does it make sense to include nothing and rather allow each
distribution to support its own?
Or should each distribution known to support postgres be invited to
submit the relevant script for inclusion? And, if so, should this be a
HACKERS [or other appropria
Sure. I didn't know there was a Debian start script. Because we
frequently keep up with the latest changes in postgres (which we
regularly use), I always build postgres from source. But that would be
a perfectly acceptable solution.
-tfo
On Aug 27, 2004, at 12:45 AM, Peter Eisentraut wrote:
Tho
I'd love to see a comment added to the linux start-script included in
contrib that referenced update-rc.d. It's useful to note because Debian
has different runlevels from Red Hat, and update-rc.d will
intelligently do the same thing as chkconfig for Debian systems.
If it's useful, I could post
See http://www.slony.org/
It's a master-multislave replication system that has a pretty robust
development cycle. It just reached a 1.0 release.
Whether any solution becomes a core part of the distribution remains, I
think, to be seen.
-tfo
On Jul 27, 2004, at 4:03 AM, chinni wrote:
Postg
I know, but I don't get too many opportunities to contribute... :)
Just figured I'd mention it.
-tfo
On Jul 23, 2004, at 4:06 PM, Tom Lane wrote:
"Thomas F.O'Connell" <[EMAIL PROTECTED]> writes:
I realize this is a trivial issue, but it seems like logic could be
added to the CASE statement to preve
In examining the output of psql -E to get some templates for some
queries I'm developing, I noticed in describe.c that there is logic to
inform the final IN clause that gets printed for relkind but no similar
logic for the CASE clause.
Here's what I get from a \d in 7.4.1:
SELECT n.nspname as "
> Um, doesn't "world's" mean "world is" ?
i forgot to provide a real-world example:
http://www.amazon.com/
"Earth's Biggest Selection"
-tfo
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-
> Um, doesn't "world's" mean "world is" ?
In this situation, the "'s" denotes possession, as in "the most advanced
open source database of the world".
"worlds" here is basically saying "every world most advanced open source
database" and does not, in any case, connote possession.
-tfo
-
i think i might've stumbled across a tiny defect in the optimizer.
unfortunately, i haven't the knowledge of the code to know where to
begin looking at how to address this problem.
anyway, consider the following:
create table foo(
id int2
);
create table bar(
id int2
f
is there any further word on 7.2.1, at this point? haven't seen mention
of it on the list in a while? is it still waiting on something big?
-tfo
Bruce Momjian wrote:
> Applied to current and 7.2.X. Thanks.
>
> (No delay for /contrib commits from maintainers.)
---(end
Bruce Momjian wrote:
> Here is a small list of big TODO items. I was wondering which ones
> people were thinking about for 7.2?
>
> * Allow inherited tables to inherit index, UNIQUE constraint, and primary key
> [inheritance]
i was wondering if there was any thought still being given to Oliv
Bruce Momjian wrote:
> Here is a general call for people to review other open-source database
> software and report back on things PostgreSQL can learn from them.
i don't know how much there is to learn since it doesn't seem as though
development has been active in a few years, but there's also
30 matches
Mail list logo