|Summary:||ASTERISK-17689: Duplicate columns retireved for CEL/PostgreSQL & multiple schemas|
|Reporter:||Anthony Messina (amessina)||Labels:|
|Date Opened:||2011-04-13 11:16:19||Date Closed:||2013-01-15 10:17:52.000-0600|
|Description:||When connecting to PostgreSQL which has separate schemas (one per asterisk host, in my case), but identical CEL tables, the following duplication of columns occurs in Asterisk 220.127.116.11:|
[Apr 12 13:44:50] ERROR cel_pgsql.c: Connection may have been lost... attempting to reconnect.
[Apr 12 13:44:50] ERROR cel_pgsql.c: Connection reestablished.
[Apr 12 13:44:50] ERROR cel_pgsql.c: HARD ERROR! Attempted reconnection failed. DROPPING CALL RECORD!
[Apr 12 13:44:50] ERROR cel_pgsql.c: Reason: ERROR: column "id" specified more than once
LINE 1: INSERT INTO chicago.cel ("id","id","eventtype","eventtype","...
****** ADDITIONAL INFORMATION ******
This seems similar to what was described here: https://issues.asterisk.org/view.php?id=16655
|Comments:||By: Leif Madsen (lmadsen) 2011-04-14 08:25:34|
You'll need to provide additional information. At a minimum, the configuration which can allow someone to duplicate this in the lab.
By: Anthony Messina (amessina) 2011-04-14 11:13:43
The schemas chicago and elburn are the same in that they both contain a 'cel' table (and a 'cdr' table) with the same columns.
From cel_pgsql.conf in Chicago:
And I have another machine in Elburn:
By: Matt Jordan (mjordan) 2013-01-15 10:17:47.489-0600
Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8.
This appears to be a duplicate of ASTERISK-15475, which was fixed in 1.6.2. If this issue persists in 1.8+, please let a bug marshal know in #asterisk-bugs and we can reopen this issue. Thanks!