Re: Problem with ssl and psql in Postgresql 13

2020-12-30 Thread Stephen Frost
Greetings, First, thanks a lot for working on all of this and improving things! * Tom Lane (t...@sss.pgh.pa.us) wrote: > I've got one last complaint about the backend GSS code: we are doing > things randomly differently in the two places that install > krb_server_keyfile as the active KRB5_KTNAME

Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Demitri Muna
Hello, I’m getting stuck on a problem I was hoping I could get some help with. I’m trying to create an index for the results of a function that touches two tables like this and get the following error: CREATE INDEX my_idx ON mytable (first_time(id)); ERROR: could not read block 0 in file "base

Re: Problem with ssl and psql in Postgresql 13

2020-12-30 Thread Tom Lane
Stephen Frost writes: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> I think we'd be best off to always override KRB5_KTNAME if we have a >> nonempty krb_server_keyfile setting, so the attached proposed patch >> makes both functions do it the same way. (I did not make an effort >> to remove the depe

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Tom Lane
Demitri Muna writes: > I’m getting stuck on a problem I was hoping I could get some help with. I’m > trying to create an index for the results of a function that touches two > tables like this and get the following error: > CREATE INDEX my_idx ON mytable (first_time(id)); > ERROR: could not re

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Demitri Muna
Hi Tom, > On Dec 30, 2020, at 11:50 AM, Tom Lane wrote: > > I would call this a bug if it were a supported case, but really you are > doing something you are not allowed to. Functions in indexed expressions > are required to be immutable, and a function that looks at the contents of > a table -

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Karsten Hilbert
Am Wed, Dec 30, 2020 at 02:37:59PM -0500 schrieb Demitri Muna: > I want to index the results of these repeated, unchanging calculations to > speed up other queries. Which mechanism would be best to do this? Create > additional columns? Create another table? A materialized view ? Karsten -- GPG

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Christophe Pettus
> On Dec 30, 2020, at 11:37, Demitri Muna wrote: > I want to index the results of these repeated, unchanging calculations to > speed up other queries. Which mechanism would be best to do this? Create > additional columns? Create another table? This might be a good use for a generated column.

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Christophe Pettus
> On Dec 30, 2020, at 11:48, Christophe Pettus wrote: > > This might be a good use for a generated column. > > https://www.postgresql.org/docs/current/ddl-generated-columns.html I take that back; the generation formula has to be immutable as well. Perhaps a column populated by a trig

Re: Getting "could not read block" error when creating an index on a function.

2020-12-30 Thread Tom Lane
Karsten Hilbert writes: > Am Wed, Dec 30, 2020 at 02:37:59PM -0500 schrieb Demitri Muna: >> I want to index the results of these repeated, unchanging calculations to >> speed up other queries. Which mechanism would be best to do this? Create >> additional columns? Create another table? > A mate