Thread

1. BUG #18779: Segmentation fault while trying to connect via psql

   PG Bug reporting form <noreply@postgresql.org> — 2025-01-17T11:36:06Z

   The following bug has been logged on the website:
   
   Bug reference:      18779
   Logged by:          Daniel Elishakov
   Email address:      dan-eli@mail.ru
   PostgreSQL version: 16.6
   Operating system:   Debian GNU/Linux 12 (bookworm)
   Description:        
   
   This bug takes place in Debian-based operating systems. To replicate this
   bug please do following:
   1) Install and initialize PostgreSQL dbms
   2) Switch user to root (sudo -i)
   3) Switch user to postgres
   4) run command psql -U postgres -h localhost (may run multiple times to see
   the bug)
   
   Looks like this bug occurs because root user has ENV variable KRB5CCNAME,
   while postgres does not. Please try to check it in other PostgreSQL versions
   and other Debian linuxes.
   
   

2. Re: BUG #18779: Segmentation fault while trying to connect via psql

   Jeff Janes <jeff.janes@gmail.com> — 2025-01-19T02:32:02Z

   On Fri, Jan 17, 2025 at 6:51 AM PG Bug reporting form <
   noreply@postgresql.org> wrote:
   
   > The following bug has been logged on the website:
   >
   > Bug reference:      18779
   > Logged by:          Daniel Elishakov
   > Email address:      dan-eli@mail.ru
   > PostgreSQL version: 16.6
   > Operating system:   Debian GNU/Linux 12 (bookworm)
   > Description:
   >
   > This bug takes place in Debian-based operating systems. To replicate this
   > bug please do following:
   > 1) Install and initialize PostgreSQL dbms
   >
   
   I think we need more details. There are multiple ways to do both of those
   things.
   
   
   > 2) Switch user to root (sudo -i)
   > 3) Switch user to postgres
   >
   
   What if you just use one command, sudo -i -u postgres?
   
   
   > 4) run command psql -U postgres -h localhost (may run multiple times to see
   > the bug)
   >
   > Looks like this bug occurs because root user has ENV variable KRB5CCNAME,
   > while postgres does not.
   
   
   What did you do to make this happen?  A default debian installation does
   have KRB5CCNAME set for root.
   
   Cheers,
   
   Jeff
   

3. Re: BUG #18779: Segmentation fault while trying to connect via psql

   Даниил Элишаков <dan-eli@mail.ru> — 2025-01-22T08:28:53Z

   
   Here is a gif with bug scenario. Gif starts while already being switched to root user. The phrase ‘’Ошибка сегментирования’’ stands for Segmentation fault. Sorry for mixing up the issue and it’s possible causes in the previous letter. Hope this gif will make it clear
    
   Regards,
   Daniil  
   >Воскресенье, 19 января 2025, 5:32 +03:00 от Jeff Janes <jeff.janes@gmail.com>:
   > 
   >On Fri, Jan 17, 2025 at 6:51AM PG Bug reporting form < noreply@postgresql.org > wrote:
   >>The following bug has been logged on the website:
   >>
   >>Bug reference:      18779
   >>Logged by:          Daniel Elishakov
   >>Email address:       dan-eli@mail.ru
   >>PostgreSQL version: 16.6
   >>Operating system:   Debian GNU/Linux 12 (bookworm)
   >>Description:       
   >>
   >>This bug takes place in Debian-based operating systems. To replicate this
   >>bug please do following:
   >>1) Install and initialize PostgreSQL dbms
   > 
   >I think we need more details. There are multiple ways to do both of those things.
   >  
   >>2) Switch user to root (sudo -i)
   >>3) Switch user to postgres
   > 
   >What if you just use one command, sudo -i -u postgres?
   >  
   >>4) run command psql -U postgres -h localhost (may run multiple times to see
   >>the bug)
   >>
   >>Looks like this bug occurs because root user has ENV variable KRB5CCNAME,
   >>while postgres does not.
   > 
   >What did you do to make this happen?  A default debian installation does have KRB5CCNAME set for root.
   > 
   >Cheers,
   > 
   >Jeff 
    
    
   С уважением,
   Даниил Элишаков
   dan-eli@mail.ru