Re: [BUGS] signal 11
Sorry, I wasn't sure how much information I should provide. To be thorough:
-Tanya
-
-- TOC Entry ID 18 (OID 16580)
--
-- Name: escalation Type: TABLE Owner: postgres
--
CREATE TABLE "escalation" (
"pathname" character varying(20) NOT NULL,
"level" smallint,
"contact" character varying(20),
"notify_method" character varying(12),
"days" character varying(12),
"hours" character varying(12),
"period" integer,
"num" integer
);
--
-- TOC Entry ID 36 (OID 16611)
--
-- Name: outages Type: TABLE Owner: postgres
--
CREATE TABLE "outages" (
"outage_id" serial NOT NULL,
"machine" character varying(30),
"service" character varying(30),
"status" character varying(12) NOT NULL,
"time" timestamp with time zone,
"owner" character varying(60),
"level" smallint DEFAULT 0 NOT NULL,
"comments" text
);
--
-- TOC Entry ID 40 (OID 16618)
--
-- Name: escalation_link Type: TABLE Owner: postgres
--
CREATE TABLE "escalation_link" (
"machine" character varying(30),
"service" character varying(30),
"status" character varying(12),
"pathname" character varying(20)
);
--
-- TOC Entry ID 41 (OID 16618)
--
-- Name: escalation_link Type: ACL Owner:
--
REVOKE ALL on "escalation_link" from PUBLIC;
GRANT ALL on "escalation_link" to "postgres";
GRANT SELECT on "escalation_link" to "ops2";
GRANT SELECT on "escalation_link" to GROUP "operators";
GRANT ALL on "escalation_link" to GROUP "opsadmins";
--
-- TOC Entry ID 37 (OID 16611)
--
-- Name: outages Type: ACL Owner:
--
REVOKE ALL on "outages" from PUBLIC;
GRANT ALL on "outages" to "postgres";
GRANT INSERT,SELECT,UPDATE,DELETE on "outages" to "ops2";
GRANT INSERT,SELECT on "outages" to GROUP "operators";
GRANT ALL on "outages" to GROUP "opsadmins";
--
-- TOC Entry ID 19 (OID 16580)
--
-- Name: escalation Type: ACL Owner:
--
REVOKE ALL on "escalation" from PUBLIC;
GRANT ALL on "escalation" to "postgres";
GRANT SELECT on "escalation" to "ops2";
GRANT SELECT on "escalation" to GROUP "operators";
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Monday, January 26, 2004 11:59 AM
To: Tanya Mamedalin
Cc: [EMAIL PROTECTED]
Subject: Re: [BUGS] signal 11
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> Possible ways to reproduce the error: Run a multipart query similar to:
> SELECT DISTINCT o.outage_id, o.machine, o.service, o.level, o.comments,
> o2.time, e.num
>FROM outages o, outages o2, escalation e
>WHERE o.outage_id='31009'
>AND e.pathname = (SELECT pathname from escalation_link el
>WHERE el.machine=o.machine AND el.service=o.service)
>AND e.level=o.level
>AND o2.outage_id=o.outage_id
>AND o2.status in ('ALERT','WARN','CRIT','DOWN','UNKNOWN')
>ORDER BY LEVEL DESC LIMIT 1;
This is difficult to do when you have not offered the definitions of the
tables used by the query ...
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] Can not always connect to postmaster. Sometimes get "Connection refused".
Hi, We’re running postgres7.3 on RedHat7.3. The Postgres at boot time is started up from a java (1.2) class that runs the following commands in order: /usr/local/pgsql/bin/pg_ctl -w start -D /var/lib/pgsql -l /var/log/pgsqld.log -o –i /usr/local/pgsql/bin/createdb management . . . As you can tell the postmaster starts up with “-i” option here. ++ In pg_hba.conf we have: local all all trust host all all 127.0.0.1 255.255.255.255 trust host all all 192.168.0.0 255.255.0.0 trust The host IP address is 192.168.55.5 which is in the right subnet. + In postgresql.conf: # # Connection Parameters # tcpip_socket = true #ssl = false max_connections = 64 #superuser_reserved_connections = 2 #port = 5432 #hostname_lookup = false #show_source_port = false #unix_socket_directory = '' #unix_socket_group = '' #unix_socket_permissions = 0777 # octal As you can see tcpip_socket = true ++ Sometimes, after Postgres starts up, when the database clients try to access the db from the localhost, we get the following error: com.solarmetric.kodo.Runtime - com.solarmetric.kodo.runtime.FatalDataStoreException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Any ideas what’s causing postmaster NOT to accept connections some of the time? This problem almost always goes away upon rebooting the machine. Any help is much appreciated. Thanks, -Allen **This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you.**
[BUGS] Why not (OID) in JDeveloper10g?
Hello!, Using JDeveloper10g (ORACLE) I can connect to PostgreSQL database on local machine; BUT! when trying to open informations on table structure, I receive this ERROR MESSAGE * See image attached! * and I'can't access table structure informations (I.E. ftable.fields list)! This is what says Oracle about this same error on his help on line into JDeveloper10g. * Cause: A database failure occurred while trying to generate an object ID (OID) and object reference (REF). When a new row is created on an entity which maps to an Oracle object table, an OID and REF for the new row are generated. This executes a SQL statement like select a.oid, make_ref(, a.oid) ... Somehow, this statement is failing. Action: Check the following: Are you using the right version of Oracle database? Is the table in question an object table? This error normally carries a detail exception from the database, which will give further information about the database failure. Take a look at the detail exception and address the database problem. Do anyone knows why this happen?, is it possible to correct already the problem?, or anyone does encountered the same problem? -- Roberto Della Grotta <> ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] BUG #1069: functions "lower()" and "upper()" not characterset-aware
Tom Lane wrote: "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: the functions "lower()" and "upper()" do not seem to work correctly with ISO_8859_7 values CREATE DATABASE mediagrk WITH TEMPLATE = template0 ENCODING = 'ISO_8859_7'; upper/lower are driven by the database locale, not the encoding. They are presently broken for multi-byte encodings, but I don't think ISO_8859_7 is multi-byte. Well, ISO_8859_7 is not multi-byte, and you're right: I had: LC_COLLATE: C LC_CTYPE: C I tried initdb -E ISO_8859_7 --locale=el_GR data1 and it all worked wonderfully. regards, tom lane Thanks a lot and sorry for the false alarm. Regards Interzone ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] initdb: directory not empty issue
Hi, Don't know if this is a bug or more of a feature request, but here goes: It would appear that by default initdb refuses to configure a database within a directory that already contains files/directories. I understand that this is desirable in most cases. The problem, however, is that this will fail if I am trying to enable a separate filesystem as the data location. It's rather annoying to have to remove a lost+found directory (or other files), init the db, and then remake lost+found (and restore other files). How about a --force flag? I reckon if an admin is willing to type out that, s/he can take the responsibility of the consequences. And of course: fantastic work on release 7.4, and postgreSQL in general! Cordially, Jeff Quinn -- --- Jeffrey Quinn [EMAIL PROTECTED] Shaman | UNIX Journeymanhttp://cs.usfca.edu/~jquinn --- ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] FW: Can not always connect to postmaster. Sometimes get "Connection refused".
Hi, We’re running postgres7.3 on RedHat7.3. The Postgres at boot time is started up from a java (1.2) class that runs the following commands in order: /usr/local/pgsql/bin/pg_ctl -w start -D /var/lib/pgsql -l /var/log/pgsqld.log -o –i /usr/local/pgsql/bin/createdb management . . . As you can tell the postmaster starts up with “-i” option here. ++ In pg_hba.conf we have: local all all trust host all all 127.0.0.1 255.255.255.255 trust host all all 192.168.0.0 255.255.0.0 trust The host IP address is 192.168.55.5 which is in the right subnet. + In postgresql.conf: # # Connection Parameters # tcpip_socket = true #ssl = false max_connections = 64 #superuser_reserved_connections = 2 #port = 5432 #hostname_lookup = false #show_source_port = false #unix_socket_directory = '' #unix_socket_group = '' #unix_socket_permissions = 0777 # octal As you can see tcpip_socket = true ++ Sometimes, after Postgres starts up, when the database clients try to access the db from the localhost, we get the following error: com.solarmetric.kodo.Runtime - com.solarmetric.kodo.runtime.FatalDataStoreException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Any ideas what’s causing postmaster NOT to accept connections some of the time? This problem almost always goes away upon rebooting the machine. Any help is much appreciated. Thanks, -Allen **This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you.**
Re: [BUGS] Why not (OID) in JDeveloper10g?
On Tue, 27 Jan 2004, rdgmus wrote: > Hello!, > Using JDeveloper10g (ORACLE) I can connect to PostgreSQL database > on local machine; > > This is what says Oracle about this same error on his help on line into > JDeveloper10g. > * > Cause: A database failure occurred while trying to generate an object ID (OID) > and object reference (REF). When a new row is created on an entity which maps > to an Oracle object table, an OID and REF for the new row are generated. This > executes a SQL statement like select a.oid, make_ref(, a.oid) ... Somehow, > this statement is failing. Action: Check the following: Are you using the > right version of Oracle database? Is the table in question an object table? > This error normally carries a detail exception from the database, which will > give further information about the database failure. Take a look at the > detail exception and address the database problem. > I'm not sure where you got the idea that oracle's product supports postgresql. If it is supposed to support pg, then the place to file the bug report would be oracle, not here. Because it uses JDBC you can probably get a connection to any database, but that doesn't mean it will actually work. Kris Jurka ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] initdb: directory not empty issue
Jeffrey Quinn <[EMAIL PROTECTED]> writes: > The problem, however, is that this will fail if I am trying to enable a > separate filesystem as the data location. It's rather annoying to have > to remove a lost+found directory (or other files), init the db, and then > remake lost+found (and restore other files). How about a --force > flag? Why not create a /data directory just below the filesystem root, and use that? I believe it's generally considered that root should own filesystem mount points, so using a filesystem root directory directly as the PG data directory seems like bad practice. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] pg_dump: procedural language for function fun_update_tptype_master not found
Hello Sir ! I am using postgresql from last six months. It's running fine. I have no problem with the database.But from last few days i am getting the Error while using the pg_dump to dump the data from my database . the error is given bellow. pg_dump: procedural language for function fun_update_tptype_master not found Waiting for positive response from your side. Regards, Yogesh. Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it!
[BUGS] segfault in psql on x86_64
I am running vanilla Fedora Core 1 - test1 for x86_64 running an update system running kernel 2.4.22-1.2166.nptlsmp The system is a dual opteron pogolinux box with 512M and a IDE RAID 1 from 3ware I downloaded postgresql-7.4.1-1PGDG.src.rpm and built it on the system. (rpmbuild --rebuild ...) and installed the resulting RPM's. The database starts and stops normally on install The psql tool ( as well as createuser/vacuum etc all seg fault) It appears to be faulting on a kerberos call which is odd because I don't use kerberos for anything. Here everything plus a gdb backtrace. [EMAIL PROTECTED] data]# psql Segmentation fault [EMAIL PROTECTED] data]# gdb psql GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (gdb) run Starting program: /usr/bin/psql [Thread debugging using libthread_db enabled] [New Thread 182894073344 (LWP 5363)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 182894073344 (LWP 5363)] 0x003de59010e0 in ?? () from /lib64/tls/libm.so.6 (gdb) bt #0 0x003de59010e0 in ?? () from /lib64/tls/libm.so.6 #1 0x003de6e16c61 in krb5int_initialize_library () from /usr/lib64/libkrb5.so.3 #2 0x003de6e413fb in krb5_init_secure_context () from /usr/lib64/libkrb5.so.3 #3 0x003e2d40844e in pg_krb5_init (PQerrormsg=0x7fbfffda50 " �\177") at fe-auth.c:291 #4 0x003e2d4085a9 in pg_krb5_authname (PQerrormsg=0x3de6f6bc80 "4�") at fe-auth.c:348 #5 0x003e2d408ce1 in fe_getauthname (PQerrormsg=0x7fbfffda50 " �\177") at fe-auth.c:731 #6 0x003e2d40af56 in conninfo_parse (conninfo=0x5320c0 "uA->", errorMessage=0x529db0) at fe-connect.c:2720 #7 0x003e2d408db8 in connectOptions1 (conn=0x529a20, conninfo=0x3de6f6bc80 "4�") at fe-connect.c:328 #8 0x003e2d4091e3 in PQsetdbLogin (pghost=0x0, pgport=0x0, pgoptions=0x0, pgtty=0x0, dbName=0x0, login=0x0, pwd=0x0) at fe-connect.c:541 #9 0x0040a1db in main (argc=1, argv=0x7fbfffe058) at startup.c:183 (gdb) -- Orion Henry <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: [BUGS] FW: Can not always connect to postmaster. Sometimes get "Connection refused".
"Hamedany, Allen" <[EMAIL PROTECTED]> writes: > Sometimes, after Postgres starts up, when the database clients try to > access the db from the localhost, we get the following error: > com.solarmetric.kodo.Runtime - > com.solarmetric.kodo.runtime.FatalDataStoreException: Connection > refused. Check that the hostname and port are correct and that the > postmaster is accepting TCP/IP connections. > Any ideas what's causing postmaster NOT to accept connections some of > the time? Nope, can't tell much from that message. You should look in the postmaster's log to see if it shows any messages at the time that a connection fails like this. (If you are sending the postmaster's stderr to /dev/null, now would be a good time to stop doing that...) If the postmaster doesn't log anything at all when this happens, my conclusion would be that the connection is being rejected at the kernel level (but why would that happen only intermittently??) or that you have a network-level problem. "Connection refused" sounds a bit like a kernel-level issue, FWIW. Another thing to ask about is whether there are any firewall machines between your clients and your database. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] signal 11
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes: > Sorry, I wasn't sure how much information I should provide. To be thorough: Thanks for the background. I tried the query with these table definitions and it didn't crash for me. This may mean that the bug is fixed in 7.4.1, or it might just mean that the problem is not triggered when executing the query with empty tables. Please try 7.4.1 and report back if you still see the failure. regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] pg_dump Error
Hello Sir ! I am really greate ful for Postgresql. It's realy a good open source database. I am using it from six months. But now a days I am getting one strange error while using pg_dump.i.e. while dumping the data from the database. I have created procedural language through CREATELANG command.Procedural language is PLPGSQL.Now i am getting Error while dumping the data in plain text format regarding the procedural language , though i have created the language.Error is given bellow. pg_dump: procedural language for function fun_update_tptype_master not found Waiting for positive respoce from your side. Regards, Yogesh. Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it!
