From: Tom Lane <tgl@sss.pgh.pa.us>
To: ahi <ahm3d.hisham@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Query unable to utilize index without typecast to fixed length character
Date: Thu, 06 Apr 2023 10:50:30 -0400
Message-ID: <2307636.1680792630@sss.pgh.pa.us> (raw)
In-Reply-To: <CADaW2UPo9tBmNVCiabhYaMG9qQ7Xk6-z4mwso44OqPntoYSsRQ@mail.gmail.com>
References: <CADaW2UPo9tBmNVCiabhYaMG9qQ7Xk6-z4mwso44OqPntoYSsRQ@mail.gmail.com>
ahi <ahm3d.hisham@gmail.com> writes:
> CREATE TABLE public.marketplace_sale (
> log_index integer NOT NULL,
> created_at timestamp with time zone DEFAULT now() NOT NULL,
> updated_at timestamp with time zone DEFAULT now() NOT NULL,
> block_timestamp timestamp with time zone NOT NULL,
> block bigint NOT NULL,
> contract_address character(42) NOT NULL,
> buyer_address character(42) NOT NULL,
> seller_address character(42) NOT NULL,
> transaction_hash character(66) NOT NULL,
> quantity numeric NOT NULL,
> token_id numeric NOT NULL,
...
Type character(N) is a hangover from the days of punched cards.
Don't use it. It has weird semantics concerning trailing spaces,
which are almost never the behavior you actually want, and cause
interoperability issues with type text. (Text is Postgres' native
string type, meaning that unlabeled string constants will tend to
get resolved to that.)
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, ahm3d.hisham@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Query unable to utilize index without typecast to fixed length character
In-Reply-To: <2307636.1680792630@sss.pgh.pa.us>
* 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