Re: unsubscribe

[Achilleas Mantzios]

On 21/11/2017 09:19, Craig Ringer wrote:

On 21 November 2017 at 15:17, Rafal Pietrak > wrote:

Hi all,

Have anyone noticed, that last couple of days on the list, can become a
nice example of HOWTO turn the best list on the planet into a nightmare?

Pls forgive rudeness, but IMHO, whoever made the "upgrade" should
manually take all the "unsubscribe" messages from archive and do that
"unsubscription" by hand  instead of giving not always helpfull
guidance.


The list used to have a filter that blocked messages with "unsubscribe" in the 
subject or forced them into moderation the moderation queue.

I thought that'd be preserved with the PgLister migration.

But really, a nightmare? Yeah, it's a pain, but I think that's laying it on a 
bit strong. Personally I appreciate the hard and usually thankless work the 
infrastructure and admin team do.


The problem IMHO is not the traffic per se, but the fact that the vast majority 
are unsubscribe messages. Maybe if subscribe messages were included that would 
certainly feel better :)



--
 Craig Ringer http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

Re: unsubscribe

[Rafal Pietrak]

Hi all,

Have anyone noticed, that last couple of days on the list, can become a
nice example of HOWTO turn the best list on the planet into a nightmare?

Pls forgive rudeness, but IMHO, whoever made the "upgrade" should
manually take all the "unsubscribe" messages from archive and do that
"unsubscription" by hand  instead of giving not always helpfull
guidance.

I do system maintenance for money. I do that when I screwup.

Regards,

-R

W dniu 21.11.2017 o 04:16, Ryan pisze:
> Hi,
> 
> All right, so not for lack of trying, I cannot figure out how to
> unsubscribe. I've tried three different things, but they've either been
> ineffective or result in me getting an automatic email that the attempt
> failed. Kindly help? I enjoyed my daily digest of PostgreSQL messages,
> but this has been a bit difficult to manage.
> 
> Best regards.
> 
> On Mon, Nov 20, 2017 at 9:37 PM, Danyelle Davis  > wrote:
> 
> 
> On Mon, Nov 20, 2017 at 9:29 PM, Amila Jayasooriya
> > wrote:
> 
> Please unsubscribe me from the list.
> 
> Thanks and Regards
>  Amila Jayasooriya
> 
> On Tue, Nov 21, 2017 at 3:48 AM, Ibram Remzi
> > wrote:
> 
> Please unsubscribe me from the list.
> 
> Please look at the listserv for options on how to unsub.  Yall are
> clogging the list with these.  
> 
> 
> 
> 
>   Virus-free. www.avast.com
> 
> 
> 
> 
> 
> <#m_4396185798928146462_m_941694909827362166_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> 

Re: [GENERAL] Query Using Massive Temp Space

[Cory Tucker]

On Mon, Nov 20, 2017 at 9:36 AM Tom Lane  wrote:

> 9.6.what exactly?
>

9.6.5


>
> The only thing I can think of offhand that could create temp files far in
> excess of the actual data volume is if a hash join repeatedly decides that
> it needs to increase the number of hash batches.  We have seen that happen
> in cases where an inner relation contains a vast number of identical hash
> key values: they all go into the same bucket, and the executor keeps
> splitting the batch trying to reduce its size, but being all identical
> values it will never be the case that some rows go into a different batch
> than others.  There is logic in there to give up splitting when this
> happens, but maybe it's not firing in your case, or maybe somebody broke
> it recently :-(.
>

I think this is exactly the scenario that happened. More below.


>
> I find it suspicious that your plan involves two separate hash joins both
> of which have a much larger table on the inside than the outside ---
> offhand that does not look very sane.  So there's also a question of
> why did the planner do that.
>
> What can you tell us about the distributions of the join keys for the two
> hash joins --- are those keys unique, or a bit less than unique, or very
> much not unique?
>

We were able to get the query to run, without using much temp space at all,
by eliminating this portion of the query:

  LEFT JOIN donation d2
ON mca.parent_id = d2.candidate_id AND mca.parent_id IS NOT NULL AND
mca.account_id = d2.account_id
   AND d2.account_id NOT IN (1, 2, 3, 195, 196, 81)

The resultant full query plan is attached (json format this time).

What was happening is that there is a fairly non-unique "parent_id" value
(66k times) that is creating a very large hashkey that it cannot break into
a smaller chunks -- so, essentially what your guess was, Tom.  Perhaps
worth investigating whether that code is still functioning as intended.

Incidentally, I'd also be interested in any suggestions for refactoring
this query for better performance.  It does complete now if we exclude the
problematic account but still takes quite a bit of time and we expect our
dataset to only get bigger.

thanks
--Cory
[
  {
"Plan": {
  "Node Type": "Aggregate",
  "Strategy": "Sorted",
  "Partial Mode": "Simple",
  "Parallel Aware": false,
  "Startup Cost": 18682578.29,
  "Total Cost": 18984282.25,
  "Plan Rows": 529305,
  "Plan Width": 526,
  "Actual Startup Time": 827809.462,
  "Actual Total Time": 1576769.572,
  "Actual Rows": 15170854,
  "Actual Loops": 1,
  "Output": ["c.account_id", "c.candidate_id", "c.number", 
"c.pre_direction", "c.street_name", "c.street_suffix", "c.post_direction", 
"c.secondary_designator", "c.secondary_number", "c.city", "c.state", 
"c.zipcode", "array_agg(DISTINCT jsonb_build_object('first_name', 
cp.first_name, 'middle_name', cp.middle_name, 'last_name', cp.last_name, 
'suffix', cp.suffix, 'salutation', cp.salutation, 'spouse', cp.spouse))", 
"array_agg(DISTINCT mce.email) FILTER (WHERE (mce.email IS NOT NULL))", 
"array_agg(DISTINCT jsonb_build_object('country_code', mcp.country_code, 
'national_number', mcp.number)) FILTER (WHERE (mcp.country_code = 1))", 
"array_agg(DISTINCT jsonb_build_object('donation_amount', d.donation_amount, 
'donation_date', COALESCE(d.donation_date, make_date(d.donation_year, 1, 1)), 
'charity', d.account_id)) FILTER (WHERE (d.account_id IS NOT NULL))"],
  "Group Key": ["c.account_id", "c.candidate_id", "c.number", 
"c.pre_direction", "c.street_name", "c.street_suffix", "c.post_direction", 
"c.secondary_designator", "c.secondary_number", "c.city", "c.state", 
"c.zipcode"],
  "Shared Hit Blocks": 15,
  "Shared Read Blocks": 1389726,
  "Shared Dirtied Blocks": 0,
  "Shared Written Blocks": 0,
  "Local Hit Blocks": 0,
  "Local Read Blocks": 0,
  "Local Dirtied Blocks": 0,
  "Local Written Blocks": 0,
  "Temp Read Blocks": 2153328,
  "Temp Written Blocks": 2292366,
  "Plans": [
{
  "Node Type": "Unique",
  "Parent Relationship": "InitPlan",
  "Subplan Name": "CTE candidates",
  "Parallel Aware": false,
  "Startup Cost": 2312476.04,
  "Total Cost": 2666322.40,
  "Plan Rows": 5293052,
  "Plan Width": 80,
  "Actual Startup Time": 80515.358,
  "Actual Total Time": 119791.347,
  "Actual Rows": 15170854,
  "Actual Loops": 1,
  "Output": ["match_candidate_address.account_id", 
"match_candidate_address.candidate_id", "match_candidate_address.parent_id", 
"match_candidate_address.number", "match_candidate_address.pre_direction", 
"match_candidate_address.street_name", "match_candidate_address.street_suffix", 
"match_candidate_address.post_direction", 
"match_candidate_address.secondary_designator", 
"match_candidate_address.secondary_number", "match_candidate_address.city", 

Re: unsubscribe

[John R Pierce]

On 11/20/2017 7:40 PM, Tom Lane wrote:

Depending on what mail software you use, you might have to use some
command like "View raw headers" or "View original message" to see
commonly-hidden headers like List-Unsubscribe.



in gmail, its Show Original, on the down-tick menu next to the 'Reply' 
button.



--
john r pierce, recycling bits in santa cruz

One Partition by list is always chosen by planner

[legrand legrand]

Hello,

after creating a table wiki_data_part with
partition by list (category);

and creating partitions like
CREATE TABLE wiki_data_part_a PARTITION OF wiki_data_part
FOR VALUES IN ('ang.q',...,'arc');
CREATE TABLE wiki_data_part_b PARTITION OF wiki_data_part
FOR VALUES IN ('bs.s',...,'bg.n');

copy table wiki_data_part from ...;

analyze wiki_data_part;

explain select * from wiki_data_part where category='en'

| Append  (cost=0.00..21595.75 rows=4 width=102)

  
|   ->  Seq Scan on wiki_data_part_e  (cost=0.00..21578.00 rows=1 width=102)

  
| Filter: ((category)::text = 'en'::text)   

  
|   ->  Seq Scan on wiki_data_part_s  (cost=0.00..17.75 rows=3 width=102)   

  
| Filter: ((category)::text = 'en'::text)

partition wiki_data_part_s (that has more than 100 values in its list) is
always scanned,
even when where predicates are not in its values list ...

Problem occurs on
PostgreSQL 10.0, compiled by Visual C++ build 1800, 64-bit
even without data loaded.

If this is a problem of max values, maybe this could be added in doc ?


wiki_data_wrong_part_s_chosen.sql

  



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

Re: unsubscribe

[Ryan]

.Hmm, yes, indeed. I tried to login to that site with my listserv account
credentials, and that got me nowhere either.

Also, I just checked this message too. Downloaded the raw message including
headers. Search in text editor for string "List-Unsubscribe" and anything
at all like it comes up with only the text you wrote in your email, Tom.
I'm definitely not getting it... I thought maybe I had set these messages
to forward through my work email account, but I just verified that there is
no forwarding. I subscribed under the address at which I'm reading them.

Ryan

On Mon, Nov 20, 2017 at 11:07 PM, Tom Lane  wrote:

> Danyelle Davis  writes:
> > https://lists.postgresql.org/manage/
>
> But note that that's only going to help if you've set up a "PG community
> account", which up to now nobody has needed unless they wanted to edit
> our wiki or work in our commitfest app, so it's a good bet that most
> subscribers to our lists haven't got one.  The List-Unsubscribe link
> is supposed to work without needing a community account.  It disturbs
> me that Ryan says he's not seeing one in traffic from the list.
> I certainly am getting one in all the mail I get from the new server.
>
> I wonder whether there are complicating factors Ryan hasn't mentioned,
> like maybe his traffic is getting forwarded from some other account
> on some other email provider.  If so, maybe the List-Unsubscribe
> header is getting dropped in forwarding?  That's a reach, but it's
> hard to explain otherwise.
>
> regards, tom lane
>

Re: unsubscribe

[Tom Lane]

Danyelle Davis  writes:
> https://lists.postgresql.org/manage/

But note that that's only going to help if you've set up a "PG community
account", which up to now nobody has needed unless they wanted to edit
our wiki or work in our commitfest app, so it's a good bet that most
subscribers to our lists haven't got one.  The List-Unsubscribe link
is supposed to work without needing a community account.  It disturbs
me that Ryan says he's not seeing one in traffic from the list.
I certainly am getting one in all the mail I get from the new server.

I wonder whether there are complicating factors Ryan hasn't mentioned,
like maybe his traffic is getting forwarded from some other account
on some other email provider.  If so, maybe the List-Unsubscribe
header is getting dropped in forwarding?  That's a reach, but it's
hard to explain otherwise.

regards, tom lane

Re: unsubscribe

[Danyelle Davis]

https://lists.postgresql.org/manage/


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Nov 20, 2017 at 10:47 PM, Ryan  wrote:

> So my searches on the web all seemed to be somehow connecting me with the
> old majordomo2 system. I think that may have been the attempt that got me a
> "failed" automatic email back. One other attempt, I couldn't find a list
> with exactly this name and tried the pgus-general unsubscribe, which
> failed. The third was something yet more convoluted. My email headers do
> not contain the string "List-Unsubscribe", at least on this message.
> Regarding a link, I don't know which previous email has any such link. A
> couple of days ago, I was getting a daily digest. Tonight I came home to
> check email and see many dozens of messages. I have no idea what to look
> for where. I understand and sympathize with the frustration you all must
> feel with me. I'm sure you put crystal clear instructions somewhere about
> how to handle this, and if I were a more responsible person with fewer
> things to do on a daily basis, I would and should have paid more careful
> attention.
>
> On Mon, Nov 20, 2017 at 10:42 PM, Danyelle Davis 
> wrote:
>
>> have you tried the link provided in the previous email?
>>
>> On Mon, Nov 20, 2017 at 10:16 PM, Ryan  wrote:
>>
>>> Hi,
>>>
>>> All right, so not for lack of trying, I cannot figure out how to
>>> unsubscribe. I've tried three different things, but they've either been
>>> ineffective or result in me getting an automatic email that the attempt
>>> failed. Kindly help? I enjoyed my daily digest of PostgreSQL messages, but
>>> this has been a bit difficult to manage.
>>>
>>> Best regards.
>>>
>>>
>>> On Mon, Nov 20, 2017 at 9:37 PM, Danyelle Davis 
>>> wrote:
>>>

 On Mon, Nov 20, 2017 at 9:29 PM, Amila Jayasooriya <
 amilajayasoor...@gmail.com> wrote:

> Please unsubscribe me from the list.
>
> Thanks and Regards
>  Amila Jayasooriya
>
> On Tue, Nov 21, 2017 at 3:48 AM, Ibram Remzi 
> wrote:
>
>> Please unsubscribe me from the list.
>>
>> Please look at the listserv for options on how to unsub.  Yall are
 clogging the list with these.



 
  Virus-free.
 www.avast.com
 
 <#m_-3120866418184761144_m_-8088747671016791610_m_3944732850624955406_m_4396185798928146462_m_941694909827362166_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

>>>
>>>
>>
>

Re: unsubscribe

[Tom Lane]

Ryan  writes:
> All right, so not for lack of trying, I cannot figure out how to
> unsubscribe. I've tried three different things, but they've either been
> ineffective or result in me getting an automatic email that the attempt
> failed. Kindly help? I enjoyed my daily digest of PostgreSQL messages, but
> this has been a bit difficult to manage.

Well, you didn't say what you tried exactly, so it's hard to say why it
did not work.  But the way that I think has the fewest chances of going
wrong is to find the List-Unsubscribe header in any message you get from
the new list server, and visit the web page it links to, and confirm there
that you want to unsubscribe.

Depending on what mail software you use, you might have to use some
command like "View raw headers" or "View original message" to see
commonly-hidden headers like List-Unsubscribe.

(If you indeed did that, and it failed to work, our list admins
would definitely want to know about it; but they'd want a lot
more details than you've provided.)

regards, tom lane

Re: To all who wish to unsubscribe

[Carl Karsten]

On Mon, Nov 20, 2017 at 1:11 PM, Tom Lane  wrote:

> Vick Khera  writes:
> > Did the list software change? All my messages from here are not being
> properly auto-files by the filter I have set up.
>
> Yes - did you not see either of the "migration to pglister" messages?
> There's a summary of the changes at
>
> https://wiki.postgresql.org/wiki/PGLister_Announce
>
> Those looking to unsubscribe should also read that page.  Sending
> "unsubscribe" messages to the list will not accomplish anything
> except to annoy the rest of the list membership.
>


It might get you a video full of foul language  :)

https://youtu.be/eC9rmsI7dnw?t=1m42s


>
> regards, tom lane
>
>


-- 
Carl K

Re: unsubscribe

[Ryan]

Hi,

All right, so not for lack of trying, I cannot figure out how to
unsubscribe. I've tried three different things, but they've either been
ineffective or result in me getting an automatic email that the attempt
failed. Kindly help? I enjoyed my daily digest of PostgreSQL messages, but
this has been a bit difficult to manage.

Best regards.

On Mon, Nov 20, 2017 at 9:37 PM, Danyelle Davis  wrote:

>
> On Mon, Nov 20, 2017 at 9:29 PM, Amila Jayasooriya <
> amilajayasoor...@gmail.com> wrote:
>
>> Please unsubscribe me from the list.
>>
>> Thanks and Regards
>>  Amila Jayasooriya
>>
>> On Tue, Nov 21, 2017 at 3:48 AM, Ibram Remzi 
>> wrote:
>>
>>> Please unsubscribe me from the list.
>>>
>>> Please look at the listserv for options on how to unsub.  Yall are
> clogging the list with these.
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_4396185798928146462_m_941694909827362166_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: To all who wish to unsubscribe

[Gavin Flower]

On 21/11/17 09:20, Magnus Hagander wrote:
On Mon, Nov 20, 2017 at 9:07 PM, Joshua D. Drake > wrote:


On 11/20/2017 12:03 PM, Tom Lane wrote:

Unfortunately, the removal of the footer is a feature not a bug.
In order to be DKIM-compatible and thus help avoid becoming
classified
as spammers, we can't mangle message content anymore, just like we
can't mangle the Subject: line.


Ugh, o.k.

In principle, the List-Unsubscribe: headers that are now
included in
mailing list headers allow MUAs to offer convenient unsubscribe
buttons.  Not sure how many of the people who are complaining use
mail agents that don't handle that.


I use Thunderbird which I imagine most people on the lists are
using. I can't find where these would work to unsubscribe.


Not even remotely. People use gmail. See 
https://blog.hagander.net/mail-agents-in-the-postgresql-community-233/ 
.


And gmail does automatically show an unsubscribe link on these mails. 
See attached screenshot for the mail from Jonathan earlier today as an 
example.


--
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 


Not everyone uses gmail!

I would never recommend it use for either for personal or business use - 
as Googol scans it for commercial [purposes.



Cheers,
Gavin

Re: To all who wish to unsubscribe

[Steve Atkins]

> On Nov 20, 2017, at 2:18 PM, Piotr Stefaniak  
> wrote:
> 
> On 2017-11-20 21:03, Tom Lane wrote:
>> "Joshua D. Drake"  writes:
>>> On 11/20/2017 11:40 AM, Magnus Hagander wrote:
>>> One thing I would note is that there is no longer a footer that
>>> tells people what to do if they want to unsubscribe. Perhaps one 
>>> thing that could be done is a header (for a temporary time period)
>>> that says:
>>> The mailing list software of Postgresql.org has changed. Please see
>>> this page on instructions on how to manage your subscription and
>>> filters. And then after the temporary time period that becomes a
>>> footer?
>> 
>> Unfortunately, the removal of the footer is a feature not a bug. In
>> order to be DKIM-compatible and thus help avoid becoming classified 
>> as spammers, we can't mangle message content anymore, just like we 
>> can't mangle the Subject: line.
> I don't miss the footers, but see RFC 6376, "5.3.1. Body Length Limits". 
> Two fragments quoted are copied below:

That's poor practice, for several reasons - replay attacks with added content
and it being an extremely rare practice that's likely to trigger bugs in DKIM
validation are two. The latter is the much bigger deal.

It also doesn't help much for most MIME encoded mail (including base64
encoded plain text, like the mail I'm replying to).

Pretending those paragraphs aren't there is the right thing to do.

Cheers,
  Steve



> 
>> A body length count MAY be specified to limit the signature 
>> calculation to an initial prefix of the body text, measured in 
>> octets. If the body length count is not specified, the entire message
>> body is signed.
> 
>> INFORMATIVE RATIONALE: This capability is provided because it is very
>> common for mailing lists to add trailers to messages (e.g., 
>> instructions on how to get off the list). Until those messages are
>> also signed, the body length count is a useful tool for the Verifier
>> since it can, as a matter of policy, accept messages having valid
>> signatures with extraneous data.

Re: Procmail recipe for new setup

[Stephen Frost]

Greetings Rich, all,

* Rich Shepard (rshep...@appl-ecosys.com) wrote:
> On Mon, 20 Nov 2017, Steve Litt wrote:
> 
> >The following procmail recipe works for me:
> >
> >===
> >:0:
> >* ^(To|Cc).*pgsql-gene...@postgresql.org
> >.Postgres/
> >===
> 
> Hi, Steve!
> 
>   Here's an alternative recipe:
> 
> :0:
> * ^TO_.*pgsql-general@(lists\.)?postgresql.org
> POSTGRES
> 
> The TO_(with no space after it) captures CCs too, and the regex (lists\.)?
> says accept 0 (zero) or 1 (one) of the lists prefix. I use mbox not maildir
> so POSTGRES is the name of the file in ~/mail/.

Yes, this is a good recipe to use, particularly as we will be,
eventually, encouraging more use of the 'lists.postgresql.org'
subdomain in the future, and email is already being accepted for the
lists through it.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: Procmail recipe for new setup

[Stephen Frost]

Greetings Piotr,

* Piotr Stefaniak (postg...@piotr-stefaniak.me) wrote:
> On 2017-11-20 23:10, Steve Litt wrote:
> 
> > The following procmail recipe works for me:
> 
> I use this:
> 
> :0
> * ^List-Id: \/.*
> {
>  :0
>  * $MATCH ?? [<]+\/.*[^>]+
>  $MATCH/
> 
>  :0
>  $MATCH/
> }

I would caution against using this kind of expansion as it may allow
malicious attackers to generate all kinds of not-nice stuff in your mail
directories.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: Procmail recipe for new setup

[Piotr Stefaniak]

On 2017-11-20 23:10, Steve Litt wrote:

> The following procmail recipe works for me:

I use this:

:0
* ^List-Id: \/.*
{
 :0
 * $MATCH ?? [<]+\/.*[^>]+
 $MATCH/

 :0
 $MATCH/
}

Re: To all who wish to unsubscribe

[Piotr Stefaniak]

On 2017-11-20 21:03, Tom Lane wrote:
> "Joshua D. Drake"  writes:
>> On 11/20/2017 11:40 AM, Magnus Hagander wrote:
>> One thing I would note is that there is no longer a footer that
>> tells people what to do if they want to unsubscribe. Perhaps one 
>> thing that could be done is a header (for a temporary time period)
>> that says:
>> The mailing list software of Postgresql.org has changed. Please see
>> this page on instructions on how to manage your subscription and
>> filters. And then after the temporary time period that becomes a
>> footer?
> 
> Unfortunately, the removal of the footer is a feature not a bug. In
> order to be DKIM-compatible and thus help avoid becoming classified 
> as spammers, we can't mangle message content anymore, just like we 
> can't mangle the Subject: line.
I don't miss the footers, but see RFC 6376, "5.3.1. Body Length Limits". 
Two fragments quoted are copied below:

> A body length count MAY be specified to limit the signature 
> calculation to an initial prefix of the body text, measured in 
> octets. If the body length count is not specified, the entire message
> body is signed.

> INFORMATIVE RATIONALE: This capability is provided because it is very
> common for mailing lists to add trailers to messages (e.g., 
> instructions on how to get off the list). Until those messages are
> also signed, the body length count is a useful tool for the Verifier
> since it can, as a matter of policy, accept messages having valid
> signatures with extraneous data.

Re: Procmail recipe for new setup

[Joshua D. Drake]

On 11/20/2017 02:10 PM, Steve Litt wrote:

Hi all,

The following procmail recipe works for me:

===
:0:
* ^(To|Cc).*pgsql-gene...@postgresql.org
.Postgres/
===


You may want to use TO ... See here:

https://www.mhonarc.org/archive/html/procmail/1998-04/msg00093.html


Thanks,

JD

--

Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

Re: Procmail recipe for new setup

[Rich Shepard]

On Mon, 20 Nov 2017, Steve Litt wrote:


The following procmail recipe works for me:

===
:0:
* ^(To|Cc).*pgsql-gene...@postgresql.org
.Postgres/
===


Hi, Steve!

  Here's an alternative recipe:

:0:
* ^TO_.*pgsql-general@(lists\.)?postgresql.org
POSTGRES

The TO_(with no space after it) captures CCs too, and the regex (lists\.)?
says accept 0 (zero) or 1 (one) of the lists prefix. I use mbox not maildir
so POSTGRES is the name of the file in ~/mail/.

Regards,

Rich

Test 501, please don't reply

[Steve Litt]

-- 
SteveT

Steve Litt 
November 2017 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust

Re: To all who wish to unsubscribe

[Stephen Frost]

Greetings,

* Tom Lane (t...@sss.pgh.pa.us) wrote:
> In principle, the List-Unsubscribe: headers that are now included in
> mailing list headers allow MUAs to offer convenient unsubscribe
> buttons.  Not sure how many of the people who are complaining use
> mail agents that don't handle that.

Quite a few people have been using that capability with their MUAs very
successfully.  Magnus just mentioned we've had some 200 or so individual
unsubscribes done that way (note that wasn't distinct addresses but
unsubscribes across all lists).

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: To all who wish to unsubscribe

[Daniel Verite]

Magnus Hagander wrote:

> So do you have any suggestions for actually fixing that? Given that we have
> more lists to migrate, if you can figure out a way to make those changes
> without peoples filters not matching, we'd be happy to hear it..

I guess it's a bit late at this point, but in theory keeping the same
List-Id headers as before may help with how many people have to
change their filters.
Using lists.postgresql.org as the new domain was explained
in the announce, but it's not clear why List-Id had to follow
the other List-* fields.
Unless it was the reason mentioned in the last sentence below.

Quoting RFC-2919:

4. Persistence of List Identifiers

   Although the list identifier MAY be changed by the mailing list
   administrator this is not desirable.  (Note that there is no
   disadvantage to changing the description portion of the List-Id
   header.)  A MUA may not recognize the change to the list identifier
   because the MUA SHOULD treat a different list identifier as a
   different list.  As such the mailing list administrator SHOULD avoid
   changing the list identifier even when the host serving the list
   changes.  On the other hand, transitioning from an informal
   unmanaged-list-id-namespace to a domain namespace is an
   acceptable reason to change the list identifier.


Best regards,
-- 
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

Re: [MESSAGE PUBLICITAIRE- VIGILANCE] RE: Unsubscribe

[Keith]

The link to this simple form below is right at the top of the other link
where it says "How to Subscribe or Unsubscribe, Fill out this form."

https://www.postgresql.org/community/lists/subscribe/





On Mon, Nov 20, 2017 at 4:25 PM, Bennett Hitchcox-Lain 
wrote:

> Yeah, that link is pretty much useless... The go to this other link for
> what you want, but then go to another link, and login, then go to. Why
> can I just put in my email and click unsubscribe.
>
>
> On Mon, Nov 20, 2017, 11:11 AM Jaimi McEntire 
> wrote:
>
>> To all wanting to unsubscribe. Go here to do it and quit flooding our
>> mail boxes:
>>
>>
>>
>> https://www.postgresql.org/list/
>>
>>
>>
>>
>> --
>> *From:* Natacha.Brosius 
>> *Sent:* Monday, November 20, 2017 1:08:41 PM
>> *To:* Vadlamudi, Chandhra
>> *Cc:* pgsql-ad...@postgresql.org; pgsql-general@lists.postgresql.org;
>> pgsql-gene...@postgresql.org
>> *Subject:* Re: [MESSAGE PUBLICITAIRE- VIGILANCE] RE: Unsubscribe
>>
>> Hi,
>>
>> Please unsubscribe me to all PostgreSQL mailing lists.
>>
>>
>>
>>  Thanks and best regard
>>
>>
>> Natacha Brosius
>>
>> Le 20 nov. 2017 à 20:02, Vadlamudi, Chandhra > blueshieldca.com> a écrit :
>>
>> I tried multiple ways to remove myself from groups but no luck.
>>
>> Please remove me from groups and communication lists.
>>
>>
>>
>> *From:* MARTIN PAREDES [mailto:map...@hotmail.com ]
>> *Sent:* Monday, November 20, 2017 10:58 AM
>> *To:* pgsql-ad...@postgresql.org; pgsql-general@lists.postgresql.org;
>> pgsql-gene...@postgresql.org
>> *Subject:* Unsubscribe
>>
>>
>>
>> ** BSCA security warning: Do not click links or trust the content unless
>> you expected this email and trust the sender – This email originated
>> outside of Blue Shield. **
>>
>> Please unsubscribe me to all PostgreSQL mailing lists.
>>
>>
>>
>>  Thanks and best regards
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>   ING. MARTIN PAREDES DOMINGUEZ
>>   *MAPASAC & MAPASOFT   ERP-SOFTWARE-DEVELOPER*
>>   FREELANCE SENIOR DEVELOPER
>>   MAPASAC SISTEMAS ADMINISTRATIVOS COMERCIALES
>>   General Escobedo, N.L., Mexico
>>   Tlf: *8182-0393-48*   map...@hotmail.com
>>
>>
>>
>>
>>

Re: Migration to PGLister - After

[Stephen Frost]

Mike,

* Michael Nolan (htf...@gmail.com) wrote:
> On Mon, Nov 20, 2017 at 9:45 AM, Stephen Frost  wrote:
> > This list has now been migrated to new mailing list software known as
> > 'PGLister'.  This migration will impact all users of this mailing list
> > in one way or another.
> 
> Is there more information available about PGLister somewhere, ie, is this a
> list package that other people running mailing lists might be able to use?
> A net search for "PGLister" doesn't find much yet.

It's open source and we'll open the git tree for it soon, but it's tied
into our community authentication system, so it's not like it's
something that would be easy to plug-n-play elsewhere.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: [MESSAGE PUBLICITAIRE- VIGILANCE] RE: Unsubscribe

[Bennett Hitchcox-Lain]

Yeah, that link is pretty much useless... The go to this other link for
what you want, but then go to another link, and login, then go to. Why
can I just put in my email and click unsubscribe.

On Mon, Nov 20, 2017, 11:11 AM Jaimi McEntire 
wrote:

> To all wanting to unsubscribe. Go here to do it and quit flooding our mail
> boxes:
>
>
>
> https://www.postgresql.org/list/
>
>
>
>
> --
> *From:* Natacha.Brosius 
> *Sent:* Monday, November 20, 2017 1:08:41 PM
> *To:* Vadlamudi, Chandhra
> *Cc:* pgsql-ad...@postgresql.org; pgsql-general@lists.postgresql.org;
> pgsql-gene...@postgresql.org
> *Subject:* Re: [MESSAGE PUBLICITAIRE- VIGILANCE] RE: Unsubscribe
>
> Hi,
>
> Please unsubscribe me to all PostgreSQL mailing lists.
>
>
>
>  Thanks and best regard
>
>
> Natacha Brosius
>
> Le 20 nov. 2017 à 20:02, Vadlamudi, Chandhra <
> chandhra.vadlam...@blueshieldca.com> a écrit :
>
> I tried multiple ways to remove myself from groups but no luck.
>
> Please remove me from groups and communication lists.
>
>
>
> *From:* MARTIN PAREDES [mailto:map...@hotmail.com ]
> *Sent:* Monday, November 20, 2017 10:58 AM
> *To:* pgsql-ad...@postgresql.org; pgsql-general@lists.postgresql.org;
> pgsql-gene...@postgresql.org
> *Subject:* Unsubscribe
>
>
>
> ** BSCA security warning: Do not click links or trust the content unless
> you expected this email and trust the sender – This email originated
> outside of Blue Shield. **
>
> Please unsubscribe me to all PostgreSQL mailing lists.
>
>
>
>  Thanks and best regards
>
>
>
>
>
>
>
>
>
>
>
>   ING. MARTIN PAREDES DOMINGUEZ
>   *MAPASAC & MAPASOFT   ERP-SOFTWARE-DEVELOPER*
>   FREELANCE SENIOR DEVELOPER
>   MAPASAC SISTEMAS ADMINISTRATIVOS COMERCIALES
>   General Escobedo, N.L., Mexico
>   Tlf: *8182-0393-48*   map...@hotmail.com
>
>
>
>
>

Re: Migration to PGLister - After

[Rob Sargent]

Kinda looking like you should have unsubscribed everybody and those of 
us that would miss the feed would re-connect.



On 11/20/2017 02:09 PM, Magnus Hagander wrote:
On Mon, Nov 20, 2017 at 9:31 PM, Michael Nolan > wrote:




On Mon, Nov 20, 2017 at 9:45 AM, Stephen Frost > wrote:


This list has now been migrated to new mailing list software
known as
'PGLister'.  This migration will impact all users of this
mailing list
in one way or another.


Is there more information available about PGLister somewhere, ie,
is this a list package that other people running mailing lists
might be able to use?  A net search for "PGLister" doesn't find
much yet.


Hi!

Please track the thread at 
https://www.postgresql.org/message-id/CABUevEw7Vs9Hpe-9dRWPwXDa4sPuE71BDNk2X8_UOQ%3Dhvf1tnA%40mail.gmail.com 
for information on that. TL/DR version is that right now it's in a 
closed repo, but it's scheduled to be opened as soon as somebody has 
had the time to go through it and make sure we're not accidentally 
leaking something that shouldn't be leaked.


--
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

Unsubscribe

[Jeferson Kasper]

Please unsubscribe me from all PostgreSQL mailing lists

Unsubscribe

[Juan Camilo Marín]

Please unsubscribe me from all PostgreSQL mailing lists

Re: To all who wish to unsubscribe

[Magnus Hagander]

On Mon, Nov 20, 2017 at 9:58 PM, John R Pierce  wrote:

> On 11/20/2017 12:49 PM, John R Pierce wrote:
>
>> Sigh, not surprised about gmail, its amazing how many .com's and .org's
>> use it now.  I'm not at ALL a fan of how the web client handles a bunch of
>> stuff like replies, & hiding your own messages from yourself.
>>
>
> oh and my biggest gripe, gmail seems to ignore the References header AND
> replies often don't seem to have that header, so if you're using a
> traditional threaded email client like Thunderbird, replies from gmail
> users don't seem to get threaded correctly and show up as new threads.
> gmail itself seems to thread purely based on Subject.


If people just use the reply feature in gmail it does set the References
header properly. It breaks threads intentionally if people edit the subject
(which you have to click a separate button to do). But if people hit the
reply buttons, the headers are correct. (I did quite a bit of analysis on
that when building the new list archives system a while ago). Many other
MUAs have much bigger problems -- but even Outlook and the Microsoft web
based ones do a decent job today. They certainly didn't use to do that...

And it's internal threading is way more complex than just using subject.
But the inability to override how it does that is definitely one of my
biggest gripes about gmail. But that only affects the user of gmail, not
the others on the list. (Unlike what broken references headers would do)

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

Re: To all who wish to unsubscribe

[Alvaro Herrera]

Edson Carlos Ericksson Richter wrote:

> I've been affected also, in a minor way, because I used to receive digest  2
> or 3 times a day, and now I'm receiving every e-mail again.
> This is, at least, annoying.
> would be better to keep the user options when migrating from one software to
> another.

Digests as a feature were considered for pglister and ultimately
rejected.  There is no value in digest nowadays: if you don't want the
emails to show up in your inbox individually, filter them to another
folder.  They impact to the rest of the subscribers too, when those
subscribed to the digest reply to it breaking all threads and quoting.
Also, they would be more work and resources to implement.

-- 
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: To all who wish to unsubscribe

[John R Pierce]

On 11/20/2017 12:49 PM, John R Pierce wrote:
Sigh, not surprised about gmail, its amazing how many .com's and 
.org's use it now.  I'm not at ALL a fan of how the web client handles 
a bunch of stuff like replies, & hiding your own messages from yourself. 


oh and my biggest gripe, gmail seems to ignore the References header AND 
replies often don't seem to have that header, so if you're using a 
traditional threaded email client like Thunderbird, replies from gmail 
users don't seem to get threaded correctly and show up as new 
threads.    gmail itself seems to thread purely based on Subject.



--
john r pierce, recycling bits in santa cruz

Re: To all who wish to unsubscribe

[Joshua D. Drake]

On 11/20/2017 12:20 PM, Magnus Hagander wrote:
On Mon, Nov 20, 2017 at 9:07 PM, Joshua D. Drake > wrote:


Not even remotely. People use gmail. See 
https://blog.hagander.net/mail-agents-in-the-postgresql-community-233/ 
.


And gmail does automatically show an unsubscribe link on these mails. 
See attached screenshot for the mail from Jonathan earlier today as an 
example.


Well Thunderbird is #2 ;) but yes I am aware that Gmail has the 
unsubscribe feature.


Thanks!

JD


--
Unless otherwise stated, opinions are my own.

Re: To all who wish to unsubscribe

[Edson Carlos Ericksson Richter]

Em 20/11/2017 18:07, Joshua D. Drake escreveu:

On 11/20/2017 12:03 PM, Tom Lane wrote:

Unfortunately, the removal of the footer is a feature not a bug.
In order to be DKIM-compatible and thus help avoid becoming classified
as spammers, we can't mangle message content anymore, just like we
can't mangle the Subject: line.


Ugh, o.k.

In principle, the List-Unsubscribe: headers that are now included in
mailing list headers allow MUAs to offer convenient unsubscribe
buttons.  Not sure how many of the people who are complaining use
mail agents that don't handle that.


I use Thunderbird which I imagine most people on the lists are using. 
I can't find where these would work to unsubscribe.


Well this is a pain for everyone it seems.

JD

Seems that Thunderbird (latest stable version) doesn't understand the 
unsubscribe header.

Or, perhaps, it is wrong.

Regards,

Edson

RE: To all who wish to unsubscribe

[Leavitt, Ted]

Vick,
  I thought it was just me.  Yes, the sender changed:

pgsql-general-ow...@postgresql.org 
-> pgsql-general@lists.postgresql.org

I have updated my rules accordingly.

-Ted

From: Vick Khera [mailto:vi...@khera.org]
Sent: Monday, November 20, 2017 10:58 AM
To: pgsql-general@lists.postgresql.org
Subject: Re: To all who wish to unsubscribe

Did the list software change? All my messages from here are not being properly 
auto-files by the filter I have set up.

On Nov 20, 2017, at 13:48, Martin Fernau 
> wrote:
PLS unsubscribe via 
https://lists.postgresql.org/manage/

Today I received dozens of unsubscribe mails, spamming my mail account :-)

thx
Am 20.11.2017 um 19:42 schrieb Ramalingam, Sankarakumar:


Thank you!

Kumar Ramalingam

From: Zacher, Stacy [mailto:szac...@mcw.edu]
Sent: Monday, November 20, 2017 12:56 PM
To: 
pgsql-general@lists.postgresql.org
Subject: unsubscribe



The information contained in this e-mail and in any attachments is intended 
only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, this 
information by persons or entities other than the intended recipient is 
prohibited. This message has been scanned for known computer viruses.

--

This email was Malware checked by UTM 9. 
http://www.sophos.com



--

FERNAUSOFT GmbH

Gartenstraße 42 - 37269 Eschwege



Telefon (0 56 51) 95 99-0

Telefax (0 56 51) 95 99-90



eMail martin.fer...@fernausoft.de

Internet 
http://www.fernausoft.de



Handelsregister Eschwege, HRB 1585

Geschäftsführer: Axel Fernau, Ulrich Fernau, Martin Fernau

Steuernummer 025 233 00041

USt-ID-Nr. DE 178 554 622

Re: Unsubscribe

[CLAUDIO LIVIO CANDIANI]

Please unsubscribe me from all PostgreSQL mailing lists.
Best regards,
Claudio

2017-11-20 18:07 GMT-02:00 Marek Przywara :

> Please unsubscribe me from all PostgreSQL mailing lists.
>
> Best regards,
>
> Marek Przywara
>

unsubcribe

[Ricardo Hiroshi Sakamoto]

 unsubcribe ricardohiroshisakam...@yahoo.com.brRicardo Hiroshi Sakamoto

Re: Migration to PGLister - After

[Tom Lane]

Ben Coleman  writes:
> On 11/20/2017 09:45 AM, Stephen Frost wrote:
>> This list has now been migrated to new mailing list software known as
>> 'PGLister'.  This migration will impact all users of this mailing list
>> in one way or another.

> I note the conspicuous absence of pgsql-annou...@postgresql.org in the
> lists the Before email was sent to.  Can I assume that that list
> continues under the old regime?

It's scheduled to be migrated next week.

regards, tom lane

Re: Migration to PGLister - After

[Ben Coleman]

On 11/20/2017 09:45 AM, Stephen Frost wrote:
> Greetings!
> 
> This list has now been migrated to new mailing list software known as
> 'PGLister'.  This migration will impact all users of this mailing list
> in one way or another.

I note the conspicuous absence of pgsql-annou...@postgresql.org in the
lists the Before email was sent to.  Can I assume that that list
continues under the old regime?

Ben
-- 
Ben Coleman  
CTO, Accelerated Design, Inc.
(678) 337-8899



signature.asc
Description: OpenPGP digital signature

Re: To all who wish to unsubscribe

[Magnus Hagander]

On Mon, Nov 20, 2017 at 9:12 PM, Tom Lane  wrote:

> Magnus Hagander  writes:
> > Right. This is why you can send an emtil to say
> > pgsql-general-unsubscr...@lists.postgresql.org to unsubscribe.
>
> Oh?  First I've heard of that, and I do not see it mentioned on the
> PGLister_Announce wiki page.  It definitely should be.
>

Yeah, that's clearly an oversight on the wiki page.

We also try to trap the word unsubscribe in the beginning of the body to
moderate those. But that one misses a lot of combinations, because we don't
want to get stuck in the same situation as the old mj2 which captured way
too much.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

Re: To all who wish to unsubscribe

[Magnus Hagander]

On Mon, Nov 20, 2017 at 9:07 PM, Joshua D. Drake 
wrote:

> On 11/20/2017 12:03 PM, Tom Lane wrote:
>
>> Unfortunately, the removal of the footer is a feature not a bug.
>> In order to be DKIM-compatible and thus help avoid becoming classified
>> as spammers, we can't mangle message content anymore, just like we
>> can't mangle the Subject: line.
>>
>
> Ugh, o.k.
>
>> In principle, the List-Unsubscribe: headers that are now included in
>> mailing list headers allow MUAs to offer convenient unsubscribe
>> buttons.  Not sure how many of the people who are complaining use
>> mail agents that don't handle that.
>>
>
> I use Thunderbird which I imagine most people on the lists are using. I
> can't find where these would work to unsubscribe.
>

Not even remotely. People use gmail. See https://blog.hagander.net/
mail-agents-in-the-postgresql-community-233/.

And gmail does automatically show an unsubscribe link on these mails. See
attached screenshot for the mail from Jonathan earlier today as an example.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

Re: To all who wish to unsubscribe

[John R Pierce]

On 11/20/2017 12:07 PM, Joshua D. Drake wrote:
I use Thunderbird which I imagine most people on the lists are using. 
I can't find where these would work to unsubscribe. 


In Thunderbird, ctrl-U shows the full headers, but the List-Unsubscribe 
links are NOT shown as hotlinks, so you have to copy/paste them to a 
browser.




--
john r pierce, recycling bits in santa cruz

Re: To all who wish to unsubscribe

[John R Pierce]

On 11/20/2017 11:44 AM, Mengxuan Xia wrote:

A common feature in modern Email client is to allow users to unsubscribe in one line. 
This works by sending a email titled "unsubscribe" to the listserv, which most 
listserv these days are able to understand and unsubscribe the user.



thats a feature of many email list SERVERS, not the email clients.  
Mailman in particular looks for the major command keywords in the first 
few lines of the email, and will respond to them, even if they are sent 
to the regular list address instead of the command address.




--
john r pierce, recycling bits in santa cruz

Re: To all who wish to unsubscribe

[John R Pierce]

On 11/20/2017 11:45 AM, Joshua D. Drake wrote:
Perhaps one thing that could be done is a header (for a temporary time 
period) that says:


The mailing list software of Postgresql.org has changed. Please see 
this page on instructions on how to manage your subscription and filters. 


vast majority of users never see the full headers, they just see From, 
To, Date, Subject, and everything else is hidden.  on a phone or a web 
mail system like gmail, its very hard to see that stuff.



--
john r pierce, recycling bits in santa cruz

Unsubscribe

[Marek Przywara]

Please unsubscribe me from all PostgreSQL mailing lists.

Best regards,

Marek Przywara

Re: To all who wish to unsubscribe

[Joshua D. Drake]

On 11/20/2017 12:03 PM, Tom Lane wrote:

Unfortunately, the removal of the footer is a feature not a bug.
In order to be DKIM-compatible and thus help avoid becoming classified
as spammers, we can't mangle message content anymore, just like we
can't mangle the Subject: line.


Ugh, o.k.

In principle, the List-Unsubscribe: headers that are now included in
mailing list headers allow MUAs to offer convenient unsubscribe
buttons.  Not sure how many of the people who are complaining use
mail agents that don't handle that.


I use Thunderbird which I imagine most people on the lists are using. I 
can't find where these would work to unsubscribe.


Well this is a pain for everyone it seems.

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

Re: To all who wish to unsubscribe

[Tom Lane]

"Joshua D. Drake"  writes:
> On 11/20/2017 11:40 AM, Magnus Hagander wrote:
> One thing I would note is that there is no longer a footer 
> that tells people what to do if they want to unsubscribe. Perhaps one 
> thing that could be done is a header (for a temporary time period) that 
> says:
> The mailing list software of Postgresql.org has changed. Please see this 
> page on instructions on how to manage your subscription and filters.
> And then after the temporary time period that becomes a footer?

Unfortunately, the removal of the footer is a feature not a bug.
In order to be DKIM-compatible and thus help avoid becoming classified
as spammers, we can't mangle message content anymore, just like we
can't mangle the Subject: line.

In principle, the List-Unsubscribe: headers that are now included in
mailing list headers allow MUAs to offer convenient unsubscribe
buttons.  Not sure how many of the people who are complaining use
mail agents that don't handle that.

regards, tom lane

Re: To all who wish to unsubscribe

[Joshua D. Drake]

On 11/20/2017 11:45 AM, Joshua D. Drake wrote:


So do you have any suggestions for actually fixing that? Given that 
we have more lists to migrate, if you can figure out a way to make 
those changes without peoples filters not matching, we'd be happy to 
hear it..


I was thinking about that. I was actually surprised at how many people 
this affected. It only affected one filter for me so it wasn't that 
big of a deal. One thing I would note is that there is no longer a 
footer that tells people what to do if they want to unsubscribe. 
Perhaps one thing that could be done is a header (for a temporary time 
period) that says:


The mailing list software of Postgresql.org has changed. Please see 
this page on instructions on how to manage your subscription and filters.


And then after the temporary time period that becomes a footer?


I would also note that removing the ability to unsubscribe in an 
standard fashion is rather user unfriendly. Although many spammers 
require that you go to a website, we rarely (I have never seen it) have 
to log in to unsubscribe from a list. If you add that most people and 
especially people that are on this list are going to be used to using 
email to subscribe/unsubscribe...


Thanks,

JD



Thanks,

JD



--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

Re: To all who wish to unsubscribe

[Joshua D. Drake]

On 11/20/2017 11:40 AM, Magnus Hagander wrote:


https://wiki.postgresql.org/wiki/PGLister_Announce


Those looking to unsubscribe should also read that page.  Sending
"unsubscribe" messages to the list will not accomplish anything
except to annoy the rest of the list membership.


This is true but I would suggest it was a flaw in the migration
not the user wondering why they are currently getting spammed
because their filters no longer work.


So do you have any suggestions for actually fixing that? Given that we 
have more lists to migrate, if you can figure out a way to make those 
changes without peoples filters not matching, we'd be happy to hear it..


I was thinking about that. I was actually surprised at how many people 
this affected. It only affected one filter for me so it wasn't that big 
of a deal. One thing I would note is that there is no longer a footer 
that tells people what to do if they want to unsubscribe. Perhaps one 
thing that could be done is a header (for a temporary time period) that 
says:


The mailing list software of Postgresql.org has changed. Please see this 
page on instructions on how to manage your subscription and filters.


And then after the temporary time period that becomes a footer?

Thanks,

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

RE: To all who wish to unsubscribe

[Mengxuan Xia]

A common feature in modern Email client is to allow users to unsubscribe in one 
line. This works by sending a email titled "unsubscribe" to the listserv, which 
most listserv these days are able to understand and unsubscribe the user.

-Original Message-
From: Alban Hertroys [mailto:haram...@gmail.com] 
Sent: November 20, 2017 2:41 PM
To: Tom Lane 
Cc: Vick Khera ; pgsql-general@lists.postgresql.org
Subject: Re: To all who wish to unsubscribe


> On 20 Nov 2017, at 20:11, Tom Lane  wrote:
> 
> Those looking to unsubscribe should also read that page.  Sending 
> "unsubscribe" messages to the list will not accomplish anything except 
> to annoy the rest of the list membership.

I imagine that some people might think along the lines of: "Annoy them enough, 
and someone will do something about it".

And they could be right too, as no doubt some subscribers might figure that 
sending an auto-reply to any unsubscribe message to the list to the person in 
question - perhaps with an explanation of how to unsubscribe properly - would 
make that person use the correct method for unsubscribing rather sooner than 
later.

Please, as tempting as that sounds, be gentle to the list server and do not do 
that.

Alban Hertroys
--
If you can't see the forest for the trees, cut the trees and you'll find there 
is no forest.

unsubscribe

[Ronny Abraham]

Best regards,
Ronny Abraham

From: Pedro Antonio [mailto:pedro.osp...@gmail.com]
Sent: Monday, November 20, 2017 1:22 PM
To: Rasha Osman
Cc: pgsql-general@lists.postgresql.org
Subject: unsubscribe


El 20/11/2017 1:20 p.m., "Rasha Osman" 
> escribió:




From: Yang, Xiaoguang >
Sent: 20 November 2017 18:16
To: 
pgsql-general@lists.postgresql.org
Subject: unsubscribe






This email is non-binding, is subject to contract, and neither Kulicke and 
Soffa Industries, Inc. nor its subsidiaries (each and collectively “K”) shall 
have any obligation to you to consummate the transactions herein or to enter 
into any agreement, other than in accordance with the terms and conditions of a 
definitive agreement if and when negotiated, finalized and executed between the 
parties. This email and all its contents are protected by International and 
United States copyright laws. Any reproduction or use of all or any part of 
this email without the express written consent of K is prohibited.

Re: To all who wish to unsubscribe

[Joshua D. Drake]

On 11/20/2017 11:11 AM, Tom Lane wrote:

Vick Khera  writes:

Did the list software change? All my messages from here are not being properly 
auto-files by the filter I have set up.

Yes - did you not see either of the "migration to pglister" messages?
There's a summary of the changes at


I certainly didn't. It is rather difficult for people with day lives 
that do not revolve around postgresql.org to keep up with the large 
amount of traffic that comes from the lists.




https://wiki.postgresql.org/wiki/PGLister_Announce

Those looking to unsubscribe should also read that page.  Sending
"unsubscribe" messages to the list will not accomplish anything
except to annoy the rest of the list membership.


This is true but I would suggest it was a flaw in the migration not the 
user wondering why they are currently getting spammed because their 
filters no longer work.


Thanks,

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

Re: To all who wish to unsubscribe

[Tom Lane]

Vick Khera  writes:
> Did the list software change? All my messages from here are not being 
> properly auto-files by the filter I have set up. 

Yes - did you not see either of the "migration to pglister" messages?
There's a summary of the changes at

https://wiki.postgresql.org/wiki/PGLister_Announce

Those looking to unsubscribe should also read that page.  Sending
"unsubscribe" messages to the list will not accomplish anything
except to annoy the rest of the list membership.

regards, tom lane

Re: Unsubscribe

[Haluk Durmus]

 Do it yourself guys ...
Am Montag, 20. November 2017, 19:58:05 MEZ hat MARTIN PAREDES 
 Folgendes geschrieben:  
 
  

Please unsubscribe me to all PostgreSQL mailing lists.
 Thanks and best regards   
|  
 
   |  |
|  

   |   ING. MARTIN PAREDES DOMINGUEZ
  MAPASAC & MAPASOFT   ERP-SOFTWARE-DEVELOPER
  FREELANCE SENIOR DEVELOPER
  MAPASAC SISTEMAS ADMINISTRATIVOS COMERCIALES
  General Escobedo, N.L., Mexico
  Tlf:8182-0393-48  map...@hotmail.com
   |




 
  

RE: Unsubscribe

[Vadlamudi, Chandhra]

I tried multiple ways to remove myself from groups but no luck.
Please remove me from groups and communication lists.

From: MARTIN PAREDES [mailto:map...@hotmail.com]
Sent: Monday, November 20, 2017 10:58 AM
To: pgsql-ad...@postgresql.org; pgsql-general@lists.postgresql.org; 
pgsql-gene...@postgresql.org
Subject: Unsubscribe

** BSCA security warning: Do not click links or trust the content unless you 
expected this email and trust the sender - This email originated outside of 
Blue Shield. **
Please unsubscribe me to all PostgreSQL mailing lists.

 Thanks and best regards







[http://www.firmasdecorreo.com/dyndata/images/firmasdecorreo.com-2013-11-09_17:06:25_8847-02.jpg]


  ING. MARTIN PAREDES DOMINGUEZ
  MAPASAC & MAPASOFT   ERP-SOFTWARE-DEVELOPER
  FREELANCE SENIOR DEVELOPER
  MAPASAC SISTEMAS ADMINISTRATIVOS COMERCIALES
  General Escobedo, N.L., Mexico
  Tlf: 8182-0393-48   map...@hotmail.com

Re: [GENERAL] postmaster deadlock while logging after syslogger exited

[David Pacheco]

Responding to several points below.

Tom Lane wrote:
> David's report isn't too clear: did the syslogger process actually run
> out of memory and exit of its own volition after an ENOMEM, or did it get
> killed by the dreaded OOM killer?  In either case, it's unclear whether
> it was really using an excessive amount of memory.  We have not heard
> reports suggesting a memory leak in the syslogger, but maybe there is
> one under unusual circumstances?

I'm running on illumos, where there is no OOM killer.

I expect what happened is that the syslogger process attempted to allocate
memory, failed because the system was low, and explicitly exited.  That's
consistent with an exited process, no core file generated, and the "FATAL"
"out
of memory" entries in the log I posted.

Of course, that doesn't mean the syslogger was using much memory.  It means
only
that it attempted to allocate any memory in a context where it could not
handle
failing.


Andres Freund wrote:
> I'm somewhat inclined to say that one has to live with this if the
> system is so resource constrainted that processes barely using memory
> get killed.

Again, there's no OOM killer here, so the process has the opportunity to
respond
differently.  I can understand the database not functioning well when the
system
is out of memory, but this half-functioning, half-deadlocked state is quite
disruptive.  By comparison, while not ideal, if the syslogger had raised
SIGABRT
instead, that would have been significantly better for my use-case.  Our
process
manager would have terminated all of the processes associated with the
database
and restarted it.


Tom Lane wrote:
> Hm, so that's another angle David didn't report on: is it possible that
> his workload could have resulted in a very large volume of incomplete
> in-progress log messages?

Yes.  I mentioned in my Nov 6 mail that large log messages over a short
period
appear to have been a major contributing factor:

> Here are all of the entries in the PostgreSQL log from 23:19:12 until the
top of
> the next hour:
>
https://gist.githubusercontent.com/davepacheco/c5541bb464532075f2da761dd990a457/raw/2ba242055aca2fb374e9118045a830d08c590e0a/gistfile1.txt
...
> There are also many log entries for some very long SQL queries.  I'm sure
that
> contributed to this problem by filling up the pipe.  I was able to
extract the
> contents of the pipe while the system was hung, and it was more of these
giant
> query strings.



Andres Freund wrote:
> Note that there's plenty of cases where you could run into this even
> without being unable to fork new processes. You'd e.g. could also run
> into this while logging the exit of some other subprocess or such,
> there's enough ereports in postmaster.

This is a critical point.  As far as I can tell, all that's necessary for
this
deadlock to occur is:

- the syslogger is unable to make forward progress (e.g., because it
segfaulted)
- enough other processes write to the pipe that it fills up before the
  postmaster can restart the syslogger
- the postmaster attempts to write to the log as part of any of its signal
  handling operations

It seems to me that the same thing can happen if there were a bug in the
syslogger that resulted in a segfault around the same time that the
postmaster
attempted to start an autovacuum worker, for example (if there was also
reasonably high log traffic).


Thanks,
Dave

Re: Migration to PGLister - After

[Rich Shepard]

On Mon, 20 Nov 2017, Joshua D. Drake wrote:


Yep, but that is why the list-id filter is bad advice (at least for me). I
filter on the list email address and it works flawlessly.


Joshua,

  This does not work if the procmail recipe is for pgsql-gene...@postgresql.org
and the source includes the server; e.g, pgsql-general@lists.postgresql.org.
Perhaps adding '.*' in front of postgresql.org will fix this.

Rich

unsubscribe

[Matt]

Re: Migration to PGLister - After

[Stephen Frost]

Josh,

* Joshua D. Drake (j...@commandprompt.com) wrote:
> Yep, but that is why the list-id filter is bad advice (at least for
> me). I filter on the list email address and it works flawlessly.

Indeed, this depends on what you're looking to do.  Filtering on
addresses listed in the To/CC is another approach and might work for
some, but it really depends on what you want.

If you do filter on the addresses listed in the To/CC, then it would
probably make sense to turn off the 'extra copy' option in the PGLister
configuration to avoid having duplicates.

If, as I do, you'd prefer to have both and to have the emails sent
through the list end up in a specific folder with the emails sent
directly to you going to your inbox, then using List-Id is the better
approach.

As mentioned up-thread, this isn't something we're able to really
control on the PGLister side, however.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: Migration to PGLister - After

[Joshua D. Drake]

On 11/20/2017 09:32 AM, John R Pierce wrote:

On 11/20/2017 6:45 AM, Stephen Frost wrote:

The changes which we expect to be most significant to users can be found
on the wiki here:https://wiki.postgresql.org/wiki/PGLister_Announce  the
current version of which is also included below.



A peeve on this new configuration:    if someone does a reply-all and 
sends both direct and list responses, the direct response ends up in 
my regular inbox because it doesn't have the List-ID... Previously, 
the direct reply would still have the Subject: [listname] that I 
filtered on, so it too would end up in my 'postgres' folder, where I 
want it.


I realize why this was done, and yada yada, what a mess.



Yep, but that is why the list-id filter is bad advice (at least for me). 
I filter on the list email address and it works flawlessly.


JD



--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *

Re: [GENERAL] unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs

[Tom Lane]

Luca Ferrari  writes:
> I don't think it is what I'm looking for, I would like something ,like:
>  select unnest( histogram_bounds::text::text[] ), unnest(
> most_common_freqs ) from pg_stats
> but with correlation between the two array indexes. Is it something
> achievable in SQL? Or should I use a plpgsql loop with an index?

Those two aren't correlated ... but I think what you want is

select ...,v,f
from
  pg_stats,
  rows from (unnest(most_common_vals::text::text[]),
 unnest(most_common_freqs)) r(v,f)
where ...

Seems to work back to 9.4.

regards, tom lane