Thread: Re: sudden program termination: no warning, error, or crash
DP> I've been trying to reproduce this here and so far have been DP> unsuccessful. The only deviations from the procedure that I've made DP> are that I've only got a small spreadsheet, and I'm using Alt+Tab to DP> toggle to Excel (Shift-Tab is simply a back-tab, which shouldn't DP> change windows, just the control that has focus in the current DP> window). DP> Are there any tiny details missing form the procedure you posted? Contents of this response are as follows: I. More comments on procedures leading up to the termination II. MS Office 2007 characteristics III. System details IV. Services running in background include I. More comments on procedures leading up to the termination: pgAdmin is 1.10.0. The error often happens after I have created a number of columns and then creating the two timestamp with timezone columnsat which the error seams to appear most. Naming convention is lower case first word, then capital first characterof subsequent words. Table creation is generally as such (toggling between Excel 2007 and pgAdminIII at every step(I use the Excel datamodel to manage the design/changes/planning etc of the db due to the inability of PostgreSQL toallow for easily re-order positions of columns as well as some other reasons). * Create table * Create a bigserial, non-null column called "serialNumInt" (This is the primary key on all tables with the exception ofmany-to-many tables) * Create a text column called "recordDescriptiveCodeStr". Add a comment to it after creation. * On many-to-many tables, create two bigint, non-null columns. Then make them jointly the primary key. Add separate foreignkeys to each (using the default settings for the foreign keys). Add a comment to some of them after creation. * Add a bigint column, null ok. Add a foreign key for this column (using default settings for the foreign key). * Create various text, bigint, and double precision columns (depending on the table) * Create 3 text columns * Create a bigint column * Create the two "timestamp with time zone" columns. Each have a comment (6 words for the first one, 7 words for the secondone). The termination is intermittent. Usually, there is no termination. When there is one, it seems most often during the creationof the second "timestamp with time zone" column (i.e., the last column of the table). II. MS Office 2007 characteristics: The following is a description of the Excel 2007 workbook (not sure how helpful this info will be though): It is the 2007 Japanese version of MS Office. Besides Excel 2007, Outlook 2007 (pst file is very large I think over 4 gig). The workbook has 15 worksheets. One of the worksheets is my data model. Another spreadsheet is a detailed description ofrules content for populating the tables. I have two windows open to the same workbook (one window on the datamodel spreadsheetand the other window to the rules content spreadsheet). I toggle between pgAdmin and the datamodel spreadsheet. The datamodel spreadsheet consists of 1,090 rows and 16 columns.I use "Grouping" tool in excel so that I can group rows of tables and expand and contract them from view. III. System details: Fujitsu FMV-S8235 Laptop. Intel Core Duo T2300 1.66 Ghz. 3.24Gb Ram. Windows 2003 Server Enterprise Edition SP2 native Japaneseversion. IV. Services running in background include: IIS and PostgreSQL 8.4 Regards, Jeff = Catholic Homeschooling Regina coeli online academy. Earn college credit. Classical study with a complete integrated Great Books program. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=0fb70de768d02e62cbb374be5690ffde
On Thu, Aug 20, 2009 at 12:41 AM, JwexlerAt MailDotCom<jwexler@mail.usa.com> wrote: > The error often happens after I have created a number of columns and then creating the two timestamp with timezone columnsat which the error seams to appear most. Naming convention is lower case first word, then capital first characterof subsequent words. Table creation is generally as such (toggling between Excel 2007 and pgAdminIII at every step(I use the Excel datamodel to manage the design/changes/planning etc of the db due to the inability of PostgreSQL toallow for easily re-order positions of columns as well as some other reasons). > * Create table > * Create a bigserial, non-null column called "serialNumInt" (This is the primary key on all tables with the exception ofmany-to-many tables) > * Create a text column called "recordDescriptiveCodeStr". Add a comment to it after creation. > * On many-to-many tables, create two bigint, non-null columns. Then make them jointly the primary key. Add separate foreignkeys to each (using the default settings for the foreign keys). Add a comment to some of them after creation. > * Add a bigint column, null ok. Add a foreign key for this column (using default settings for the foreign key). > * Create various text, bigint, and double precision columns (depending on the table) > * Create 3 text columns > * Create a bigint column > * Create the two "timestamp with time zone" columns. Each have a comment (6 words for the first one, 7 words for the secondone). > The termination is intermittent. Usually, there is no termination. When there is one, it seems most often during the creationof the second "timestamp with time zone" column (i.e., the last column of the table). What encoding/locale is your database using? Hiroshi/Quan - are either of you able to reproduce this issue? I'm wondering if this is something specific to Japanese Windows/locales etc. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Hi. Um, sorry, I can't reproduce a problem.... If possible, please send me the script which can reproduce a problem. Regards, Hiroshi Saito ----- Original Message ----- From: "Dave Page" <dpage@pgadmin.org> On Thu, Aug 20, 2009 at 12:41 AM, JwexlerAt MailDotCom<jwexler@mail.usa.com> wrote: > The error often happens after I have created a number of columns and then creating the two > timestamp with timezone columns at which the error seams to appear most. Naming convention is > lower case first word, then capital first character of subsequent words. Table creation is > generally as such (toggling between Excel 2007 and pgAdminIII at every step (I use the Excel > datamodel to manage the design/changes/planning etc of the db due to the inability of PostgreSQL > to allow for easily re-order positions of columns as well as some other reasons). > * Create table > * Create a bigserial, non-null column called "serialNumInt" (This is the primary key on all > tables with the exception of many-to-many tables) > * Create a text column called "recordDescriptiveCodeStr". Add a comment to it after creation. > * On many-to-many tables, create two bigint, non-null columns. Then make them jointly the primary > key. Add separate foreign keys to each (using the default settings for the foreign keys). Add a > comment to some of them after creation. > * Add a bigint column, null ok. Add a foreign key for this column (using default settings for the > foreign key). > * Create various text, bigint, and double precision columns (depending on the table) > * Create 3 text columns > * Create a bigint column > * Create the two "timestamp with time zone" columns. Each have a comment (6 words for the first > one, 7 words for the second one). > The termination is intermittent. Usually, there is no termination. When there is one, it seems > most often during the creation of the second "timestamp with time zone" column (i.e., the last > column of the table). What encoding/locale is your database using? Hiroshi/Quan - are either of you able to reproduce this issue? I'm wondering if this is something specific to Japanese Windows/locales etc. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com