Em qua., 18 de dez. de 2019 às 15:59, Stephen Frost
escreveu:
> >Alright, well, oddly enough, *this* email included the other headers and
> >appears threaded properly (in mutt, at least).
>
> >Did you do something different when replying to this email vs. the other
> >emails you've been replying
Greetings,
* Ranier Vilela (ranier_...@hotmail.com) wrote:
> De: Robert Haas
> Enviado: quarta-feira, 18 de dezembro de 2019 15:44
>
> >A lot of your emails, like this one, seem to be replies to other
> >emails, but at least in my mail reader (gmail) something you're doing
> >is causing the
De: Robert Haas
Enviado: quarta-feira, 18 de dezembro de 2019 15:44
>A lot of your emails, like this one, seem to be replies to other
>emails, but at least in my mail reader (gmail) something you're doing
>is causing the threading to get broken, so it's very hard to know what
>this is replying
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, Dec 17, 2019 at 9:06 AM Ranier Vilela wrote:
> > De: Michael Paquier
> > Enviadas: Terça-feira, 17 de Dezembro de 2019 04:45
> > >And if you actually group things together so as any individual looking
> > >at your patches does not
On Tue, Dec 17, 2019 at 9:06 AM Ranier Vilela wrote:
> De: Michael Paquier
> Enviadas: Terça-feira, 17 de Dezembro de 2019 04:45
> >And if you actually group things together so as any individual looking
> >at your patches does not have to figure out which piece applies to
> >what, that's also
De: Michael Paquier
Enviadas: Terça-feira, 17 de Dezembro de 2019 04:45
>And if you actually group things together so as any individual looking
>at your patches does not have to figure out which piece applies to
>what, that's also better.
I'm still trying to find the best way.
>Anyway, the patch
On Mon, Dec 16, 2019 at 07:57:10PM +0100, Juan José Santamaría Flecha wrote:
> If you want to address 2 unrelated issues, it makes little sense to use a
> single thread and 3 patches.
And if you actually group things together so as any individual looking
at your patches does not have to figure
On Mon, Dec 16, 2019 at 6:34 PM Ranier Vilela
wrote:
>
> Considering that postgres only supports windows versions that have the new
> API, it would be good to make the replace.
>
>
That is not actually the case. If you check the _WIN32_WINNT logic
in src/include/port/win32.h you can see that
Hi,
According to microsoft documentation at:
https://docs.microsoft.com/en-us/windows/win32/api/wincrypt/nf-wincrypt-cryptgenrandom
The function CryptGenRandom is deprecated, and may can be removed in future
release.
Considering that postgres only supports windows versions that have the new API,
