On 2023-04-08 Sa 14:13, Andres Freund wrote:
Hi,
On 2023-04-08 13:53:34 -0400, Tom Lane wrote:
Peter Geoghegan writes:
I was under the impression that issues like this would be caught by
CI. We used to have an MSVC CI target, but that's no longer the case
-- not since commit e6b6ea02. I'll
Hi,
On 2023-04-08 13:53:34 -0400, Tom Lane wrote:
> Peter Geoghegan writes:
> > I was under the impression that issues like this would be caught by
> > CI. We used to have an MSVC CI target, but that's no longer the case
> > -- not since commit e6b6ea02. I'll need to remember that.
>
> I thought
On Sat, Apr 8, 2023 at 10:53 AM Tom Lane wrote:
> I thought we were planning to drop the MSVC build scripts for v16.
> Is that no longer happening? If they're going to be around for
> awhile, maybe that CI job needs to be resurrected.
It seems as if commit e6b6ea02 had very good reasons to
Peter Geoghegan writes:
> I was under the impression that issues like this would be caught by
> CI. We used to have an MSVC CI target, but that's no longer the case
> -- not since commit e6b6ea02. I'll need to remember that.
I thought we were planning to drop the MSVC build scripts for v16.
Is
On Sat, Apr 8, 2023 at 8:22 AM Andrew Dunstan wrote:
> Try to unbreak MSVC builds for pg_waldump
>
> remedy an omission in commit 7d8219a444
Thanks for taking care of this.
I was under the impression that issues like this would be caught by
CI. We used to have an MSVC CI target, but that's no
Try to unbreak MSVC builds for pg_waldump
remedy an omission in commit 7d8219a444
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bbec50de16d2bf6e1a2878ff0f7e39dbd86ecff8
Modified Files
--
src/tools/msvc/Mkvcbuild.pm | 2 +-
1 file changed, 1
