Thread: BUG #18678: While installing the PostgreSQL wizard, it throws an error for an non found column

The following bug has been logged on the website:

Bug reference:      18678
Logged by:          Claudio
Email address:      claudioan00@gmail.com
PostgreSQL version: 17.0
Operating system:   Windows 10 Home
Description:

I'm installing it after trying to install it once on a Windows 10 Home VM,
as i had to change from NAT network to Bridge to be able to download the
files it needed. It went ok until the StackBuilder it seems, as it threw
this error:

psql: ERROR: no existe la columna d.daticulocale
LINE 8: d.daticulocale as "ICU Locale",
           ^
HINT: Probablemente quiera hacer referencia a la columna
Â<<d.datlocaleÂ>>.

I don't know why this happened but Google says something about some version
problem where a table is not being used anymore.

Thanks and keep the great work.

On 2024-10-30 20:57 +0100, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      18678
> Logged by:          Claudio
> Email address:      claudioan00@gmail.com
> PostgreSQL version: 17.0
> Operating system:   Windows 10 Home
> Description:        
> 
> I'm installing it after trying to install it once on a Windows 10 Home VM,
> as i had to change from NAT network to Bridge to be able to download the
> files it needed. It went ok until the StackBuilder it seems, as it threw
> this error:
> 
> psql: ERROR: no existe la columna d.daticulocale
> LINE 8: d.daticulocale as "ICU Locale",
>            ^
> HINT: Probablemente quiera hacer referencia a la columna
> Â<<d.datlocaleÂ>>.

Same error as reported by [1].

I wonder why the column alias reads "ICU Locale" when this is supposed
to be version 17.0.  That has been changed to just "Locale" in 17.0 [2].
Maybe the Windows builds just use some outdated localizations.

Is this a fresh 17.0 installation or an upgrade of a 15.x or 16.x
instance?  If the error originates from that query in [2], then the
installer thinks its connected to a 15.x or 16.x server when in fact
it is 17.0.

I don't know if EDB modifies the code for the Windows builds, but it
could be that the installer just didn't get the memo about the rename
and uses an outdated copy of that list-all-databases query, and that the
error is not actually coming from psql's \l command.

[1] https://postgr.es/m/DM4PR12MB85718BFA02214EC4AFD2A5CCF1482%40DM4PR12MB8571.namprd12.prod.outlook.com
[2]
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blobdiff;f=src/bin/psql/describe.c;h=68b2ea8872a430e5e40f445b557cbbad75e07876;hp=c05befbb6f2430f5ba016cb4a358a729447c9a9c;hb=f696c0cd5f299f1b51e214efc55a22a782cc175d;hpb=81d13a8dc066e571dca032da0a5fc1d81214d2bb

-- 
Erik