From: | Imre Samu <pella(dot)samu(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL Mailing list public archives : search not working ... |
Date: | 2023-04-06 22:27:04 |
Message-ID: | CAJnEWwkpt6nCR8m_O3MY1JciunDnV-5YjY7bC4rgJOF72C+U0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-www |
>
>
> I can confirm that this example gives different result sets depending
> on the choice of sort order. Surely that's a bug? I have little idea
> what's going on under the hood though.
>
I assumed that if I searched for an existing email subject[1], I would get
a hit.
And when I didn't get a hit [2] I was very surprised and didn't understand
why?
So It's strange to me.
[1] https://www.postgresql.org/list/pgsql-general/since/202212010000/
"postgres large database backup" <-- so this email subject exists.
[2] if I search for "postgres large database backup" in
"pgsql-general" ordered by "date"
https://www.postgresql.org/search/?m=1&q=postgres+large+database+backup&l=2&d=-1&s=d
~ 2 ( + this mail expected )
compare to
https://postgrespro.com/search/?q=postgres+large+database+backup&area=archive&list=pgsql-general&period=&order=date
where I see - the expected mail
- 2022-11-30 18:40:23 | postgres large database backup (Atul Kumar)
regards,
Imre
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2023-04-06 23:47:55 | Re: PostgreSQL Mailing list public archives : search not working ... |
Previous Message | Benedict Holland | 2023-04-06 21:42:16 | Re: UPSERT in Postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2023-04-06 23:47:55 | Re: PostgreSQL Mailing list public archives : search not working ... |
Previous Message | Tom Lane | 2023-04-06 20:04:43 | Re: PostgreSQL Mailing list public archives : search not working ... |