On 29 September 2010 20:18, Bernd Helmle wrote:
>
>
> --On 8. September 2010 09:00:33 +0100 Dean Rasheed
> wrote:
>
>> Here's an updated version with improved formatting and a few minor
>> wording changes to the triggers chapter.
>
> This version doesn't apply clean anymore due to some rejects in
On 30.09.2010 04:30, Itagaki Takahiro wrote:
On Wed, Sep 29, 2010 at 11:09 PM, Alvaro Herrera
wrote:
I'm not sure that it's a good idea to embed into the FDW API the set of
operations known to the executor. For example your proposal fails to
consider bitmap scans. Seems simpler and more gene
> On tor, 2010-09-30 at 08:09 +0900, Tatsuo Ishii wrote:
>> Problem with 9.0 doc build system is now it's a mixture of
>> DocBook/SGML *and* DocBook/XML(used for man pages). The former *only*
>> accepts EUC-JP, the latter *only* accepts UTF-8. So we are stuck.
>
> How do you get to the conclusion
On 29.09.2010 10:56, Fujii Masao wrote:
On Wed, Sep 29, 2010 at 11:47 AM, Robert Haas wrote:
So we've got two patches that implement synchronous replication, and
no agreement on which one, if either, should be committed. We have no
agreement on how synchronous replication should be configured,
On tor, 2010-09-30 at 08:09 +0900, Tatsuo Ishii wrote:
> Problem with 9.0 doc build system is now it's a mixture of
> DocBook/SGML *and* DocBook/XML(used for man pages). The former *only*
> accepts EUC-JP, the latter *only* accepts UTF-8. So we are stuck.
How do you get to the conclusion that DocB
Reference: https://commitfest.postgresql.org/action/patch_view?id=312
The patch from
http://archives.postgresql.org/message-id/ca2e4c4762eae28d68404...@amenophis
does not apply cleanly to the current git master:
$ patch -p1 < extend_not_null.patch
patching file src/backend/catalog/heap.c
patchin
Robert Haas writes:
> But that's not what Tom is talking about, I don't think: you might
> also want a way to explicitly whack the flag in pg_control around.
> That would probably be along the lines of pg_resetxlog. I'm not sure
> how much use case there is for such a thing, but if it's needed it
On Wed, Sep 29, 2010 at 11:55 AM, Leonardo Francalanci wrote:
> Can someone else test the patch to see if what I found is still valid?
> I don't think it makes much sense if I'm the only one that says
> "this is faster" :)
I ran a few more performance tests on this patch. Here's what I got
for th
Hi, I have a question about the latest patch.
On Sun, Aug 22, 2010 at 11:03 PM, Quan Zongliang
wrote:
> New patch attached. How about this?
>> I don't see us ever using anything other than auto or demand. The
>> others aren't for "regular services"
+ set_starttype(char *starttypeopt)
+ {
+
On Wed, Sep 29, 2010 at 11:01 AM, Robert Haas wrote:
> Makes sense to me. It seems that there are actually two halves to
> this problem: getting the child EMs to be generated in the first
> place, and then getting them to be examined at the appropriate time.
So I tried out the logic described in
(2010/09/30 10:28), Robert Haas wrote:
> 2010/9/29 KaiGai Kohei:
>>> But with that exception,
>>> they seemed to think that coarse-grained permissions would be fine for
>>> a basic implementation: perhaps even just install something in
>>> ProcessUtility_hook and bounce DDL across the board, so lon
On Wed, Sep 29, 2010 at 11:09 PM, Alvaro Herrera
wrote:
> I'm not sure that it's a good idea to embed into the FDW API the set of
> operations known to the executor. For example your proposal fails to
> consider bitmap scans. Seems simpler and more general to hand the quals
> over saying "I need
2010/9/29 KaiGai Kohei :
>> But with that exception,
>> they seemed to think that coarse-grained permissions would be fine for
>> a basic implementation: perhaps even just install something in
>> ProcessUtility_hook and bounce DDL across the board, so long as it's
>> controlled by reference to the
(2010/09/30 0:36), Robert Haas wrote:
> On Wed, Sep 29, 2010 at 9:59 AM, KaiGai Kohei wrote:
>> (2010/09/29 22:00), Robert Haas wrote:
>>>
>>> On Wed, Sep 29, 2010 at 6:38 AM, KaiGai Koheiwrote:
I don't think it is an option to move the hook after the pollution
of system catalog
> On Thu, Sep 30, 2010 at 8:09 AM, Tatsuo Ishii wrote:
>> Japanese community has been using the DocBook/SGML tool chain with
>> EUC-JP translated documents since SGML was emplyed by
>> PostgreSQL. Problem with 9.0 doc build system is now it's a mixture of
>> DocBook/SGML *and* DocBook/XML(used for
On Wed, Sep 29, 2010 at 3:56 AM, Fujii Masao wrote:
> On Wed, Sep 29, 2010 at 11:47 AM, Robert Haas wrote:
>> So we've got two patches that implement synchronous replication, and
>> no agreement on which one, if either, should be committed. We have no
>> agreement on how synchronous replication
2010/9/23 Robert Haas :
> All of this leaves me wondering why Greg ended up ifdefing out this
> code in the first place. There's probably something I'm missing
> here... but for now I can't think of a better idea than just removing
> the #ifdefs and hoping that whatever problem they were causing
On Wed, Sep 29, 2010 at 1:29 AM, Sushant Sinha wrote:
> Any updates on this?
>
>
> On Tue, Sep 21, 2010 at 10:47 PM, Sushant Sinha
> wrote:
>>
>> > I looked at this patch a bit. I'm fairly unhappy that it seems to be
>> > inventing a brand new mechanism to do something the ts parser can
>> > alr
Attached is a patch that implements replacing a primary key with another
index. This would help overcome the limitation that primary keys cannot be
reindexed
without taking exclusive locks.
The use case is to create an identical index, concurrenlty, with the
same
structure as the primary k
On Thu, Sep 30, 2010 at 8:09 AM, Tatsuo Ishii wrote:
> Japanese community has been using the DocBook/SGML tool chain with
> EUC-JP translated documents since SGML was emplyed by
> PostgreSQL. Problem with 9.0 doc build system is now it's a mixture of
> DocBook/SGML *and* DocBook/XML(used for man p
Hi,
Is there any reason the postmaster.pid and external_pid_file contents to be
different?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pg
> On ons, 2010-09-29 at 23:22 +0900, Tatsuo Ishii wrote:
>> Starting from 9.0, it seems unable to generate man pages for Japanese
>> translated sgml(generating html is ok). Until 8.4 it worked fine. Does
>> anybody succeeded in generating non English/multibyte translated man pages?
>
> You leave a
Magnus Hagander wrote:
> Comments and contributions are most welcome.
This is probably too esoteric to be worked on yet, but for this to
be useful for us we would need to pass the resulting files through
pg_clearxlogtail and gzip in an automated fashion. And we would
need to do regular log fi
Hello
What is the way to get tupledesc from array of records?
Regards
Pavel Stehule
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Sep 29, 2010 at 3:09 PM, Dimitri Fontaine
wrote:
> Robert Haas writes:
>> On Wed, Sep 29, 2010 at 10:02 AM, Tom Lane wrote:
>>> I think keeping the status information in a transient text file may
>>> still be a good design choice. If you push it into pg_control it will
>>> be impossible
Done
On Wed, 29 Sep 2010, Magnus Hagander wrote:
On Wed, Sep 29, 2010 at 17:31, Marc G. Fournier wrote:
On Wed, 29 Sep 2010, Alvaro Herrera wrote:
Excerpts from Peter Eisentraut's message of mi? sep 29 04:08:35 -0400
2010:
On s?n, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
Yeah
Hackers,
Any tips / conventional wisdom regarding running postgres on large-
ish memory ccNUMA intel machines, such as a 32G dual-quad-core,
showing two NUMA nodes of 16G each? I expect each postgres backend's
non-shared memory usage to remain nice and reasonably sized, hopefully
staying
Robert Haas writes:
> On Wed, Sep 29, 2010 at 10:02 AM, Tom Lane wrote:
>> I think keeping the status information in a transient text file may
>> still be a good design choice. If you push it into pg_control it will
>> be impossible to modify by hand.
>
> It could be done with a trivial tool, th
Oops.
Apparently type= service is the default, so we can remove that bit.
Then we should add state= all. The default = active, a third option = inactive.
So:
sc query state= all
should list all services, in all states.
And then we pipe to find which is the Windows equivalent of grep, but
it n
On ons, 2010-09-29 at 23:22 +0900, Tatsuo Ishii wrote:
> Starting from 9.0, it seems unable to generate man pages for Japanese
> translated sgml(generating html is ok). Until 8.4 it worked fine. Does
> anybody succeeded in generating non English/multibyte translated man pages?
You leave a lot to b
Colin,
> To query for Postgresql services on Windows use:
>
> sc query type= service | find "postgresql"
>
sad news is that (at least on my computer) it only finds running services.
Harald
--
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
Amtsgericht Stuttg
On Wed, Sep 29, 2010 at 17:31, Marc G. Fournier wrote:
> On Wed, 29 Sep 2010, Alvaro Herrera wrote:
>
>> Excerpts from Peter Eisentraut's message of mi? sep 29 04:08:35 -0400
>> 2010:
>>>
>>> On s?n, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
>>
Yeah, that's what you need to do. I woul
> > Here's my post with a (very simple) performance test:
> > http://archives.postgresql.org/pgsql-hackers/2010-02/msg00766.php
> I think the 10M rows test is more in line with what we want (83s vs. 646).
Can someone else test the patch to see if what I found is still valid?
I don't think it ma
On Wed, Sep 29, 2010 at 9:59 AM, KaiGai Kohei wrote:
> (2010/09/29 22:00), Robert Haas wrote:
>>
>> On Wed, Sep 29, 2010 at 6:38 AM, KaiGai Kohei wrote:
>>>
>>> I don't think it is an option to move the hook after the pollution
>>> of system catalogs, although we can pull out any information abou
Itagaki Takahiro writes:
> On Wed, Sep 29, 2010 at 11:56 PM, Tom Lane wrote:
>> I'm not sure that fixing this case is worth the amount of work it'd
>> take. How often do you drop just one member of a commutator pair?
> I found the issue when an user tries to write a "safe" installer
> script un
KaiGai,
* KaiGai Kohei (kai...@kaigai.gr.jp) wrote:
> All the existing security checks applies before modifying system catalogs.
>
> At least, I cannot find out any constructive reason why we try to apply
> permission checks on object creation time with different manner towards
> the existing priv
Peter Eisentraut wrote:
> Do you have an existing commit where you see a difference so I can
> try it and see if there is some other problem that my local
> configuration has?
Random poking around in the postgresql.git commits didn't turn up
any where it mattered, so here's before and after fi
On Wed, Sep 29, 2010 at 11:56 PM, Tom Lane wrote:
> I'm not sure that fixing this case is worth the amount of work it'd
> take. How often do you drop just one member of a commutator pair?
I found the issue when an user tries to write a "safe" installer
script under "DROP before CREATE" coding ru
On Wed, Sep 29, 2010 at 10:02 AM, Tom Lane wrote:
> Fujii Masao writes:
>> On Tue, Sep 28, 2010 at 10:34 PM, Robert Haas wrote:
>>> The idea of relying on the existence of recovery.conf to determine
>>> whether we should continue recovery forever or switch to normal
>>> running seems somewhat kl
On Tue, Sep 28, 2010 at 11:13 PM, Tom Lane wrote:
> Robert Haas writes:
>> ...what makes the pathkeys potentially useful is that they match the
>> root pathkeys for the query. However, without Greg's hacks, the
>> transposed child equivalence classes don't show up in the equivalence
>> member li
Alvaro Herrera writes:
> Excerpts from Itagaki Takahiro's message of mié sep 29 03:56:33 -0400 2010:
>> When we drop an operator used by other operators as COMMUTATOR or NEGATOR,
>> pg_dump generates an invalid SQL command for the operators depending on
>> the dropped one. Is it an unavoidable re
On sön, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
> On Sun, Sep 26, 2010 at 15:39, Heikki Linnakangas
> wrote:
> > On 25/09/10 19:43, Peter Eisentraut wrote:
> >>
> >> I'm not subscribed to pgsql-committers, but apparently under the new
> >> git-enabled setup, I'm getting a "Stalled post t
On Wed, Sep 29, 2010 at 15:54, Dave Page wrote:
> On Wed, Sep 29, 2010 at 2:45 PM, Magnus Hagander wrote:
>> On Mon, Sep 27, 2010 at 14:34, Dave Page wrote:
>>> On Thu, Sep 9, 2010 at 9:09 PM, Tom Lane wrote:
Robert Haas writes:
> It's hard to say what the safest option is, I think.
Hi,
Starting from 9.0, it seems unable to generate man pages for Japanese
translated sgml(generating html is ok). Until 8.4 it worked fine. Does
anybody succeeded in generating non English/multibyte translated man pages?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en
Bruce,
To query for Postgresql services on Windows use:
sc query type= service | find "postgresql"
On my machine this yields:
SERVICE_NAME: postgresql-9.0
DISPLAY_NAME: postgresql-9.0 - PostgreSQL Server 9.0
NB the space after type= is very important, don't ask me why...
I prefer to use '
Excerpts from Itagaki Takahiro's message of mié sep 29 03:56:33 -0400 2010:
> When we drop an operator used by other operators as COMMUTATOR or NEGATOR,
> pg_dump generates an invalid SQL command for the operators depending on
> the dropped one. Is it an unavoidable restriction?
Maybe we need a pg
On Wed, Sep 29, 2010 at 10:14 PM, Robert Haas wrote:
>> http://reorg.projects.postgresql.org/
>
> Can you reproduce that with this patch?
No, I can't use the machine anymore.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
Peter Eisentraut wrote:
> I have tried this switch various times now and haven't seen any
> difference at all in the output. Do you have an existing commit
> where you see a difference so I can try it and see if there is
> some other problem that my local configuration has?
Having looked at i
Excerpts from Robert Haas's message of mar sep 28 10:26:54 -0400 2010:
> Then:
>
> - Begin a sequential scan with the following set of quals.
> - Begin an index scan using the index called X with the following set of
> quals.
> - Fetch next tuple.
> - End scan.
I'm not sure that it's a good ide
Fujii Masao writes:
> On Tue, Sep 28, 2010 at 10:34 PM, Robert Haas wrote:
>> The idea of relying on the existence of recovery.conf to determine
>> whether we should continue recovery forever or switch to normal
>> running seems somewhat klunky to me. It mixes up settings with
>> control informa
(2010/09/29 22:00), Robert Haas wrote:
On Wed, Sep 29, 2010 at 6:38 AM, KaiGai Kohei wrote:
I don't think it is an option to move the hook after the pollution
of system catalogs, although we can pull out any information about
the new relation from syscache.
Why not?
All the existing securit
Excerpts from KaiGai Kohei's message of mié sep 29 06:38:09 -0400 2010:
> (2010/09/28 12:57), Robert Haas wrote:
> > 2010/9/1 KaiGai Kohei:
> >> This patch allows external security providers to check privileges
> >> to create a new relation and to inform the security labels to be
> >> assigned on
On Wed, Sep 29, 2010 at 2:45 PM, Magnus Hagander wrote:
> On Mon, Sep 27, 2010 at 14:34, Dave Page wrote:
>> On Thu, Sep 9, 2010 at 9:09 PM, Tom Lane wrote:
>>> Robert Haas writes:
It's hard to say what the safest option is, I think. There seem to be
basically three proposals on the
On Mon, Sep 27, 2010 at 14:34, Dave Page wrote:
> On Thu, Sep 9, 2010 at 9:09 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> It's hard to say what the safest option is, I think. There seem to be
>>> basically three proposals on the table:
>>
>>> 1. Back-port the dead-man switch, and ignore exit
On Mon, Sep 27, 2010 at 14:34, Dave Page wrote:
> On Thu, Sep 9, 2010 at 9:09 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> It's hard to say what the safest option is, I think. There seem to be
>>> basically three proposals on the table:
>>
>>> 1. Back-port the dead-man switch, and ignore exit
On Wed, Sep 29, 2010 at 9:16 PM, Robert Haas wrote:
> On Wed, Sep 29, 2010 at 2:44 AM, Greg Smith wrote:
> > One compiler warning I noticed that needs to get resolved:
> >
> > src/backend/commands/explain.c:
> >
> > explain.c: In function ‘ExplainMergeActions’:
> > explain.c:1528: warning: compa
On Wed, Sep 29, 2010 at 2:44 AM, Greg Smith wrote:
> One compiler warning I noticed that needs to get resolved:
>
> src/backend/commands/explain.c:
>
> explain.c: In function ‘ExplainMergeActions’:
> explain.c:1528: warning: comparison of distinct pointer types lacks a cast
>
> That is complaining
On Wed, Sep 29, 2010 at 1:12 AM, Itagaki Takahiro
wrote:
> On Wed, Sep 29, 2010 at 1:27 PM, Alvaro Herrera
> wrote:
>>> I see a consistent
>>> ~10% advantage for the sequential scan clusters.
>>
>> 10% is nothing. I was expecting this patch would give an order of
>> magnitude of improvement or s
On Wed, Sep 29, 2010 at 2:44 AM, Greg Smith wrote:
> The rest of the compiler warnings I saw didn't look related to his code,
> maybe stuff my picky Ubuntu compiler is noticing that was done recently to
> HEAD. I haven't checked HEAD without this patch yet to confirm, and am done
> for the night
On Wed, Sep 29, 2010 at 3:14 AM, Fujii Masao wrote:
> On Tue, Sep 28, 2010 at 10:34 PM, Robert Haas wrote:
>> The idea of relying on the existence of recovery.conf to determine
>> whether we should continue recovery forever or switch to normal
>> running seems somewhat klunky to me. It mixes up
On Wed, Sep 29, 2010 at 6:38 AM, KaiGai Kohei wrote:
> I don't think it is an option to move the hook after the pollution
> of system catalogs, although we can pull out any information about
> the new relation from syscache.
Why not?
> Sorry, it seems to me the idea simplifies the issue too much
Excerpts from Itagaki Takahiro's message of mié sep 29 01:25:38 -0400 2010:
> To be exact, It's very complex.
> During reconstructing tables, it requires about twice disk space of
> the old table (for sort tapes and the new table).
> After sorting the table, CLUSTER performs REINDEX. We need
> {sa
On Tue, 28 Sep 2010 22:14:22 +0300
Heikki Linnakangas wrote:
> On 09/28/10 17:26, Robert Haas wrote:
> > First, it seems totally wrong to assume that the same functions and
> > operators will be defined on the remote side as you have locally;
> > indeed, for CSV files, you won't have anything defi
Excerpts from Leonardo Francalanci's message of mié sep 29 03:17:07 -0400 2010:
> Here's my post with a (very simple) performance test:
>
> http://archives.postgresql.org/pgsql-hackers/2010-02/msg00766.php
I think the 10M rows test is more in line with what we want (83s vs. 646).
--
Álvaro Her
(2010/09/29 20:53), Dave Page wrote:
2010/9/29 KaiGai Kohei:
Does the git.postgresql.org down?
Harada-san being also unreachable now.
Seems to be a network issue. It's fine for some people (like me), and
down for others.
Thom reports that it's now back for him.
Now I'm reachable to the git
2010/9/29 KaiGai Kohei :
> Does the git.postgresql.org down?
>
> Harada-san being also unreachable now.
Seems to be a network issue. It's fine for some people (like me), and
down for others.
Thom reports that it's now back for him.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnak
It looks that way to me too.
.Oh wait, it works now.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Does the git.postgresql.org down?
Harada-san being also unreachable now.
--
KaiGai Kohei
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Thanks for your reviewing, and sorry for delayed responding due to
the LinuxCon Japan for a couple of days.
(2010/09/28 12:57), Robert Haas wrote:
2010/9/1 KaiGai Kohei:
This patch allows external security providers to check privileges
to create a new relation and to inform the security labels
On ons, 2010-09-15 at 12:58 -0500, Kevin Grittner wrote:
> I just discovered the --patience flag on the git diff command, and
> I'd like to suggest that we encourage people to use it when possible
> for building patches. I just looked at output with and without it
> (and for good measure, before a
On ons, 2010-09-29 at 10:19 +0200, Magnus Hagander wrote:
> > Btw., I think it would be more proper if the commit notifications
> > contained a header like
> >
> > Sender: g...@gitmaster.postgresql.org
> >
> > so that they don't give a false impression about the origin of the
> > message.
>
> We d
On Wed, Sep 29, 2010 at 05:40, Fujii Masao wrote:
> On Tue, Sep 28, 2010 at 5:23 PM, Magnus Hagander wrote:
>>> When I ran that, the size of the WAL file in inprogress directory
>>> became more than 16MB. Obviously something isn't right.
>>
>> Wow, that's weird. I'm unable to reproduce that here
On Thu, Sep 23, 2010 at 6:49 PM, Dimitri Fontaine
wrote:
> Automatic registration is a good answer to both your points A)
> monitoring and C) wal_keep_segments, but needs some more thinking wrt
> security and authentication.
Aside from standby registration itself, I have another thought for C). K
On Wed, Sep 29, 2010 at 10:08, Peter Eisentraut wrote:
> On sön, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
>> On Sun, Sep 26, 2010 at 15:39, Heikki Linnakangas
>> wrote:
>> > On 25/09/10 19:43, Peter Eisentraut wrote:
>> >>
>> >> I'm not subscribed to pgsql-committers, but apparently unde
Hello
2010/9/29 Itagaki Takahiro :
> On Thu, Sep 9, 2010 at 8:57 PM, Pavel Stehule wrote:
>> I am sending a updated version.
>>
>> changes:
>> * tag %v removed from format function,
>> * proprietary tags %lq a iq removed from sprintf
>> * code cleaned
>>
>> patch divided to two parts - format fun
On Wed, Sep 29, 2010 at 11:47 AM, Robert Haas wrote:
> So we've got two patches that implement synchronous replication, and
> no agreement on which one, if either, should be committed. We have no
> agreement on how synchronous replication should be configured, and at
> most a tenuous agreement th
On Tue, 28 Sep 2010 10:26:42 -0400
Robert Haas wrote:
> On Mon, Sep 27, 2010 at 2:50 AM, SAKAMOTO Masahiko
> wrote:
> > ?http://wiki.postgresql.org/wiki/SQL/MED
> With regard to what is written here, it strikes me that it would be an
> extremely bad idea to try to mix reloptions or attoptions wit
When we drop an operator used by other operators as COMMUTATOR or NEGATOR,
pg_dump generates an invalid SQL command for the operators depending on
the dropped one. Is it an unavoidable restriction?
CREATE OPERATOR <<< (
PROCEDURE = text_lt, LEFTARG = text, RIGHTARG = text, COMMUTATOR = >>>
> > 10% is nothing. I was expecting this patch would give an order of
> > magnitude of improvement or somethine like that in the worst cases of
> > the current code (highly unsorted input)
>
> Yes. It should be x10 faster than ordinary method in the worst cases.
Here's my post with a (very
On Tue, Sep 28, 2010 at 10:34 PM, Robert Haas wrote:
> The idea of relying on the existence of recovery.conf to determine
> whether we should continue recovery forever or switch to normal
> running seems somewhat klunky to me. It mixes up settings with
> control information. Maybe the control in
80 matches
Mail list logo
