Timescaledb: Creating table failed after enabling the timescaledb extension

Created on 10 Oct 2017  路  5Comments  路  Source: timescale/timescaledb

I'm getting "server closed the connection unexpectedly" error after executing the following commands in psql.

postgres=# create database test; 
CREATE DATABASE                  
postgres=# create extension timescaledb;
CREATE EXTENSION
postgres=# create table old_table (id integer);                        
CREATE TABLE                                  
postgres=# CREATE TABLE new_table (LIKE old_table);                              
server closed the connection unexpectedly                          
        This probably means the server terminated abnormally       
        before or while processing the request.                    
The connection to the server was lost. Attempting reset: Failed.

If I don't enable extension the "CREATE TABLE new_table (LIKE old_table)" would work without any issue. I still can enable the extension after creating the table but it's kinda annoying.

I'm running timescale 0.5 on docker.

bug duplicate

All 5 comments

Hi @ziXet: Thanks for the report!

We pushed a fix to master for this problem a few days ago. It will be part of the 0.6 release, which should go out later this week.

(I believe this is the PR that fixes the problem: https://github.com/timescale/timescaledb/pull/230)

@mfreed Is this same issue as what I reported in slack earlier today?

I'm guessing the server crashed with seg fault here.

@ryan-shaw If my memory serves me correctly, I think your issue was slightly different, but this merged PR should fix your problem: https://github.com/timescale/timescaledb/pull/251

Will be in next release.

Hi, I have the exact same issue here but with Timescale 0.9.1 with Postgresql 10 on windows10. I don't know if I need to comment here or create another issue...

Feel free to open a new issue with as much detail as you can.

Was this page helpful?
0 / 5 - 0 ratings