Haribabu Kommi | 3 Mar 00:25 2014
Picon

Re: BUG #9370: PostgreSQL Service Unexpectedly closing in SERVER Computer


On Sat, Mar 1, 2014 at 3:35 PM, vivek s <vivekspathil <at> gmail.com> wrote:
i here by attached the the log file, please check it ...  its really urgent our clients complaining

and for your information we are using Devart's Dotconnect for Postgres instead of Npgsql

From the log files, It is observed as the server is getting crashed with the following information.

2014-02-26 11:59:45 IST LOG:  server process (PID 5488) was terminated by exception 0xC0000142
2014-02-26 11:59:45 IST HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.

The error code description from ntstatus.h file says because of DLL init failed.
// // MessageId: STATUS_DLL_INIT_FAILED // // MessageText: // // {DLL Initialization Failed} // Initialization of the dynamic link library %hs failed. The process is terminating abnormally. // #define STATUS_DLL_INIT_FAILED ((NTSTATUS)0xC0000142L)Can you please check in your setup for the above problem.
Regards,
Hari Babu
Fujitsu Australia
davidpf75 | 1 Mar 22:46 2014
Picon

BUG #9404: (URGENT) problem after calling PQconnectdb, exceptions are not caught

The following bug has been logged on the website:

Bug reference:      9404
Logged by:          David
Email address:      davidpf75 <at> gmail.com
PostgreSQL version: 8.4.0
Operating system:   Windows 7 64bit
Description:        

Hi. 
I need help with this issue. I'm working on an important project!

After calling PQconnectdb , everything is ok, the db and all queries. But I
don't know why, error and exceptions are not caught. I mean, I don't see the
windows error crash popup anymore. 

this code just exit without windows error/crash window:
{
	int tmp_i = 0;
	db = PQconnectdb("host=127.0.0.1 dbname='test' user=test password=test");
	tmp_i /= tmp_i;
}
----------
but this one shows a crash/error window
{
	int tmp_i = 0;
	tmp_i /= tmp_i;
}

------
So is like PQconnectdb is blocking exceptions or error handling. Can you
help me? 

my email is davidpf75 <at> gmail.com

Thanks!

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

no-email | 1 Mar 10:51 2014

BUG #9398: DELETE refering to a materialized view produces "cannot lock rows in materialized view" error

The following bug has been logged on the website:

Bug reference:      9398
Logged by:          nakag
Email address:      no-email <at> example.com
PostgreSQL version: 9.3.3
Operating system:   Linux
Description:        

CREATE TABLE base ( id int primary key );
CREATE MATERIALIZED VIEW mv AS SELECT * FROM base;
CREATE TABLE d ( id int primary key );
DELETE FROM d WHERE EXISTS ( SELECT * FROM mv WHERE mv.id = d.id );

The above code produces an ERROR "cannot lock rows in materialized view."

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

rajkumarmca1488 | 28 Feb 15:55 2014
Picon

BUG #9384: Restore Database using psql utility fails

The following bug has been logged on the website:

Bug reference:      9384
Logged by:          Rajkumar.K
Email address:      rajkumarmca1488 <at> gmail.com
PostgreSQL version: 9.3.2
Operating system:   Linux CentsOs 6.4
Description:        

Fine i have taken backup of my database using "pg_dump" utility(dump file
name is "testbackup.sql").Before restoring it back,i dropped all
tables,view,sequences,functions which i have created. After that using
"psql" command try to restore the dump back.But it shows the duplicate-key
violation error.
Error : psql.bin:testbackup.sql:17884: ERROR:  duplicate key value violates
unique constraint "pg_largeobject_metadata_oid_index".I googled in internet
but i cant come to a correct solution.so Kindly provide us theproper
solution.

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

consolity | 27 Feb 21:12 2014

BUG #9373: UUID, UUID-OSSP extension, and ODBC issues

The following bug has been logged on the website:

Bug reference:      9373
Logged by:          Jeremy Thornton
Email address:      consolity <at> outlook.com
PostgreSQL version: 9.3.3
Operating system:   Windows 8.1 Pro
Description:        

In using pgsqlODBC 09.03.0200 or any version prior that we have tested we
seem to be having a performance decrease to only 625 inserts per second when
using UUID as the primary key and using the UUID-OSSP to generate the
default value of uuid_generate_v1() whereas if we generate the UUID client
side for the primary key and send it with the values in the insert
transaction we can increase it to 1500 inserts per second bypassing the
UUID-OSSP extension. This is consistent and repeatable. The only change
being made is Postgres generating the UUID using the extension or us passing
the value in the insert statement. If Postgres generates it internally while
inserting using PgAdmin then it can generate at near 2000 inserts per second
so uuid-ossp shouldn't be the problem since it can keep up, but when used
over default settings in ODBC it is 2/3 slower. The data being tested is the
same in all cases. I am using a default System DSN on Windows 8.1 Pro (no
special settings). Is this a bug or a settings adjustment that needs to be
made?

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

randy.antler | 1 Mar 01:46 2014

BUG #9396: Line editing keybindings not working

The following bug has been logged on the website:

Bug reference:      9396
Logged by:          Randy Antler
Email address:      randy.antler <at> socrata.com
PostgreSQL version: 9.3.2
Operating system:   Mavericks
Description:        

The keybinding that is commonly used on Mac OS X systems — control-d — does
not work in the query editor.

This represents a significant hardship for me.

Is it possible to fix this error?

Thank you very much.

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

mark.a.sloan | 27 Feb 22:52 2014
Picon

BUG #9374: some timzone abbver is missing from pg_timezone_abbrevs that are in pg_timezone_names

The following bug has been logged on the website:

Bug reference:      9374
Logged by:          Mark Sloan
Email address:      mark.a.sloan <at> gmail.com
PostgreSQL version: 9.3.3
Operating system:   CentOS 6.5
Description:        

postgres=# SELECT * FROM pg_timezone_names   where abbrev = 'WIB' ;
         name         | abbrev | utc_offset | is_dst 
----------------------+--------+------------+--------
 posix/Asia/Pontianak | WIB    | 07:00:00   | f
 posix/Asia/Jakarta   | WIB    | 07:00:00   | f
 Asia/Pontianak       | WIB    | 07:00:00   | f
 Asia/Jakarta         | WIB    | 07:00:00   | f
(4 rows)

postgres=# SELECT * FROM pg_timezone_abbrevs  where abbrev = 'WIB' ;
 abbrev | utc_offset | is_dst 
--------+------------+--------
(0 rows)

using PGDG rpms. 

postgresql-server-9.2.7, or 9.3.3
tzdata-2013i-2 

I am not sure if "ALL" of these are supposed to be in pg_timezone_abbrevs. 

here is the missing ones. 

 abbrev 
--------
 AQTT
 CAT
 CHOT
 CVT
 CWST
 ChST
 ECT
 GMT+1
 GMT+10
 GMT+11
 GMT+12
 GMT+2
 GMT+3
 GMT+4
 GMT+5
 GMT+6
 GMT+7
 GMT+8
 GMT+9
 GMT-1
 GMT-10
 GMT-11
 GMT-12
 GMT-13
 GMT-14
 GMT-2
 GMT-3
 GMT-4
 GMT-5
 GMT-6
 GMT-7
 GMT-8
 GMT-9
 GST
 HAST
 HOVT
 IRST
 MIST
 MeST
 NCT
 NRT
 ORAT
 QYZT
 ROTT
 SAKT
 SAMT
 SBT
 SRT
 SST
 SYOT
 TLT
 VOST
 WIB
 WIT
 WITA
 WSDT
 WST
(57 rows)

the WIB one is giving me grief, I am going to push that we convert to always
using timezone names rather than abbreviations, but this looked odd to me.  

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

jenifersouza8 | 28 Feb 01:09 2014
Picon

BUG #9376: erro na instalação

The following bug has been logged on the website:

Bug reference:      9376
Logged by:          jenifersouza.
Email address:      jenifersouza8 <at> hotmail.com
PostgreSQL version: 9.3.3
Operating system:   windows 7
Description:        

gente, preciso fazer um trabalho e todas as versões que eu baixei chega no
final e dá erro no pg_hba.conf, sendo assim não consigo conectar com o
servidor.

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Jeremy Thornton | 27 Feb 21:10 2014

UUID, UUID-OSSP extension, and ODBC issue

In using pgsqlODBC 09.03.0200 or any version prior that we have tested we seem to be having a performance decrease to only 625 inserts per second when using UUID as the primary key and using the UUID-OSSP to generate the default value of uuid_generate_v1() whereas if we generate the UUID client side for the primary key and send it with the values in the insert transaction we can increase it to 1500 inserts per second bypassing the UUID-OSSP extension. This is consistent and repeatable. The only change being made is Postgres generating the UUID using the extension or us passing the value in the insert statement. If Postgres generates it internally while inserting using PgAdmin then it can generate at near 2000 inserts per second so uuid-ossp shouldn't be the problem since it can keep up, but when used over default settings in ODBC it is 2/3 slower. The data being tested is the same in all cases. I am using a default System DSN on Windows 8.1 Pro (no special settings). Is this a bug or a settings adjustment that needs to be made?

Spec summary:
ODBC: pgsql 09.03.0200 with default settings;
OS: Windows 8.1 Pro;
Postgres version: 9.3.3;


Jeremy Thornton | 28 Feb 17:31 2014

UUID, UUID-OSSP extension, and ODBC issue

ODBC: pgsql 09.03.0200;
OS: Windows 8.1 Pro;
Postgres version: 9.3.3;

In using pgsqlODBC 09.03.0200 or any version prior that we have tested we seem to be having a performance decrease to only 625 inserts per second when using UUID as the primary key and using the UUID-OSSP to generate the default value of uuid_generate_v1() whereas if we generate the UUID client side for the primary key and send it with the values in the insert transaction we can increase it to 1500 inserts per second bypassing the UUID-OSSP extension. This is consistent and repeatable. The only change being made is Postgres generating the UUID using the extension or us passing the value in the insert statement. If Postgres generates it internally while inserting using a script through PgAdmin then it can generate at near 2000 inserts per second so uuid-ossp shouldn't be the problem since it can keep up inside PgAdmin, but when used over default settings in ODBC it is 2/3 slower. The data being tested is the same in all cases. I am using a default System DSN on Windows 8.1 Pro (no special settings). Is this a bug, expected behavior, or a settings adjustment that needs to be made?

DSN settings:

AB = 0
BI = 0
BoolsAsChar = 1
ByteaAsLongVarbinary = 1
CancelAsFreeStmt = 0
CommLog = 0
Debug = 0
DisallowPremature = 0
Driver = 0903\bin\psqlodbc30a.dll
ExtraSysTablePrefixes = dd_;
FakeOidIndex = 0
Fetch = 100
GssAuthUseGSS = 0
Ksqo = 1
LFConversion = 1
LowerCaseIdentifier = 0
MaxLongVarcharSize = 8190
MaxVarCharSize = 255
Optimizer = 0
Parse = 0
Port = 5432
Protocol = 7.4-1
ReadOnly = 0
RowVersioning = 0
ShowOidColumn = 0
ShowSystemTables = 0
SSLmode = allow
TextAsLongVarchar = 1
TurelsMinus1 = 0
UniqueIndex = 1
UnknownsAsLongVarChar = 1
UnkownSizes = 0
UpdatableCursors = 1
UseDeclareFetch = 0
UseServerSidePrepare = 1
XaOpt = 1


Sandro Santilli | 28 Feb 12:28 2014
Picon

uninterruptable regexp_replace in 9.2 and 9.3

Starting with commit 173e29aa5 the regexp_replace function
became uninterruptable during operations, and takes a lot
of time and RAM to process some patterns.

Full story in this thread:
http://www.postgresql.org/message-id/646.1393031856 <at> sss.pgh.pa.us

I'm hoping a mail to pgsql-bugs would assign this issue a ticket
number for me to follow. Let me know if there's a better way.
Thank you !

--strk;

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt  

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


Gmane