e such.
+1 from me. In case of recovery, I think one should still get the full
output, no? It might be important information then.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
0 seconds, but I suppose one might want a smaller naptime
for a very active system?
A PostgreSQL database on my laptop for testing. It should use as little
resources as possible while being idle. That would be a scenario for
naptime greater than 60 seconds, wouldn't it?
Best Regards
Michae
apabilities
in core.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
tch status says "waiting on update from author":
http://archives.postgresql.org/pgsql-patches/2007-04/msg00331.php
Any updates on this?
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
=> select length(n) from test;
length
100017
(1 row)
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
hers.
I just see no compelling reason to comply with a certain standard here.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining colum
on_age".
Please lets have the unambiguous abbreviations. Please lets make it all
case-insensitive. After all this discussion, what about a straight
forward vote? Bruce, we had those before, no?
Best Regards
Michael Paesold
---(end of broadcast)
quite arrogant. Most people here have tried to bring arguments and
reasoning... you put it off with irrelevant anecdotes in the wrong context.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Marko Kreen wrote:
On 6/21/07, Michael Paesold <[EMAIL PROTECTED]> wrote:
Marko Kreen wrote:
> Considering Postgres will never user either "meter" or "mile"
> in settings, I don't consider your argument valid.
>
> I don't see the value of having
ot;
somehow resets $? on windows, sometimes, under some circumstances?
Perhaps just move up the "my $status.." one line up?
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 6: explain analyze is your friend
could provide numbers from production high use databases. We could
probably back those down a little and make more reasonable numbers.
Please do so. Perhaps others can also tell their typical settings.
Best Regards
Michael Paesold
---(end of broa
just
burning cycles. What about a threshold of 10 or 50, to have at least
some sanity limit? Even though the cost of vacuum of a small table is
low, it is still not free, IMHO, no?
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 9: In ver
than the list of
historic startup messages that were removed recently. Just my two €-cents.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
] The idea was born in the thread starting here (involving
Tom Lane, Joshua Drake, and Teodor Sigaev):
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00912.php
with the conclusion here:
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00936.php
Best Regards
Michael Paesold
-
e migration for text search in
8.3 as a benefit of getting into core and be dump-able.
I guess so. Especially if you change some functions, they will have to
change source code anyway. So you can as well cleanup all functions that
don't fit into a sound naming schema.
Best Regards
Michae
still, if we pretend that
there are no subtransaction, that command should too propage to the
outermost transaction on release, shouldn't it?
...
I believe that for consistencies sake, the "set transaction read only"
should have propagated to the outermost transaction on "
Tom Lane wrote:
Michael Paesold <[EMAIL PROTECTED]> writes:
I don't think it's a very good idea to make SET TRANSACTION an alias for
SET LOCAL, because SET TRANSACTION has already got its own meaning in the
SQL spec - it sets transaction modes.
Yeah --- I'm not sur
eep the behavior simple.
What about a new separate lock type for analyze? Couldn't that really
solve the issue? I know I'm just hand-waving here ;-)
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 4: Have you
point (even when the maintenance
window ends too early... or perhaps any cleanup task started during a
maintenance window should keep it's "maintenance priority"?)
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 5: don&
earlier: it will be before end of beta that
people will complain about more than just restoring dumps. ;-)
So does this approach work for both analyze as well as vacuum?
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have
r just disable
cost-delay, as Heikki suggested. There might be valid work-loads for both
options...
Btw., I am grateful you took up the work here, Simon.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 1: if posting/reading through Usen
.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
chema changes (doesn't sound like a good idea anyway). In that case
they would better issue manual vacuums on such tables.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ing harder?
IMHO this is exactly what we want. It does only offer more information when
you already got authentication right and therefore doesn't open an
information leak.
Not sure about the warning when creating a role with a password but
nologin. Could be useful.
Best Regards
r own command aliases, e.g. "hg cdiff
..." to do -c diffs.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
d of course the user complained.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Alvaro Herrera wrote:
Michael Paesold wrote:
Simon Riggs wrote:
On Thu, 2007-10-25 at 13:41 -0300, Alvaro Herrera wrote:
...
FWIW I disagree with cancelling just any autovac work automatically; in
my patch I'm only cancelling if it's analyze, on the grounds that if
you have reall
ajor performance fixes may sometimes slip in as "bug fixes".)
If you all decide against that patch, we might as well just go for RC1. The
catalog changes seem rather trivial, and just a required initdb is no
reason for calling it another beta, IMHO.
Great work on that patch, btw.!
Be
casting now.
Just my $0.02.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
w to make that
work case-insensitively.
Wouldn't it be possible to create a variant of regexp_replace, i.e.
regexp_replace(citext,citext,text), which would again lower-case the
first two arguments before passing the input to
regexp_replace(text,text,text)?
Best Regards
Michael Paesold
David E. Wheeler writes:
On Jul 17, 2008, at 03:45, Michael Paesold wrote:
Wouldn't it be possible to create a variant of regexp_replace, i.e.
regexp_replace(citext,citext,text), which would again lower-case
the first two arguments before passing the input to
regexp_replace(text
Am 19.08.2008 um 20:47 schrieb Tom Lane:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Joshua Drake wrote:
Is our backpatch policy documented? It does not appear to be in
developer FAQ.
Seems we need to add it.
I'm not sure that I *want* a formal written-down backpatch policy.
Whether (and h
, including a link to the documentation of GUC parameters.
As a kind of starting point for (new) users.
Best Regards
Michael Paesold
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Comments/objections?
Yeah, please fix this performance regression in the 8.3 branch. This
would affect most of the JDBC applications out there, I think.
Best Regards
Michael Paesold
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Am 01.04.2008 um 13:14 schrieb Dave Cramer:
On 1-Apr-08, at 6:25 AM, Michael Paesold wrote:
Am 01.04.2008 um 01:26 schrieb Tom Lane:
While testing the changes I was making to Pavel's EXECUTE USING
patch
to ensure that parameter values were being provided to the planner,
it b
slaves, and SQL window support.
I don't think these people need guidance on how to manage the
project, they need some sort of way to feel comfortable saying "will
pledge $Y for feature $X" in a way that makes sense on both sides.
That's what I thought, too. That page just
the most reasonable thing to do. Regarding the log
messages about orphaned tables, it would be nice if you could add a
hint/detail message explaining how to cleanup those tables. If that's
possible.
Best Regards
Michael Paesold
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
e are allowing a
nonstandard half-measure to drive our thinking, rather than solving
the
real problem which is column-level collations.
Wouldn't you still need per-database and per-table default collations?
At least MySQL does have such a concept.
Best Regards
Michael Paesold
--
Sent via
imply ON_ERROR_STOP or some variant by default?
Sounds reasonable, +1 from me.
Regards
Michael Paesold
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
,
Michael Paesold
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
about this all?
Best Regards,
Michael Paesold
--> logfile:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
'bench_big_pkey' for table 'bench_big'
DEBUG: recycled transaction log file 009F
[...skipping: recycled transaction log file 0
Michael Meskes wrote:
> Hi,
>
> is a pl/pgSQL function completely parsed once? Or is only the next
> statement parsed as with many interpreters? If it's the latter it would
> mean one has to run each branch just to see if the syntax is correct. Is
> that true?
>
> Michael
If the docs are true,
ch of a job to keep track of
> > that many IP blocks too.
>
>
> I'd suggest setting a cookie, so I only see the 'pick a mirror' the
> first time. And provide a link to 'pick a different mirror' that resets
> or ignores the cookie.
If I had a vote, I
Hi,
I have come across a problem (bug?) with PL/pgSQL GET DIAGNOSTICS.
In a PL/pgSQL function I want to insert into a table and get the OID back.
That usually works with
GET DIAGNOSTICS last_oid = RESULT_OID;
right after the insert statement.
But if the table that I insert to has a rule (or per
Hi,
I am wondering about bad INSERT performance compared against the speed of
COPY. (I use 7.2.2 on RedHat 7.2)
I have a table with about 30 fields, some constraints, some indexes, some
foreign key constraints. I use COPY to import old data. Copying about
10562 rows takes about 19 seconds.
For
Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > I have come across a problem (bug?) with PL/pgSQL GET DIAGNOSTICS.
>
> Hm. This seems to be SPI's version of the same definitional issue
> we're contending with for status data
Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > To insert another 10562 rows takes about 12 minutes now!!!
>
> See
> http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/populate.html
> particularly the point about not committing ea
Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > To insert another 10562 rows takes about 12 minutes now!!!
>
> > As I said I wrote a function to insert the rows (PL/pgSQL). All values
were
> > inserted inside a single function ca
nsert times to lowest possible:
vacuum full; helps
vacuum analyze; helps
analyze ; of table that I insert to doesn't help!
analyze ; of any table reference in foreign key constraints
doesn't help!
Only vacuum will reset the insert times to the lowest possible!
What d
Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > Only vacuum will reset the insert times to the lowest possible!
> > What does the vacuum code do?? :-]
>
> It removes dead tuples. Dead tuples can only arise from update or
> delete ope
SELECT INTO ret invoice_id FROM invoice WHERE invoice_id < \'30\'
ORDER BY invoice_id DESC limit 1;
RETURN ret + 1;
END;
' LANGUAGE 'plpgsql';
Using that is nearly as fast as a regular sequence.
Thanks to all of you for your help.
Best Regards,
Michael Paeso
least you can set up different users per database, so that it doesn't
matter if the proposed restriction setting is by database or by user.
Regards,
Michael Paesold
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
This document:
http://developer.postgresql.org/docs/postgres/release-7-2-3.html
mentions a release date of 2002-10-01 for version 7.2.3.
It isn't on the main website, tough, is it?
Regards,
Michael
---(end of broadcast)---
TIP 2: you can get off
Justin Clift <[EMAIL PROTECTED]> wrote:
> Hi Michael,
>
> Michael Paesold wrote:
>
> > Hi Justin,
> >
> > I am from Austria, and I would like to help. I could provide a German
> > translation. The Babelfish's translation is really funny. Ma
Tino Wildenhain <[EMAIL PROTECTED]> wrote:
> Hi Justin,
>
> > Good point. For the moment we've whipped up that MS Excel document
> > (created in OpenOffice of course) of all the English text strings in the
> > site and emailed it to the volunteers. :)
>
> Btw. did you ever unzip the native Open
Mike Mascari <[EMAIL PROTECTED]> wrote:
> I can't test the use of CURRENT_TIMESTAMP because I have Oracle
> 8, not 9.
What about NOW()? It should be available in Oracle 8? Is it the same as
SYSDATE?
Regards,
Michael Paesold
---
Mike Mascari <[EMAIL PROTECTED]> wrote:
> Michael Paesold wrote:
>
> > What about NOW()? It should be available in Oracle 8? Is it the same as
> > SYSDATE?
> >
>
> Unless I'm missing something, NOW() neither works in Oracle 8
> nor appears in
ish's translation is really funny. Machine
translation is readable, but it is no advocacy. ;-) I do not really nead an
interface, but just tell me in what way you want the texts.
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 2: y
>
> Is that good?
CURRENT_TIMESTAMP etc. are converted to now()::TIMESTAMP, at least in 7.2,
right?
So when there are all three options available, it would be easy to change
the behaviour of CURRENT_DATE/TIME/TIMESTAMP, right?
SET .. or GUC would be options, no?
Best Regards,
Michael Pa
>
> regards, tom lane
That is a very good point. At least with serializable transactions it seems
perfectly reasonable to return a frozen CURRENT_TIMESTAMP. What do you think
about read-commited level? Can time be commited? ;-)
It would be even more surprising to new u
, if
CURRENT_TIMESTAMP advances with each statement, the result would also
change. That is an inherent problem with read-commited though and has not so
much to do with the timestamp behavior.
Regards,
Michael Paesold
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
setup proves to work fast and reliable
I would also be interested in such a locking. I don't care about
the feature if I find the postgresql/NFS/netapp-filer setup to be
unreliable or bad performing.
I'll see.
Regards,
Michael Paesold
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ady been cc'd to you, you
can use:
set ALL eliminatecc your-email
for a full list of set options send:
help set
to majordomo.
Regards,
Michael Paesold
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
h directory structures better over the oracle style.
Regards,
Michael Paesold
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > In a PL/pgSQL function I want to insert into a table and get the OID
back.
> > That usually works with
> > GET DIAGNOSTICS last_oid = RESULT_OID;
> > right a
`/spool/home/teodor/pgsql/src'
> gmake: *** [all] Error 2
> % bison -V
> bison (GNU Bison) 1.35
Although I am not a hacker, I think you just need to upgrade
bison to version 1.75 if you want to build from CVS. The ecpg
interface is broken with version 1.35 of bison.
Best
Tom Lane <[EMAIL PROTECTED]> wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Basically, total connections is to be set larger than you think you will
> > ever need, while you expect per-db to be hit, and if something keeps
> > trying to connect and failing, we may get very bad connection
>
usage accounting in that case, so that users can be charged for
added database usage. That would probably also be easier to
implement because each user would have their own database and
only pg_xlog shared -- that part seems tricky as you said before.
Best Regards,
Michael Paesold
-
LEVEL
-
READ COMMITTED< this should be SERIALIZABLE, no??
(1 row)
billing=# commit;
COMMIT
Is it a bug?
Regards,
Michael Paesold
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
h
t feasibility, just liked the idea)
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
pktable where base2=2;
delete from pktable where base1=2;
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the TODO items, apache has a nice description of their accept()
serialization:
http://httpd.apache.org/docs-2.0/misc/perf-tuning.html
Perhaps this could be useful if someone decided to start implementing those
features.
Regards,
Michael Paesold
---(end of broadcast)---
found!
Download PostgreSQL from the primary site
Read this if you would like to host a mirror.
Of course the primary FTP site is already unavailable (530 - maximum
number of users reached).
I get the same error for older releases, too. Can someone look into this?
Best Regards
Michael Paesold
Shane Ambler wrote:
Michael Paesold wrote:
Not being subscribed to any more appropriate list, I post this here on
hackers.
I just wanted to download the postgresql-8.0.9 tarball. The page I got
was this:
Choose a download mirror
Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz
We could
Magnus Hagander wrote:
Michael Paesold wrote:
I just wanted to download the postgresql-8.0.9 tarball. The
page I got was this:
Choose a download mirror
Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz
We could not query the database or no mirrors could be found!
Download PostgreSQL from
s at a time in accumArrayResult(). Most of the rest of the
code deals with resizing arrays using a "double it each time it has
to grow" approach, I wonder why this is different?
Without reading the code, I guess that simply means O(n^2) runtime. This
should be fixed, then, right?
: Table has type numeric, but query expects numeric.
STATEMENT: UPDATE reminder SET reminder_charges='0' WHERE reminder_id=29362
reminder_charges is defined as:
reminder_charges | numeric(5,2) | not null
I guess this is a bug.
Best Regards
Micha
Tom Lane wrote:
Michael Paesold <[EMAIL PROTECTED]> writes:
after upgrading from 8.1.5 to 8.1.7, I got errors in the server log when
updating decimal values using string constants.
Have you got a constraint or functional index on that column?
Yes.
Check const
I understand, it's as simple as this (untested):
CREATE TABLE tab (
c DECIMAL(5,2) NOT NULL,
CHECK (c >= 0)
);
INSERT INTO tab ('0');
Right?
Or at least:
UPDATE tab SET c='0';
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 6: explain analyze is your friend
; after
rebuilding the repository? (This command would re-sync the trac database
with the repository.) Otherwise I would certainly expect such issues as
Alvaro describes.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 1: if posting/reading th
A DBA will usually not even learn about this issue until they are presented
with a failing restore.
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http:
that
implements connection pooling using the JDBC API, i.e. it is an *internal*
pool running inside the app servers JVM. PG Admin cannot in any case
connect through this pool.
Best Regards
Michael Paesold
[1] http://sourceforge.net/projects/c3p0
---(end of broadcast)
edStatement but
without a "prepare-threshold"[*] set. If it uses the unnamed-statement,
then I guess the proposed change would be a win.
Best Regards
Michael Paesold
[*] This option determines, after how many executes of a prepared
statement, the driver will switch to server-side prepares.
st bind, or right at
prepare.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 6: explain analyze is your friend
coding.
Even with psql there could be issues with existing scripts, but I see a
benefit at least.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
s now.
Sure a directory can be skipped. I am confused how it could change
expected files because it only formats C files.
As far as I understand, ecpg creates .c files.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP 1: if posting/re
e bit of work to
regenerate the links. I'll try to work on that.
I think it would also help if you would create reference runs for the
latest 8.0 and 8.1 releases on the new hardware.
Best Regards
Michael Paesold
---(end of broadcast)---
TIP
at query level, but not in postgresql.conf.
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Bruce Momjian wrote:
Michael Paesold wrote:
Magnus Hagander wrote:
[snip]
Michael, I am not sure why you come to the conclusion that open_sync
requires turning off the disk write cache. I saw nothing to indicate
that in the thread:
I was just seeing his error message below...
http
t's better when cast selection does not depend
on the search_path. It seems dangerous for objects that you don't usually
qualify with a schema. With all other objects in schemas I can think of, you
can easily write the full-qualified name.
So I vote for t
Alvaro Herrera wrote:
On Tue, Apr 12, 2005 at 08:39:09AM +0200, Michael Paesold wrote:
Tom Lane wrote:
>The other possible solution that comes to mind is to invent the notion
>that a cast has a specific owner (which arguably it should have anyway)
>and then say that "system casts&qu
Bruce would want is a way to "stop new transactions, archive and
shutdown", which would do this atomically. Then we could have another
shutdown switch for pg_ctl.
But yea, a documentation for a manual procedure would be ok, too, just not
as user friendly.
Best Regards,
Micha
27;ttyonly' and figure out a default
My vote:
1) disable it by default for all sessions
2) enable it with \set (can be set in .psqlrc), but provide a way so it only
works with interactive commands, either always, or something like
\set ON_ERROR_ROLLBACK interactive
Best Regards,
Michael Paeso
to put savely into .psqlrc (what some people will want, I have \set
AUTOCOMMIT off in my .psqlrc file, too, and I know I am not the only one)
* another one that will also work in scripts
I hope you understand and accept the issue here.
Best Regards,
Michael Paesold
---(end of
Richard Huxton wrote:
Michael Paesold wrote:
But people (like me for example) will want to enable this behaviour by
default. So they (me too) will put the option in .psqlrc. It is then
enabled "by default". But then many of my scripts will destroy data
instead of just erroring out.
I
resql design and philosophy in the first place, but well,
it is because of them that postgresql exists as what it is.
Most of the hassles can be avoided by speaking up on hackers first and
convince some one with good postgresql know-how to help you get your work on
track.
Best Regards,
Michael P
quot; in the mailing list archives of pgsql-committers.)
Bruce Momjian wrote:
> Please check the web site version. Someone has already implemented
> "Allow COPY to optionally include column headings in the first line".
Hope that clarifies the situation a little bit.
Best Regards,
Mic
), so
anything older than that is probably not representative.
The run with 60 minutes checkpoint timeout seems to be 06/04/05, the one
with 5 minutes is 06/18/05.
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 8: explain analyze is your
e postgres database could just look like roots home directory in
/root,... would you exclude that from backups?
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
users? For many people it will be hard work to type the subquery to get
the database oid.
I vote for all (possibly corrected) functions to be moved into core.
Best Regards,
Michael Paesold
---(end of broadcast)---
TIP 9: In versions below 8.0, t
1 - 100 of 189 matches
Mail list logo
