pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Erik Wienhold <ewie@ewie.name>
To: [Quipsy] Markus Karg <karg@quipsy.de>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: AW: Cast INTEGER to BIT confusion
Date: Tue, 15 Aug 2023 16:27:53 +0200 (CEST)
Message-ID: <400164688.228966.1692109673749@office.mailbox.org> (raw)
In-Reply-To: <84bd46dba5ec4097ba9663f46a1e5754@quipsy.de>
References: <fbc716336d544e93b6af5e11af3e4aa0@quipsy.de>
	<533487381.212078.1692100096551@office.mailbox.org>
	<84bd46dba5ec4097ba9663f46a1e5754@quipsy.de>

> On 15/08/2023 14:02 CEST [Quipsy] Markus Karg <karg@quipsy.de> wrote:
>
> I just tried out your proposal on PostgreSQL 15.3 and this is the result:
>
> ERROR:  column "c" is of type bit but expression is of type integer
> LINE 5:   INSERT INTO t VALUES (1);
>                                 ^
> HINT:  You will need to rewrite or cast the expression.
>
> Apparently the search path is ignored?!
>
> -----Ursprüngliche Nachricht-----
> Von: Erik Wienhold <ewie@ewie.name> 
> Gesendet: Dienstag, 15. August 2023 13:48
> An: [Quipsy] Markus Karg <karg@quipsy.de>; pgsql-general@lists.postgresql.org
> Betreff: Re: Cast INTEGER to BIT confusion
>
> You could create a custom domain if you're only interested in values 0 and 1
> and don't use bit string functions.  The search path must be changed so that
> domain bit overrides pg_catalog.bit:
> 
> 	=# CREATE SCHEMA xxx;
> 	=# CREATE DOMAIN xxx.bit AS int;
> 	=# SET search_path = xxx, pg_catalog;
> 	=# CREATE TABLE t (c bit);
> 	=# INSERT INTO t VALUES (1);
> 	INSERT 0 1
>
> But I would do that only if the third-party code cannot be tweaked because
> the custom domain could be confusing.  It's also prone to errors as it relies
> on a specific search path order.  Also make sure that regular users cannot
> create objects in schema xxx that would override objects in pg_catalog.

Hmm, I thought that Postgres resolves all types through the search path, but
apparently that is not the case for built-in types.  I never used this to
override built-in types so this is a surprise to me.  (And obviously I haven't
tested the search path feature before posting.)

Neither [1] or [2] mention that special (?) case or if there's a distinction
between built-in types and user-defined types.  The USAGE privilege is required
according to [2] but I was testing as superuser anyway.

[1] https://www.postgresql.org/docs/15/ddl-schemas.html
[2] https://www.postgresql.org/docs/15/runtime-config-client.html#GUC-SEARCH-PATH

--
Erik





view thread (4+ messages)

Message-ID: <400164688.228966.1692109673749@office.mailbox.org>
Permalink:  ../400164688.228966.1692109673749@office.mailbox.org/
Also on:    postgresql.org/message-id/400164688.228966.1692109673749@office.mailbox.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ewie@ewie.name, karg@quipsy.de
  Subject: Re: Cast INTEGER to BIT confusion
  In-Reply-To: <400164688.228966.1692109673749@office.mailbox.org>
  References: <fbc716336d544e93b6af5e11af3e4aa0@quipsy.de> <533487381.212078.1692100096551@office.mailbox.org> <84bd46dba5ec4097ba9663f46a1e5754@quipsy.de> <400164688.228966.1692109673749@office.mailbox.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox