pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBug report
28+ messages / 16 participants
[nested] [flat]
* Bug report
@ 2003-03-21 00:26 Robert E. Bruccoleri <bruc@stone.congenomics.com>
0 siblings, 2 replies; 28+ messages in thread
From: Robert E. Bruccoleri @ 2003-03-21 00:26 UTC (permalink / raw)
To: pgsql-bugs
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Robert Bruccoleri
Your email address : bruc@acm.org
System Configuration
---------------------
Architecture (example: Intel Pentium) : SGI Origin 3000
Operating System (example: Linux 2.0.26 ELF) : Irix 6.5.18
PostgreSQL version (example: PostgreSQL-7.3.2): PostgreSQL-7.3.2 and possibly 7.2.1
Compiler used (example: gcc 2.95.2) : MIPS Pro 7.4 and MIPS Pro 7.3.1.3, 64 bit compilation model.
Please enter a FULL description of your problem:
------------------------------------------------
The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that
would normally deadlock.
The following debugging session on the core dump shows some details:
nunu postgres 101 >>dbx /pg/postgresql-7.3.2/bin/postgres
dbx version 7.3.3 (78517_Dec16 MR) Dec 16 2001 07:45:22
Core from signal SIGBUS: Bus error
file foo.dbx already exists, appending
[3] record input foo.dbx (0 lines)
warning: file foo.dbx already exists, appending
[4] record output foo.dbx (0 lines)
(dbx) where
> 0 ExpandConstraints(constraints = 0x1041ad58, nConstraints = 1) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/deadlock.c":586, 0x101df1ec]
1 TestConfiguration(startProc = 0x8006483ebf8) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/deadlock.c":322, 0x101de90c]
2 DeadLockCheckRecurse(proc = 0x8006483ebf8) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/deadlock.c":246, 0x101de698]
3 DeadLockCheckRecurse(proc = 0x8006483ebf8) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/deadlock.c":280, 0x101de828]
4 DeadLockCheck(proc = 0x8006483ebf8) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/deadlock.c":192, 0x101de4a4]
5 CheckDeadLock() ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/proc.c":843, 0x101dd9d0]
6 handle_sig_alarm(postgres_signal_arg = 14) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/proc.c":1145, 0x101de280]
7 _sigtramp(0xc, 0x1, 0xda710a4, 0x7f7f7f7f7f7f7f7f, 0x1034fe50, 0xe, 0x1, 0x9) ["/xlv14/patches/4847/work/irix/lib/libc/libc_64_M4/signal/sigtramp.s":71, 0xda6250c]
8 __syscall(0x41d, 0x2, 0xf1, 0x1, 0x72, 0x75, 0x80044833070, 0x1) ["/xlv14/patches/4847/work/irix/lib/libc/libc_64_M4/sys/syscall.s":20, 0xda93178]
9 _semop(0xf1, 0xffffffcca30, 0x1, 0x1, 0x72, 0x75, 0x80044833070, 0x1) ["/xlv14/patches/4847/work/irix/lib/libc/libc_64_M4/sys/semsys.c":62, 0xda946a4]
10 PGSemaphoreLock(sema = 0x8006483ec08, interruptOK = '\001') ["/pg/postgresql-7.3.2/src/backend/port/pg_sema.c":434, 0x101a8d8c]
11 ProcSleep(lockMethodTable = 0x800648367c8, lockmode = 8, lock = 0x80064861480, holder = 0x800648625d0) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/proc.c":673, 0x101dd5e8]
12 WaitOnLock(lockmethod = 1, lockmode = 8, lock = 0x80064861480, holder = 0x800648625d0) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/lock.c":896, 0x101daa34]
13 LockAcquire(lockmethod = 1, locktag = 0xffffffccc58, xid = 5681, lockmode = 8, dontWait = '') ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/lock.c":685, 0x101da294]
14 LockRelation(relation = 0x104bc560, lockmode = 8) ["/pg/postgresql-7.3.2/src/backend/storage/lmgr/lmgr.c":133, 0x101d81c8]
15 relation_open(relationId = 23467, lockmode = 8) ["/pg/postgresql-7.3.2/src/backend/access/heap/heapam.c":477, 0x1005b46c]
16 LockTableCommand(lockstmt = 0x104c12d8) ["/pg/postgresql-7.3.2/src/backend/commands/lockcmds.c":61, 0x101061e4]
17 ProcessUtility(parsetree = 0x104c12d8, dest = Remote=2, completionTag = 0xffffffccf18 = "") ["/pg/postgresql-7.3.2/src/backend/tcop/utility.c":806, 0x101eb498]
18 pg_exec_query_string(query_string = 0x104c1010, dest = Remote=2, parse_context = 0x104bf120) ["/pg/postgresql-7.3.2/src/backend/tcop/postgres.c":789, 0x101e6cc8]
19 PostgresMain(argc = 4, argv = 0xffffffcd0c0, username = 0x103bf1a9 = "bruc") ["/pg/postgresql-7.3.2/src/backend/tcop/postgres.c":2013, 0x101e8be4]
20 DoBackend(port = 0x103bf078) ["/pg/postgresql-7.3.2/src/backend/postmaster/postmaster.c":2302, 0x101ad4c4]
21 BackendStartup(port = 0x103bf078) ["/pg/postgresql-7.3.2/src/backend/postmaster/postmaster.c":1924, 0x101ac8ec]
22 ServerLoop() ["/pg/postgresql-7.3.2/src/backend/postmaster/postmaster.c":1027, 0x101aae58]
23 PostmasterMain(argc = 8, argv = 0x103b3f98) ["/pg/postgresql-7.3.2/src/backend/postmaster/postmaster.c":788, 0x101aa6c4]
24 main(argc = 8, argv = 0xffffffcdde8) ["/pg/postgresql-7.3.2/src/backend/main/main.c":210, 0x1015fed4]
25 __start() ["/xlv55/kudzu-apr12/work/irix/lib/libc/libc_64_M4/csu/crt1text.s":177, 0x10032c78]
(dbx) l 570,590
570 int nConstraints)
571 {
572 int nWaitOrderProcs = 0;
573 int i,
574 j;
575
576 nWaitOrders = 0;
577
578 /*
579 * Scan constraint list backwards. This is because the last-added
580 * constraint is the only one that could fail, and so we want to test
581 * it for inconsistency first.
582 */
583 for (i = nConstraints; --i >= 0;)
584 {
585 PGPROC *proc = constraints[i].waiter;
* 586 LOCK *lock = proc->waitLock;
587
588 /* Did we already make a list for this lock? */
589 for (j = nWaitOrders; --j >= 0;)
590 {
(dbx) p proc
0x7f7f7f7f7f7f7f7f
(dbx) p constraints[0]
struct {waiter = 0x7f7f7f7f7f7f7f7f, blocker = 0x7f7f7f7f7f7f7f7f, pred = 2139062143, link = 2139062143}
(dbx) p constraints[1]
struct {waiter = 0x7f7f7f7f7f7f7f7f, blocker = 0x7f7f7f7f7f7f7f7f, pred = 2139062143, link = 2139062143}
(dbx) p i
0
(dbx) p nConstraints
1
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
0) Create a user named tilfordc with all rights.
1) Construct a database using the 'maptracker.sql' schema attached to this message.
Use the name, 'maptracker', as an example.
2) Start two psql sessions on maptracker. Issue "BEGIN;" commands in both.
3) In session 1, type "lock mapping;".
4) In session 2, type "lock location;" and then "lock mapping;"
5) In session 1, type "lock location;". The backend will crash in a few seconds.
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
+-----------------------------+------------------------------------+
| Robert E. Bruccoleri, Ph.D. | email: bruc@acm.org |
| President, Congenomics Inc. | URL: http://www.congen.com/~bruc |
| P.O. Box 314 | Phone: 609 818 7251 |
| Pennington, NJ 08534 | |
+-----------------------------+------------------------------------+
Attachments:
maptracker.sql (text/plain, 28.0K) download
--
-- PostgreSQL database dump
--
\connect - tilfordc
SET search_path = public, pg_catalog;
--
-- TOC entry 2 (OID 23419)
-- Name: seqname_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE seqname_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 3 (OID 23421)
-- Name: class_list_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE class_list_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 4 (OID 23423)
-- Name: transform_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE transform_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 5 (OID 23425)
-- Name: authority_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE authority_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 6 (OID 23427)
-- Name: relationship_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE relationship_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 7 (OID 23429)
-- Name: mapping_seq; Type: SEQUENCE; Schema: public; Owner: tilfordc
--
CREATE SEQUENCE mapping_seq
START 1
INCREMENT 1
MAXVALUE 9223372036854775807
MINVALUE 1
CACHE 1;
--
-- TOC entry 8 (OID 23431)
-- Name: authority; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE authority (
authority_id integer NOT NULL,
upper_name character varying(100),
authname character varying(100),
descr character varying(255)
);
--
-- TOC entry 9 (OID 23435)
-- Name: class_list; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE class_list (
class_id integer NOT NULL,
parent_id integer,
seqclass character varying(20),
descr character varying(255)
);
--
-- TOC entry 10 (OID 23439)
-- Name: relationship; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE relationship (
type_id integer NOT NULL,
label character varying(20),
reads_forward character varying(50),
reads_backward character varying(50),
class1 integer,
class2 integer,
descr character varying(255)
);
--
-- TOC entry 11 (OID 23443)
-- Name: seqname; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE seqname (
name_id integer NOT NULL,
upper_name character varying(100),
seqname character varying(100)
);
--
-- TOC entry 12 (OID 23447)
-- Name: species; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE species (
tax_id integer NOT NULL,
taxa_name character varying(255),
upper_taxa character varying(255)
);
--
-- TOC entry 13 (OID 23451)
-- Name: species_alias; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE species_alias (
tax_id integer,
alias character varying(255),
name_class character varying(50)
);
--
-- TOC entry 14 (OID 23453)
-- Name: transform; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE transform (
trans_id integer NOT NULL,
transname character varying(50),
step1 double precision,
step2 double precision
);
--
-- TOC entry 15 (OID 23457)
-- Name: relation; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE relation (
name1 integer,
name2 integer,
type_id integer,
authority_id integer
);
--
-- TOC entry 16 (OID 23459)
-- Name: seq_class; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE seq_class (
class_id integer,
name_id integer,
authority_id integer
);
--
-- TOC entry 17 (OID 23461)
-- Name: seq_species; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE seq_species (
tax_id integer,
name_id integer,
authority_id integer
);
--
-- TOC entry 18 (OID 23463)
-- Name: mapping; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE mapping (
map_id integer NOT NULL,
name1 integer,
start1 double precision,
end1 double precision,
name2 integer,
start2 double precision,
end2 double precision,
trans_id integer,
authority_id integer,
map_score double precision,
strand integer
);
--
-- TOC entry 19 (OID 23467)
-- Name: location; Type: TABLE; Schema: public; Owner: tilfordc
--
CREATE TABLE "location" (
map_id integer,
start1 double precision,
end1 double precision,
start2 double precision
);
--
-- TOC entry 21 (OID 3260248)
-- Name: u_thrty_pprnm; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE UNIQUE INDEX u_thrty_pprnm ON authority USING btree (upper_name);
--
-- TOC entry 23 (OID 3260249)
-- Name: u_clsslst_sqclss; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE UNIQUE INDEX u_clsslst_sqclss ON class_list USING btree (seqclass);
--
-- TOC entry 27 (OID 3260250)
-- Name: u_rltnshp_lbl; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE UNIQUE INDEX u_rltnshp_lbl ON relationship USING btree (label);
--
-- TOC entry 24 (OID 3260251)
-- Name: ifk_rltnshp_clss1; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX ifk_rltnshp_clss1 ON relationship USING btree (class1);
--
-- TOC entry 25 (OID 3260252)
-- Name: ifk_rltnshp_clss2; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX ifk_rltnshp_clss2 ON relationship USING btree (class2);
--
-- TOC entry 29 (OID 3260253)
-- Name: u_sqnm_pprnm; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE UNIQUE INDEX u_sqnm_pprnm ON seqname USING btree (upper_name);
--
-- TOC entry 31 (OID 3260254)
-- Name: ifk_spcsls_txd; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX ifk_spcsls_txd ON species_alias USING btree (tax_id);
--
-- TOC entry 33 (OID 3260255)
-- Name: rltn_nm1nm2; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX rltn_nm1nm2 ON relation USING btree (name1, name2);
--
-- TOC entry 35 (OID 3260256)
-- Name: sqclss_nmd; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX sqclss_nmd ON seq_class USING btree (name_id);
--
-- TOC entry 36 (OID 3260257)
-- Name: sqspcs_nmd; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX sqspcs_nmd ON seq_species USING btree (name_id);
--
-- TOC entry 38 (OID 3260258)
-- Name: mppng_nm1strt1nd1; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX mppng_nm1strt1nd1 ON mapping USING btree (name1, start1, end1);
--
-- TOC entry 39 (OID 3260259)
-- Name: mppng_nm2strt2nd2; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX mppng_nm2strt2nd2 ON mapping USING btree (name2, start2, end2);
--
-- TOC entry 37 (OID 3260260)
-- Name: mppng_nm1nm2; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX mppng_nm1nm2 ON mapping USING btree (name1, name2);
--
-- TOC entry 41 (OID 3260261)
-- Name: ifk_lctn_mpd; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX ifk_lctn_mpd ON "location" USING btree (map_id);
--
-- TOC entry 34 (OID 3260262)
-- Name: rltn_nm2; Type: INDEX; Schema: public; Owner: tilfordc
--
CREATE INDEX rltn_nm2 ON relation USING btree (name2);
--
-- TOC entry 20 (OID 23433)
-- Name: pk_thrty_thrtyd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY authority
ADD CONSTRAINT pk_thrty_thrtyd PRIMARY KEY (authority_id);
--
-- TOC entry 22 (OID 23437)
-- Name: pk_clsslst_clssd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY class_list
ADD CONSTRAINT pk_clsslst_clssd PRIMARY KEY (class_id);
--
-- TOC entry 26 (OID 23441)
-- Name: pk_rltnshp_typd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY relationship
ADD CONSTRAINT pk_rltnshp_typd PRIMARY KEY (type_id);
--
-- TOC entry 28 (OID 23445)
-- Name: pk_sqnm_nmd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY seqname
ADD CONSTRAINT pk_sqnm_nmd PRIMARY KEY (name_id);
--
-- TOC entry 30 (OID 23449)
-- Name: pk_spcs_txd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY species
ADD CONSTRAINT pk_spcs_txd PRIMARY KEY (tax_id);
--
-- TOC entry 32 (OID 23455)
-- Name: pk_trnsfrm_trnsd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY transform
ADD CONSTRAINT pk_trnsfrm_trnsd PRIMARY KEY (trans_id);
--
-- TOC entry 40 (OID 23465)
-- Name: pk_mppng_mpd; Type: CONSTRAINT; Schema: public; Owner: tilfordc
--
ALTER TABLE ONLY mapping
ADD CONSTRAINT pk_mppng_mpd PRIMARY KEY (map_id);
--
-- TOC entry 56 (OID 3260263)
-- Name: RI_ConstraintTrigger_3260263; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relationship
FROM class_list
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class1', 'class_id');
--
-- TOC entry 50 (OID 3260264)
-- Name: RI_ConstraintTrigger_3260264; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON class_list
FROM relationship
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class1', 'class_id');
--
-- TOC entry 51 (OID 3260265)
-- Name: RI_ConstraintTrigger_3260265; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON class_list
FROM relationship
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class1', 'class_id');
--
-- TOC entry 57 (OID 3260266)
-- Name: RI_ConstraintTrigger_3260266; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relationship
FROM class_list
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class2', 'class_id');
--
-- TOC entry 52 (OID 3260267)
-- Name: RI_ConstraintTrigger_3260267; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON class_list
FROM relationship
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class2', 'class_id');
--
-- TOC entry 53 (OID 3260268)
-- Name: RI_ConstraintTrigger_3260268; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON class_list
FROM relationship
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relationship', 'class_list', 'UNSPECIFIED', 'class2', 'class_id');
--
-- TOC entry 74 (OID 3260269)
-- Name: RI_ConstraintTrigger_3260269; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON species_alias
FROM species
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'species_alias', 'species', 'UNSPECIFIED', 'tax_id', 'tax_id');
--
-- TOC entry 72 (OID 3260270)
-- Name: RI_ConstraintTrigger_3260270; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON species
FROM species_alias
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'species_alias', 'species', 'UNSPECIFIED', 'tax_id', 'tax_id');
--
-- TOC entry 73 (OID 3260271)
-- Name: RI_ConstraintTrigger_3260271; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON species
FROM species_alias
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'species_alias', 'species', 'UNSPECIFIED', 'tax_id', 'tax_id');
--
-- TOC entry 77 (OID 3260272)
-- Name: RI_ConstraintTrigger_3260272; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relation
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 60 (OID 3260273)
-- Name: RI_ConstraintTrigger_3260273; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 61 (OID 3260274)
-- Name: RI_ConstraintTrigger_3260274; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 78 (OID 3260275)
-- Name: RI_ConstraintTrigger_3260275; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relation
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 62 (OID 3260276)
-- Name: RI_ConstraintTrigger_3260276; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 63 (OID 3260277)
-- Name: RI_ConstraintTrigger_3260277; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relation', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 79 (OID 3260278)
-- Name: RI_ConstraintTrigger_3260278; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relation
FROM relationship
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relation', 'relationship', 'UNSPECIFIED', 'type_id', 'type_id');
--
-- TOC entry 58 (OID 3260279)
-- Name: RI_ConstraintTrigger_3260279; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON relationship
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relation', 'relationship', 'UNSPECIFIED', 'type_id', 'type_id');
--
-- TOC entry 59 (OID 3260280)
-- Name: RI_ConstraintTrigger_3260280; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON relationship
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relation', 'relationship', 'UNSPECIFIED', 'type_id', 'type_id');
--
-- TOC entry 80 (OID 3260281)
-- Name: RI_ConstraintTrigger_3260281; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON relation
FROM authority
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'relation', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 42 (OID 3260282)
-- Name: RI_ConstraintTrigger_3260282; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON authority
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'relation', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 43 (OID 3260283)
-- Name: RI_ConstraintTrigger_3260283; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON authority
FROM relation
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'relation', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 81 (OID 3260284)
-- Name: RI_ConstraintTrigger_3260284; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON seq_class
FROM class_list
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'seq_class', 'class_list', 'UNSPECIFIED', 'class_id', 'class_id');
--
-- TOC entry 54 (OID 3260285)
-- Name: RI_ConstraintTrigger_3260285; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON class_list
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'seq_class', 'class_list', 'UNSPECIFIED', 'class_id', 'class_id');
--
-- TOC entry 55 (OID 3260286)
-- Name: RI_ConstraintTrigger_3260286; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON class_list
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'seq_class', 'class_list', 'UNSPECIFIED', 'class_id', 'class_id');
--
-- TOC entry 82 (OID 3260287)
-- Name: RI_ConstraintTrigger_3260287; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON seq_class
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'seq_class', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 64 (OID 3260288)
-- Name: RI_ConstraintTrigger_3260288; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'seq_class', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 65 (OID 3260289)
-- Name: RI_ConstraintTrigger_3260289; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'seq_class', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 83 (OID 3260290)
-- Name: RI_ConstraintTrigger_3260290; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON seq_class
FROM authority
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'seq_class', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 44 (OID 3260291)
-- Name: RI_ConstraintTrigger_3260291; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON authority
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'seq_class', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 45 (OID 3260292)
-- Name: RI_ConstraintTrigger_3260292; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON authority
FROM seq_class
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'seq_class', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 84 (OID 3260293)
-- Name: RI_ConstraintTrigger_3260293; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON seq_species
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'seq_species', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 66 (OID 3260294)
-- Name: RI_ConstraintTrigger_3260294; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM seq_species
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'seq_species', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 67 (OID 3260295)
-- Name: RI_ConstraintTrigger_3260295; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM seq_species
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'seq_species', 'seqname', 'UNSPECIFIED', 'name_id', 'name_id');
--
-- TOC entry 85 (OID 3260296)
-- Name: RI_ConstraintTrigger_3260296; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON seq_species
FROM authority
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'seq_species', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 46 (OID 3260297)
-- Name: RI_ConstraintTrigger_3260297; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON authority
FROM seq_species
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'seq_species', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 47 (OID 3260298)
-- Name: RI_ConstraintTrigger_3260298; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON authority
FROM seq_species
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'seq_species', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 86 (OID 3260299)
-- Name: RI_ConstraintTrigger_3260299; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON mapping
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 68 (OID 3260300)
-- Name: RI_ConstraintTrigger_3260300; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 69 (OID 3260301)
-- Name: RI_ConstraintTrigger_3260301; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name1', 'name_id');
--
-- TOC entry 87 (OID 3260302)
-- Name: RI_ConstraintTrigger_3260302; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON mapping
FROM seqname
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 70 (OID 3260303)
-- Name: RI_ConstraintTrigger_3260303; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON seqname
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 71 (OID 3260304)
-- Name: RI_ConstraintTrigger_3260304; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON seqname
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'mapping', 'seqname', 'UNSPECIFIED', 'name2', 'name_id');
--
-- TOC entry 88 (OID 3260305)
-- Name: RI_ConstraintTrigger_3260305; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON mapping
FROM transform
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'mapping', 'transform', 'UNSPECIFIED', 'trans_id', 'trans_id');
--
-- TOC entry 75 (OID 3260306)
-- Name: RI_ConstraintTrigger_3260306; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON transform
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'mapping', 'transform', 'UNSPECIFIED', 'trans_id', 'trans_id');
--
-- TOC entry 76 (OID 3260307)
-- Name: RI_ConstraintTrigger_3260307; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON transform
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'mapping', 'transform', 'UNSPECIFIED', 'trans_id', 'trans_id');
--
-- TOC entry 89 (OID 3260308)
-- Name: RI_ConstraintTrigger_3260308; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON mapping
FROM authority
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'mapping', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 48 (OID 3260309)
-- Name: RI_ConstraintTrigger_3260309; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON authority
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'mapping', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 49 (OID 3260310)
-- Name: RI_ConstraintTrigger_3260310; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON authority
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'mapping', 'authority', 'UNSPECIFIED', 'authority_id', 'authority_id');
--
-- TOC entry 92 (OID 3260311)
-- Name: RI_ConstraintTrigger_3260311; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER INSERT OR UPDATE ON "location"
FROM mapping
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'location', 'mapping', 'UNSPECIFIED', 'map_id', 'map_id');
--
-- TOC entry 90 (OID 3260312)
-- Name: RI_ConstraintTrigger_3260312; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON mapping
FROM "location"
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del" ('<unnamed>', 'location', 'mapping', 'UNSPECIFIED', 'map_id', 'map_id');
--
-- TOC entry 91 (OID 3260313)
-- Name: RI_ConstraintTrigger_3260313; Type: TRIGGER; Schema: public; Owner: tilfordc
--
CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON mapping
FROM "location"
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('<unnamed>', 'location', 'mapping', 'UNSPECIFIED', 'map_id', 'map_id');
* Re: Bug report
@ 2003-03-21 05:34 Tom Lane <tgl@sss.pgh.pa.us>
parent: Robert E. Bruccoleri <bruc@stone.congenomics.com>
1 sibling, 1 reply; 28+ messages in thread
From: Tom Lane @ 2003-03-21 05:34 UTC (permalink / raw)
To: bruc@acm.org; +Cc: pgsql-bugs
"Robert E. Bruccoleri" <bruc@stone.congenomics.com> writes:
> The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that
> would normally deadlock.
Can't duplicate that here, using either 7.3 branch or CVS tip. You sure
you have a clean build?
regards, tom lane
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2003-03-21 07:14 Neil Conway <neilc@samurai.com>
parent: Robert E. Bruccoleri <bruc@stone.congenomics.com>
1 sibling, 1 reply; 28+ messages in thread
From: Neil Conway @ 2003-03-21 07:14 UTC (permalink / raw)
To: bruc@acm.org; +Cc: pgsql-bugs
On Thu, 2003-03-20 at 19:26, Robert E. Bruccoleri wrote:
> MIPS Pro 7.4 and MIPS Pro 7.3.1.3, 64 bit compilation model.
I've seen some other people having troubles with PostgreSQL compiled
with Mips Pro on IRIX/MIPS -- does the problem persist if you recompile
PostgreSQL with gcc?
Cheers,
Neil
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2003-03-22 04:20 Robert E. Bruccoleri <bruc@stone.congenomics.com>
parent: Neil Conway <neilc@samurai.com>
0 siblings, 0 replies; 28+ messages in thread
From: Robert E. Bruccoleri @ 2003-03-22 04:20 UTC (permalink / raw)
To: neilc@samurai.com; +Cc: bruc@acm.org; pgsql-bugs
Dear Neil,
>
> On Thu, 2003-03-20 at 19:26, Robert E. Bruccoleri wrote:
> > MIPS Pro 7.4 and MIPS Pro 7.3.1.3, 64 bit compilation model.
>
> I've seen some other people having troubles with PostgreSQL compiled
> with Mips Pro on IRIX/MIPS -- does the problem persist if you recompile
> PostgreSQL with gcc?
PostgreSQL does not compile properly with gcc. I've been using
PostgreSQL on Irix/MIPS for about six years -- it's quite stable. This
bug appears to be related to the use of constraints in deadlock
detection, it doesn't look like a compiler problem.
--Bob
+-----------------------------+------------------------------------+
| Robert E. Bruccoleri, Ph.D. | email: bruc@acm.org |
| President, Congenomics Inc. | URL: http://www.congen.com/~bruc |
| P.O. Box 314 | Phone: 609 818 7251 |
| Pennington, NJ 08534 | |
+-----------------------------+------------------------------------+
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2003-03-22 04:24 Robert E. Bruccoleri <bruc@stone.congenomics.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 28+ messages in thread
From: Robert E. Bruccoleri @ 2003-03-22 04:24 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: bruc@acm.org; pgsql-bugs
Dear Tom,
>
>
> "Robert E. Bruccoleri" <bruc@stone.congenomics.com> writes:
> > The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that
> > would normally deadlock.
>
> Can't duplicate that here, using either 7.3 branch or CVS tip. You sure
> you have a clean build?
Oh yes, the regression tests all pass, and we've been using the system
heavily. What's different about this case in our shop is the heavy use
of constraints.
If I gave you access to an SGI running PostgreSQL 7.3.2, would you
be willing to log in and explore the problem "live"? If so, I will set
this up for you.
Regards,
Bob
+-----------------------------+------------------------------------+
| Robert E. Bruccoleri, Ph.D. | email: bruc@acm.org |
| President, Congenomics Inc. | URL: http://www.congen.com/~bruc |
| P.O. Box 314 | Phone: 609 818 7251 |
| Pennington, NJ 08534 | |
+-----------------------------+------------------------------------+
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2003-03-22 04:52 Tom Lane <tgl@sss.pgh.pa.us>
parent: Robert E. Bruccoleri <bruc@stone.congenomics.com>
0 siblings, 1 reply; 28+ messages in thread
From: Tom Lane @ 2003-03-22 04:52 UTC (permalink / raw)
To: bruc@acm.org; +Cc: pgsql-bugs
> If I gave you access to an SGI running PostgreSQL 7.3.2, would you
> be willing to log in and explore the problem "live"?
You bet. Do you have gdb installed?
regards, tom lane
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2003-03-26 00:07 Robert E. Bruccoleri <bruc@stone.congenomics.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 28+ messages in thread
From: Robert E. Bruccoleri @ 2003-03-26 00:07 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: pgsql-bugs
Dear Tom,
>
>
> > If I gave you access to an SGI running PostgreSQL 7.3.2, would you
> > be willing to log in and explore the problem "live"?
>
> You bet. Do you have gdb installed?
Thank you so much.
WRT to gdb, it's not available. However, you can use dbx, SGI's
debugger. It's similar so you should be able to navigate.
We need to discuss the logistics of this. Please call me tomorrow
at 609 818 7251 or please send me your phone number, and I'll call you.
--Bob
+-----------------------------+------------------------------------+
| Robert E. Bruccoleri, Ph.D. | email: bruc@acm.org |
| President, Congenomics Inc. | URL: http://www.congen.com/~bruc |
| P.O. Box 314 | Phone: 609 818 7251 |
| Pennington, NJ 08534 | |
+-----------------------------+------------------------------------+
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug Report
@ 2003-10-07 21:12 Branden R. Williams <brw@brw.net>
0 siblings, 2 replies; 28+ messages in thread
From: Branden R. Williams @ 2003-10-07 21:12 UTC (permalink / raw)
To: pgsql-bugs
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Branden R. Williams
Your email address : brw@brw.net
System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel Pentium
Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.18 ELF
PostgreSQL version (example: PostgreSQL-7.3.4): PostgreSQL-7.3.4
Compiler used (example: gcc 2.95.2) : Your RPM, RH 8.
Please enter a FULL description of your problem:
------------------------------------------------
When using the replace() function, it appears that some of the output is
filtered through a printf variant. If you have legitimate db characters
that are also printf flags, it causes big problems.
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
Place this data inside one field in a db...
/estore/purchase_licenses.asp?numberoflicenses='UNION'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='UNION'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='%22&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='%22&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=9%2c+9%2c+9&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=9%2c+9%2c+9&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='bad_bad_value&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='bad_bad_value&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=bad_bad_value'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=bad_bad_value'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='+OR+'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='+OR+'&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='WHERE&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='WHERE&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=%3B&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses=%3B&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='OR&ID=1& =
/estore/purchase_licenses.asp?numberoflicenses='OR&ID=1& =
Now pretend that you want to filter out various characters, including the
% because %2c is something that printf uses. In my app, I use printf to
parse data that comes from the database, so I need to fix this.
Doing a nested replace, select the field out using the following
commands...
replace(replace(replace(reportresults.data, chr(92), '\'), chr(37),
'%'), chr(9), '') as data
Look at the results and you will notice the select does not look like it
does if you do not filter at all (or have the replaced characters in there
on some lines).
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
You will probably have to filter out any % so that printf does not try to
interpret it.
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-10-08 21:58 Joe Conway <mail@joeconway.com>
parent: Branden R. Williams <brw@brw.net>
1 sibling, 1 reply; 28+ messages in thread
From: Joe Conway @ 2003-10-08 21:58 UTC (permalink / raw)
To: Branden R. Williams <brw@brw.net>; +Cc: pgsql-bugs
Branden R. Williams wrote:
> ============================================================================
> POSTGRESQL BUG REPORT TEMPLATE
> ============================================================================
> Your name : Branden R. Williams
> Your email address : brw@brw.net
> System Configuration
> ---------------------
> Architecture (example: Intel Pentium) : Intel Pentium
> Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.18 ELF
> PostgreSQL version (example: PostgreSQL-7.3.4): PostgreSQL-7.3.4
> Compiler used (example: gcc 2.95.2) : Your RPM, RH 8.
> Please enter a FULL description of your problem:
> ------------------------------------------------
> When using the replace() function, it appears that some of the output is
> filtered through a printf variant. If you have legitimate db characters
> that are also printf flags, it causes big problems.
This was fixed for 7.3.4 (or so I thought); see:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/adt/varlena.c.diff?r1=1.92...
Are you sure you don't have something earlier? Was does
select version();
show?
Joe
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-10-08 22:44 Tom Lane <tgl@sss.pgh.pa.us>
parent: Branden R. Williams <brw@brw.net>
1 sibling, 0 replies; 28+ messages in thread
From: Tom Lane @ 2003-10-08 22:44 UTC (permalink / raw)
To: Branden R. Williams <brw@brw.net>; +Cc: pgsql-bugs
"Branden R. Williams" <brw@brw.net> writes:
> When using the replace() function, it appears that some of the output is
> filtered through a printf variant.
This was fixed as of 7.3.3.
regards, tom lane
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-10-09 00:51 Branden R. Williams <brw@brw.net>
parent: Joe Conway <mail@joeconway.com>
0 siblings, 0 replies; 28+ messages in thread
From: Branden R. Williams @ 2003-10-09 00:51 UTC (permalink / raw)
To: Joe Conway <mail@joeconway.com>; +Cc: pgsql-bugs
Nuts, my sincere apologies on this one. This is the one server in our
entire farm that is not 7.3.4. I'm upgrading right now.
Sorry for the inconvenience!
On Wed, 8 Oct 2003, Joe Conway wrote:
> Branden R. Williams wrote:
> > ============================================================================
> > POSTGRESQL BUG REPORT TEMPLATE
> > ============================================================================
> > Your name : Branden R. Williams
> > Your email address : brw@brw.net
> > System Configuration
> > ---------------------
> > Architecture (example: Intel Pentium) : Intel Pentium
> > Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.18 ELF
> > PostgreSQL version (example: PostgreSQL-7.3.4): PostgreSQL-7.3.4
> > Compiler used (example: gcc 2.95.2) : Your RPM, RH 8.
> > Please enter a FULL description of your problem:
> > ------------------------------------------------
> > When using the replace() function, it appears that some of the output is
> > filtered through a printf variant. If you have legitimate db characters
> > that are also printf flags, it causes big problems.
>
> This was fixed for 7.3.4 (or so I thought); see:
> http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/adt/varlena.c.diff?r1=1.92...
> Are you sure you don't have something earlier? Was does
> select version();
> show?
>
> Joe
>
Fair Winds and Following Seas,
Branden R. Williams, CISSP
<brw@brw.net>
http://www.brw.net/
--
Public Key ID: 0x442E9483 | PGP Keyserver: pgp.mit.edu
Public Key Fingerprint: 6B44 B798 934F 043D C34D 219F D628 FC0E 442E 9483
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug Report
@ 2003-11-21 04:09 Douglas M. Westfall <dougw@net.kent.edu>
0 siblings, 2 replies; 28+ messages in thread
From: Douglas M. Westfall @ 2003-11-21 04:09 UTC (permalink / raw)
To: pgsql-bugs
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to pgsql-ports@postgresql.org.
To report any other bug, fill out the form below and e-mail it to
pgsql-bugs@postgresql.org.
If you not only found the problem but solved it and generated a patch
then e-mail it to pgsql-patches@postgresql.org instead. Please use the
command "diff -c" to generate the patch.
You may also enter a bug report at http://www.postgresql.org/ instead of
e-mail-ing this form.
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Douglas M. Westfall
Your email address : dougw@net.kent.edu
System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel P4 Itanium 2.4
Operating System (example: Linux 2.0.26 ELF) : Linux
2.4.22-1.2087.nptlsmp #1 SMP i686 i686 i386 GNU/Linux (RH9+)
PostgreSQL version (example: PostgreSQL-7.3.4): PostgreSQL-7.3.4
Compiler used (example: gcc 2.95.2) : RH9 using Ximian RUG rpm's ...
update of 19 Nov 2003
Please enter a FULL description of your problem:
------------------------------------------------
1) table contains a valid inet field
2) query works fine in pgsql 7.2 & 7.3
3) query no longer works in pgsql 7.4
select * from <table> where <field> ilike '%<inetvalue>%' ;
fails with:
ERROR: Unable to identify an operator '~~*' for types 'inet' and
'"unknown"'
You will have to retype this query using an explicit cast
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%' order by
ip2_address asc;
CASTing the operator provides no resolution, as it causes syntax errors,
ie:
select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%'::inet
order by ip2_address asc;
returns:
ERROR: invalid INET value '%10.123.252.4%'
AND:
select * from ipaddrs2 where ip2_address ilike CAST('%10.123.252.4% as
inet) order by ip2_address asc;
returns:
ERROR: invalid INET value '%10.123.252.4%'
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
Apparent problem in ilike function dealing with inet values
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-11-23 03:59 Douglas M. Westfall <dougw@net.kent.edu>
parent: Douglas M. Westfall <dougw@net.kent.edu>
1 sibling, 1 reply; 28+ messages in thread
From: Douglas M. Westfall @ 2003-11-23 03:59 UTC (permalink / raw)
To: pgsql-bugs
Yes, I have searched the archives, and searches for 'inet' or 'ilike' or
'inet+ilike' and 'inet&ilike' return 0 results each.
Have I missed something?
Regards,
DougW
On Thu, 2003-11-20 at 23:09, Douglas M. Westfall wrote:
> If PostgreSQL failed to compile on your computer or you found a bug that
> is likely to be specific to one platform then please fill out this form
> and e-mail it to pgsql-ports@postgresql.org.
>
> To report any other bug, fill out the form below and e-mail it to
> pgsql-bugs@postgresql.org.
>
> If you not only found the problem but solved it and generated a patch
> then e-mail it to pgsql-patches@postgresql.org instead. Please use the
> command "diff -c" to generate the patch.
>
> You may also enter a bug report at http://www.postgresql.org/ instead of
> e-mail-ing this form.
>
> ============================================================================
> POSTGRESQL BUG REPORT TEMPLATE
> ============================================================================
>
>
> Your name : Douglas M. Westfall
> Your email address : dougw@net.kent.edu
>
>
> System Configuration
> ---------------------
> Architecture (example: Intel Pentium) : Intel P4 Itanium 2.4
>
> Operating System (example: Linux 2.0.26 ELF) : Linux
> 2.4.22-1.2087.nptlsmp #1 SMP i686 i686 i386 GNU/Linux (RH9+)
>
> PostgreSQL version (example: PostgreSQL-7.3.4): PostgreSQL-7.3.4
>
> Compiler used (example: gcc 2.95.2) : RH9 using Ximian RUG rpm's ...
> update of 19 Nov 2003
>
>
> Please enter a FULL description of your problem:
> ------------------------------------------------
> 1) table contains a valid inet field
> 2) query works fine in pgsql 7.2 & 7.3
> 3) query no longer works in pgsql 7.4
>
> select * from <table> where <field> ilike '%<inetvalue>%' ;
>
> fails with:
> ERROR: Unable to identify an operator '~~*' for types 'inet' and
> '"unknown"'
> You will have to retype this query using an explicit cast
>
>
> Please describe a way to repeat the problem. Please try to provide a
> concise reproducible example, if at all possible:
> ----------------------------------------------------------------------
>
> select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%' order by
> ip2_address asc;
>
> CASTing the operator provides no resolution, as it causes syntax errors,
> ie:
> select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%'::inet
> order by ip2_address asc;
> returns:
> ERROR: invalid INET value '%10.123.252.4%'
> AND:
> select * from ipaddrs2 where ip2_address ilike CAST('%10.123.252.4% as
> inet) order by ip2_address asc;
> returns:
> ERROR: invalid INET value '%10.123.252.4%'
>
> If you know how this problem might be fixed, list the solution below:
> ---------------------------------------------------------------------
>
> Apparent problem in ilike function dealing with inet values
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-11-23 07:54 Stephan Szabo <sszabo@megazone.bigpanda.com>
parent: Douglas M. Westfall <dougw@net.kent.edu>
0 siblings, 0 replies; 28+ messages in thread
From: Stephan Szabo @ 2003-11-23 07:54 UTC (permalink / raw)
To: Douglas M. Westfall <dougw@net.kent.edu>; +Cc: pgsql-bugs
On Sat, 22 Nov 2003, Douglas M. Westfall wrote:
> Yes, I have searched the archives, and searches for 'inet' or 'ilike' or
> 'inet+ilike' and 'inet&ilike' return 0 results each.
>
> Have I missed something?
I believe your problem is that you were relying on a cast from inet to
text (on which ilike is defined) which isn't marked as implicit,
you'd probably want:
select * from <table> where CAST(<field> as text) ilike <pattern>;
> > Please enter a FULL description of your problem:
> > ------------------------------------------------
> > 1) table contains a valid inet field
> > 2) query works fine in pgsql 7.2 & 7.3
> > 3) query no longer works in pgsql 7.4
> >
> > select * from <table> where <field> ilike '%<inetvalue>%' ;
> >
> > fails with:
> > ERROR: Unable to identify an operator '~~*' for types 'inet' and
> > '"unknown"'
> > You will have to retype this query using an explicit cast
> >
> >
> > Please describe a way to repeat the problem. Please try to provide a
> > concise reproducible example, if at all possible:
> > ----------------------------------------------------------------------
> >
> > select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%' order by
> > ip2_address asc;
> >
> > CASTing the operator provides no resolution, as it causes syntax errors,
> > ie:
> > select * from ipaddrs2 where ip2_address ilike '%10.123.252.4%'::inet
> > order by ip2_address asc;
> > returns:
> > ERROR: invalid INET value '%10.123.252.4%'
> > AND:
> > select * from ipaddrs2 where ip2_address ilike CAST('%10.123.252.4% as
> > inet) order by ip2_address asc;
> > returns:
> > ERROR: invalid INET value '%10.123.252.4%'
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2003-11-23 18:43 Tom Lane <tgl@sss.pgh.pa.us>
parent: Douglas M. Westfall <dougw@net.kent.edu>
1 sibling, 0 replies; 28+ messages in thread
From: Tom Lane @ 2003-11-23 18:43 UTC (permalink / raw)
To: Douglas M. Westfall <dougw@net.kent.edu>; +Cc: pgsql-bugs
"Douglas M. Westfall" <dougw@net.kent.edu> writes:
> 1) table contains a valid inet field
> 2) query works fine in pgsql 7.2 & 7.3
> 3) query no longer works in pgsql 7.4
> select * from <table> where <field> ilike '%<inetvalue>%' ;
> ERROR: Unable to identify an operator '~~*' for types 'inet' and '"unknown"'
> You will have to retype this query using an explicit cast
This certainly did not work in 7.3 (in fact, you are quoting the 7.3
spelling of the error message).
There is not and never has been a LIKE operator for inet values; it's
only defined for textual data types. The reason it "worked" in 7.2 was
that 7.2 would implicitly cast the inet value to text for you. In 7.3
we changed a lot of casts to not be implicitly invocable, because of the
potential for unexpected behavior. Personally I'd class this as an
example of exactly the kind of unexpected behavior we meant to
prevent...
Short anser: cast the field value to text.
regards, tom lane
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug report
@ 2004-10-01 21:48 Andrew Grillet <andrew@grillet.co.uk>
0 siblings, 1 reply; 28+ messages in thread
From: Andrew Grillet @ 2004-10-01 21:48 UTC (permalink / raw)
To: pgsql-bugs
Hi
Bug category serious:
The bug report link as www.postgresql.org/bugs/bugs.php is not working.
Original bug I was trying to report is that 7.4.5 builds OK on Freebsd
4.10 and runs fine, but if you try "createlang" (eg to install plpgsql)
it fails because of undefined symbol "downcase_truncate_identifier".
I have tried this on two different systems. In one, the pgsql was a
portupgrade -R, in the other it was built and installed from ports.
Also, unrelated issue:
It would be really nice if the manual .had an example of inserting a
nested query:
is it:
a) INSERT INTO table2 SELECT * from table1;
b) INSERT INTO table2 (SELECT * from table1);
c) INSERT INTO table2 VALUES (SELECT * from table1);
And what if you have a list of columns.
some of us are too stupid to remember, and have to look it up every
time! And there is nothing listed under INSERT or SUBQUERY, and it
takes about 15 mins to look it up!. (Even after using SQL for nearly 20
years :-()
regards
Andrew
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2004-10-01 22:58 Tom Lane <tgl@sss.pgh.pa.us>
parent: Andrew Grillet <andrew@grillet.co.uk>
0 siblings, 0 replies; 28+ messages in thread
From: Tom Lane @ 2004-10-01 22:58 UTC (permalink / raw)
To: andrew@grillet.co.uk; +Cc: pgsql-bugs
Andrew Grillet <andrew@grillet.co.uk> writes:
> Original bug I was trying to report is that 7.4.5 builds OK on Freebsd
> 4.10 and runs fine, but if you try "createlang" (eg to install plpgsql)
> it fails because of undefined symbol "downcase_truncate_identifier".
I think you are trying to load a 7.4 plpgsql into a 7.3 backend.
> It would be really nice if the manual .had an example of inserting a
> nested query:
The fourth example under Examples on the INSERT reference page seems to
respond to this ...
regards, tom lane
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug Report
@ 2005-01-11 11:27 Elvis E. Henriquez A. <elvish@cantv.net>
0 siblings, 1 reply; 28+ messages in thread
From: Elvis E. Henriquez A. @ 2005-01-11 11:27 UTC (permalink / raw)
To: pgsql-bugs
PostgreSQL RC4 Command prompt functions on Windows (Windows 2000
Professional - Spanish with SP4) still displays a message in the format:
could not find a "functionname" to execute when executing a psql, pg_dump,
createdb, createuser and some other functions. They work and do the required
job, but display that message first. Psql even displays it twice.
Another bug is in the ODBC driver included, which has been since the first
beta releases of PostgreSQL 8 and it's that it doesn't handle correctly
Spanish/European characters. The database stores them perfectly, but the
ODBC driver doesn't read them, displaying a "?" mark where an accented
work
or a letter ñ should be, and truncating such word in that place.
When updating, creating or deleting a recordset (through the ODBC driver),
the following error is displayed:
Insufficient base table information for updating or refreshing.
# -2147467259
Elvis E. Henríquez A.
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2005-01-14 14:03 Alvaro Herrera <alvherre@dcc.uchile.cl>
parent: Elvis E. Henriquez A. <elvish@cantv.net>
0 siblings, 1 reply; 28+ messages in thread
From: Alvaro Herrera @ 2005-01-14 14:03 UTC (permalink / raw)
To: Elvis E. Henriquez A. <elvish@cantv.net>; +Cc: pgsql-bugs
On Tue, Jan 11, 2005 at 07:27:44AM -0400, Elvis E. Henriquez A. wrote:
> PostgreSQL RC4 Command prompt functions on Windows (Windows 2000
> Professional - Spanish with SP4) still displays a message in the format:
> could not find a "functionname" to execute when executing a psql, pg_dump,
> createdb, createuser and some other functions. They work and do the required
> job, but display that message first. Psql even displays it twice.
Hmm ... I'm not sure I understand the problem here. Please copy & paste
the exact message and commands executed.
> Another bug is in the ODBC driver included, which has been since the first
> beta releases of PostgreSQL 8 and it's that it doesn't handle correctly
> Spanish/European characters. The database stores them perfectly, but the
> ODBC driver doesn't read them, displaying a "?" mark where an accented
> work or a letter ñ should be, and truncating such word in that place.
Most likely, it's an encoding problem. Do you have client_encoding
correctly set? Is the database using the correct server-side encoding?
Please be aware that a there is a high quality spanish list
(pgsql-es-ayuda); feel free to report there, with details added.
--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
Y dijo Dios: "Que sea Satanás, para que la gente no me culpe de todo a mí."
"Y que hayan abogados, para que la gente no culpe de todo a Satanás"
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug Report
@ 2005-01-15 04:13 Alvaro Herrera <alvherre@dcc.uchile.cl>
parent: Alvaro Herrera <alvherre@dcc.uchile.cl>
0 siblings, 0 replies; 28+ messages in thread
From: Alvaro Herrera @ 2005-01-15 04:13 UTC (permalink / raw)
To: Elvis E. Henriquez A. <elvish@cantv.net>; +Cc: pgsql-bugs
On Fri, Jan 14, 2005 at 09:50:32PM -0400, Elvis E. Henriquez A. wrote:
Hi,
Please keep the copy to the list when replying.
> C:\Documents and Settings\Elvis>psql -h localhost -U postgres -f Update13.sql prueba
> could not find a "psql" to execute
> Password:
> could not find a "psql" to execute
Now that's weird. But I don't think it's a Postgres problem; maybe your
shell is playing some games on you. I don't know a lot about Hasefroch
command line utilities to help you more here.
> About the ODBC problem, I don't think it's an encoding problem.
> My database encoding is sql_ascii, which I'm being using since
> postgresql 7.3.2, and worked perfectly. If I use, for example, pgAdmin
> III or phpPgAdmin, data is perfectly displayed. But when I make a
> select statement through the ODBC driver, using for example Visual
> Basic 6 with ADO, the data seems to be damaged,
I think that's exactly the problem. With SQL_ASCII you should limit
yourself to (7 bit) ASCII characters, or be bitten by Postgres' recoding
capabilities. If you want to use non-ascii characters, you should
declare your database as LATIN1 or LATIN9, or if it's a Hasefroch server
maybe win125x, cp850, whatever. And your client_encoding should be set
to the correct value, so that if there is gonna be character conversion,
the results are what you expect.
--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
^ permalink raw reply [nested|flat] 28+ messages in thread
* bug report
@ 2009-04-03 09:35 n.franken3@kpnplanet.nl
0 siblings, 0 replies; 28+ messages in thread
From: n.franken3@kpnplanet.nl @ 2009-04-03 09:35 UTC (permalink / raw)
To: pgsql-bugs
Sir,
I have changed Antivirus environment from AVG to Avast .
After I have tried to restart my PostgreSQL Server I got 10061 error TCP/IP.
Starting the server triggers err 5 ''Access denied''
After this missfaillure I have uninstalled PostgreSQL 8.3. and then I have tried to riinstall PostgreSQL 8.3 again.
Installation failed caused by this message :
Tried to create a debugger
c:/users/nico/AppData/Local/Temp/bitrock_debug_5204.xml
AVG worked perfect but out of budgetary reasens I had to install a Free Antivirus download Avast.
.Next month I restore former setup AVG AntiVirus and EnterpriseDB.
What to do to work with PostgreSQL 8.3?
Thank You in advance.
N.Franken
The Netherlands.
^ permalink raw reply [nested|flat] 28+ messages in thread
* bug report
@ 2010-10-08 23:13 Bryson Holland <bryson@brysonholland.com>
0 siblings, 1 reply; 28+ messages in thread
From: Bryson Holland @ 2010-10-08 23:13 UTC (permalink / raw)
To: pgsql-bugs
what other information do you need from me to make this useful?
configure: WARNING: uuid.h: present but cannot be compiled
configure: WARNING: uuid.h: check for missing prerequisite headers?
configure: WARNING: uuid.h: see the Autoconf documentation
configure: WARNING: uuid.h: section "Present But Cannot Be Compiled"
configure: WARNING: uuid.h: proceeding with the preprocessor's result
configure: WARNING: uuid.h: in the future, the compiler will take precedence
configure: WARNING: ## ---------------------------------------- ##
configure: WARNING: ## Report this to pgsql-bugs@postgresql.org ##
configure: WARNING: ## ---------------------------------------- ##
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: bug report
@ 2010-10-09 12:06 Peter Eisentraut <peter_e@gmx.net>
parent: Bryson Holland <bryson@brysonholland.com>
0 siblings, 0 replies; 28+ messages in thread
From: Peter Eisentraut @ 2010-10-09 12:06 UTC (permalink / raw)
To: Bryson Holland <bryson@brysonholland.com>; +Cc: pgsql-bugs
On fre, 2010-10-08 at 16:13 -0700, Bryson Holland wrote:
> what other information do you need from me to make this useful?
Platform, version, command line
> configure: WARNING: uuid.h: present but cannot be compiled
> configure: WARNING: uuid.h: check for missing prerequisite headers?
> configure: WARNING: uuid.h: see the Autoconf documentation
> configure: WARNING: uuid.h: section "Present But Cannot Be Compiled"
> configure: WARNING: uuid.h: proceeding with the preprocessor's result
> configure: WARNING: uuid.h: in the future, the compiler will take precedence
> configure: WARNING: ## ---------------------------------------- ##
> configure: WARNING: ## Report this to pgsql-bugs@postgresql.org ##
> configure: WARNING: ## ---------------------------------------- ##
>
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug report
@ 2016-04-28 07:17 Кирковский Александр <alex.kirkouski@gmail.com>
0 siblings, 1 reply; 28+ messages in thread
From: Кирковский Александр @ 2016-04-28 07:17 UTC (permalink / raw)
To: pgsql-bugs
Hi.
There is some pretty strange behavior in "PostgreSQL 9.4.5, compiled by
Visual C++ build 1800, 64-bit".
I have a query (it is attached to the letter - bug.script), that do some
complex calculations using window functions. When the data is stored in
global tables it works just fine (returns 2711 rows), but when data is in
temporary tables the query returns 9076 (some rows are duplicated).
I've checked, this bug is not reproduced in PostgreSQL 9.5.2, but I wonder
if it is coincidence, because the bug is pretty fragile (changing almost any
join leads to normal behavior), and in 9.5.2 the plan is totally different.
I've also attached db backup (plain and tar), plans and non-default settings
in both postgresql versions.
Sincerely yours,
Alexander Kirkouski.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Attachments:
bug.script (application/octet-stream, 6.5K) download
bugdb.backup (application/octet-stream, 357.4K) download
bugdbtar.backup (application/octet-stream, 117.6K) download
p952.settings (application/xml, 7.7K) download
p945.plan (application/octet-stream, 12.7K) download
p952.plan (application/octet-stream, 12.1K) download
p945.settings (application/xml, 8.1K) download
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: Bug report
@ 2016-04-30 00:20 Tom Lane <tgl@sss.pgh.pa.us>
parent: Кирковский Александр <alex.kirkouski@gmail.com>
0 siblings, 0 replies; 28+ messages in thread
From: Tom Lane @ 2016-04-30 00:20 UTC (permalink / raw)
To: Кирковский Александр <alex.kirkouski@gmail.com>; +Cc: pgsql-bugs
=?koi8-r?B?68nSy8/X08vJyiDhzMXL08HOxNI=?= <alex.kirkouski@gmail.com> writes:
> I have a query (it is attached to the letter - bug.script), that do some
> complex calculations using window functions. When the data is stored in
> global tables it works just fine (returns 2711 rows), but when data is in
> temporary tables the query returns 9076 (some rows are duplicated).
I've pushed a fix for this. Many thanks for the reproducible test case!
> I've checked, this bug is not reproduced in PostgreSQL 9.5.2, but I wonder
> if it is coincidence, because the bug is pretty fragile (changing almost any
> join leads to normal behavior), and in 9.5.2 the plan is totally different.
Yeah, it was only accidentally masked in 9.5.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
^ permalink raw reply [nested|flat] 28+ messages in thread
* bug report
@ 2017-09-30 17:49 Lucas O <luke@ottenweb.net>
0 siblings, 1 reply; 28+ messages in thread
From: Lucas O @ 2017-09-30 17:49 UTC (permalink / raw)
To: pgsql-bugs
Message says to report this.
I can run msfconsole just fine, but have never gotten it to connect to the postgresdb.
This is on Mac OSX. I can nmap and see that port 5432 is open on locahost.
Lucas-Ottens-MacBook-Pro:bin lotten$ ./msfconsole
LOG: skipping missing configuration file "/Users/lotten/.msf4/db/postgresql.auto.conf"
LOG: postmaster became multithreaded
DETAIL: Please report this to <pgsql-bugs@postgresql.org>.
pg_ctl: directory "/Users/lotten/.msf4/db" is not a database cluster directory
Found a database at /Users/lotten/.msf4/db, checking to see if it is started
Using database port 5432
Starting database at /Users/lotten/.msf4/db...failed
/opt/metasploit-framework/embedded/framework/msfdb:68:in `readlines': No such file or directory @ rb_sysopen - /Users/lotten/.msf4/db/log (Errno::ENOENT)
from /opt/metasploit-framework/embedded/framework/msfdb:68:in `tail'
from /opt/metasploit-framework/embedded/framework/msfdb:119:in `start_db'
from /opt/metasploit-framework/embedded/framework/msfdb:189:in `init_db'
from /opt/metasploit-framework/embedded/framework/msfdb:309:in `<main>'
[-] Failed to connect to the database: FATAL: role "msfpassword" does not exist
sent while mobile
^ permalink raw reply [nested|flat] 28+ messages in thread
* Re: bug report
@ 2017-09-30 18:16 Tom Lane <tgl@sss.pgh.pa.us>
parent: Lucas O <luke@ottenweb.net>
0 siblings, 0 replies; 28+ messages in thread
From: Tom Lane @ 2017-09-30 18:16 UTC (permalink / raw)
To: Lucas O <luke@ottenweb.net>; +Cc: pgsql-bugs
Lucas O <luke@ottenweb.net> writes:
> LOG: postmaster became multithreaded
> DETAIL: Please report this to <pgsql-bugs@postgresql.org>.
Well, that's not supposed to happen, but you haven't provided anywhere
near enough information for anyone else to duplicate/debug it.
What version of Postgres is this exactly, and what macOS version?
What configure options did you use while building Postgres?
Are you using non-default versions of any libraries? How about
non-default postgresql.conf options?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
^ permalink raw reply [nested|flat] 28+ messages in thread
* Bug Report
@ 2021-11-12 15:25 Tumrong (Tommy) Sakulchaicharoen <tumrong@k2insight.com>
0 siblings, 0 replies; 28+ messages in thread
From: Tumrong (Tommy) Sakulchaicharoen @ 2021-11-12 15:25 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Dear Support,
We freshly installed Postgres version on Amazon Web Service, Then, we did data dump from old Postgres to our new Postgres database. After database is recovered from the old Postgres. We try to the command VACUUM, REINDEX, and ANALYZE tables. The commands run successfully on some table, Some table The ANALYZE table command keep running forever. The ANALYZE command is being run inside pgAdmin 4.
Here is our Postgres and OS version:
PostgreSQL 9.6.22 on x86_64-pc-linux-gnu (Ubuntu 9.6.22-1.pgdg16.04+1),
compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609, 64-bit
Please kindly provide recommendation to fix the problem. The screen shot of ANALYZE command. The table has the total number of records 101183. I check table "pg_stat_all_tables" The column name "last_analyze" has time stamp. Thank you very much for your support.
[cid:af850314-1a1f-4915-a8af-5441cdcedcda]
Best regards,
Tommy
Attachments:
image.png (image/png, 25.0K) download
view image
end of thread, other threads:[~2021-11-12 15:25 UTC | newest]
Thread overview: 28+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-03-21 00:26 Bug report Robert E. Bruccoleri <bruc@stone.congenomics.com>
2003-03-21 05:34 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-03-22 04:24 ` Robert E. Bruccoleri <bruc@stone.congenomics.com>
2003-03-22 04:52 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-03-26 00:07 ` Robert E. Bruccoleri <bruc@stone.congenomics.com>
2003-03-21 07:14 ` Neil Conway <neilc@samurai.com>
2003-03-22 04:20 ` Robert E. Bruccoleri <bruc@stone.congenomics.com>
2003-10-07 21:12 Bug Report Branden R. Williams <brw@brw.net>
2003-10-08 21:58 ` Re: Bug Report Joe Conway <mail@joeconway.com>
2003-10-09 00:51 ` Re: Bug Report Branden R. Williams <brw@brw.net>
2003-10-08 22:44 ` Re: Bug Report Tom Lane <tgl@sss.pgh.pa.us>
2003-11-21 04:09 Bug Report Douglas M. Westfall <dougw@net.kent.edu>
2003-11-23 03:59 ` Re: Bug Report Douglas M. Westfall <dougw@net.kent.edu>
2003-11-23 07:54 ` Re: Bug Report Stephan Szabo <sszabo@megazone.bigpanda.com>
2003-11-23 18:43 ` Re: Bug Report Tom Lane <tgl@sss.pgh.pa.us>
2004-10-01 21:48 Bug report Andrew Grillet <andrew@grillet.co.uk>
2004-10-01 22:58 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-01-11 11:27 Bug Report Elvis E. Henriquez A. <elvish@cantv.net>
2005-01-14 14:03 ` Re: Bug Report Alvaro Herrera <alvherre@dcc.uchile.cl>
2005-01-15 04:13 ` Re: Bug Report Alvaro Herrera <alvherre@dcc.uchile.cl>
2009-04-03 09:35 bug report n.franken3@kpnplanet.nl
2010-10-08 23:13 bug report Bryson Holland <bryson@brysonholland.com>
2010-10-09 12:06 ` Re: bug report Peter Eisentraut <peter_e@gmx.net>
2016-04-28 07:17 Bug report Кирковский Александр <alex.kirkouski@gmail.com>
2016-04-30 00:20 ` Tom Lane <tgl@sss.pgh.pa.us>
2017-09-30 17:49 bug report Lucas O <luke@ottenweb.net>
2017-09-30 18:16 ` Re: bug report Tom Lane <tgl@sss.pgh.pa.us>
2021-11-12 15:25 Bug Report Tumrong (Tommy) Sakulchaicharoen <tumrong@k2insight.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox