Skip to content

PostgreSQL is dropping native Windows port, use RPMs.

Important stuff is going on in IT industry nowadays.

Given that Microsot is merging bash shell into Windows, PostgreSQL is considering to drop native Windows port.

Core Team member Josh Berkus sent an email to PostgreSQL hackers mailing list the other day, and proposed dropping the Windows port.

Unsurprisingly, he got great support from Tom Lane. Tom wrote a response. Here is a quote from his email:

"Really? Good. I just committed my very last Windows-related fix, then. Somebody else can deal with it."

There are some unofficial reports about Tom that he opened up a champagne bottle right after this email, but I cannot disclosure my source.

Josh was also backed up by Joe Conway, who authors the famous PL/R extension:

"I would surely love to dump Windows support in PL/R as it is a major league PITA. It is probably an understatement to say that over the last 10+ years, 95+% of the time I have spent maintaining and supporting PL/R has been directly attributable to the Windows port."

However, users from the field acted promptly, looking for alternatives to run PostgreSQL on Windows.

After discussing with other team members, we, as the PostgreSQL YUM repo developers, decided to add Windows support to our RPMs. We contacted Microsoft, and Microsoft kindly provided us a tech preview of the bash environment. After some hacks, here are the results:

$ rpm -ivh postgresql95-libs-9.5.7-1PGDG.Windows2017.x86_64.rpm

command works as expected.

Please stay tuned, until we release all the remaining RPMs for Windows.


No Trackbacks


Display comments as Linear | Threaded

Craig Ringer on :

Amazingly, the base premise of this is NOT an april fool's joke. Microsoft really do seem to be releasing a syscall wrapper to let unmodified Linux binaries run on Windows, starting with an Ubuntu image.

The real announcement from PGDG will therefore be concerning apt repositories :p

Adrian Klaver on :

Any good con starts with the truth:) The email links where a nice touch.

Chris on :

Yes it's true. Not an April fools. The issue may be for those companies that are not able to upgrade to Windows 10. Those business users that use Postgres may not be able to use any newer releases/patches.

Here is a more detailed post. It's Ubuntu's bash specifically.

Adrian Klaver on :

It is true up to:

"However, users from the field...."

The giveaway being:

$ rpm -ivh postgresql95-libs-9.5.7-1PGDG.Windows2017.x86_64.rpm

Postgres 9.5 as of yesterdays release is at 9.5.2 not 9.5.7 and afaik there is no Windows 2017.

Chris on :

@Adrian - True. Didn't look closely at the rpm command.

Technically I don't see why it wouldn't work unless there are some features that Postgres needs that aren't implemented or are buggy.

They were able to apt-get Redis on Windows bash.

Adrian Klaver on :

Well given that Ubuntu(the distro running on Windows 10) is deb based the 'native' way to do it would be apt-get, otherwise you are going to have to invoke alien. At any rate the post is one of the best April fools I have run across lately. Plausible enough to get you thinking.

Craig Ringer on :

There are lots of reasons we wouldn't want to really do this. Just for one thing I doubt it's possible to use Windows-specific things like SSPI authentication when running under the Linux kernel syscall translator.

I find the fact that the syscall translator is real quite bizarre.

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.

Form options