Re: [BUGS] PosgreSQL is crashing with a signal 11 - Bug?
we got a new coredump of 7.3.7 today. this instance was running on a
freshly installed computer, to eliminate(?) all hardware issues. it's
still the same brand and model, though. the old system has been
running hard disk tests 30+ hours with no errors yet.
the core dump happens at the same place in the code, and this time we
got a complete backtrace:
(gdb) bt
#0 0xb734d07c in memcpy () from /lib/tls/libc.so.6
#1 0x0806bba8 in DataFill (data=0xb7488fff "", tupleDesc=0x82899a0,
value=0x8289980, nulls=0xbfffd3c0 "n\"", infomask=0x8806b04c,
bit=0x8806b04f "ï\001") at heaptuple.c:139
#2 0x0806c3ee in heap_formtuple (tupleDescriptor=0x8279ec0, value=0x8289980,
nulls=0xbfffd3c0 "n\"") at heaptuple.c:623
#3 0x080d1af1 in ExecTargetList (targetlist=0x8278298, nodomains=9,
targettype=0x8279ec0, values=0x8289980, econtext=0x8279a60,
isDone=0xbfffd468) at execQual.c:2230
#4 0x080d1cdb in ExecScan (node=0x827a208, accessMtd=0xbfffd468)
at execScan.c:49
#5 0x080d1d7d in ExecScan (node=0x8278c70, accessMtd=0x80d7c58 )
at execScan.c:146
#6 0x080d7cfb in InitScanRelation (node=0x82899a0, estate=0x8278c70,
scanstate=0xbfffd4c8) at nodeSeqscan.c:162
#7 0x080cfd86 in ExecProcNode (node=0x8289bf8, parent=0x0)
at execProcnode.c:315
#8 0x080cecf3 in ExecutePlan (estate=0x8279c90, plan=0x8278c70,
operation=CMD_SELECT, numberTuples=0, direction=136878496,
destfunc=0x82899c8) at execMain.c:964
#9 0x080ce392 in ExecutorEnd (queryDesc=0x82899a0, estate=0x0)
at execMain.c:223
#10 0x0811d069 in ProcessQuery (parsetree=0x82899c8, plan=0x8278c70,
dest=Remote, completionTag=0xbfffd610 "") at pquery.c:251
#11 0x0811b7ed in pg_exec_query_string (query_string=0xbfffd610, dest=Remote,
parse_context=0x823d610) at postgres.c:844
#12 0x0811c64d in PostgresMain (argc=4, argv=0xbfffd850,
username=0x8238c69 "cerebrum") at postgres.c:2018
#13 0x0810413d in DoBackend (port=0x8238b38) at postmaster.c:2304
#14 0x08103cb2 in BackendStartup (port=0x8238b38) at postmaster.c:1935
#15 0x08102dad in ServerLoop () at postmaster.c:1016
#16 0x081027ea in PostmasterMain (argc=1, argv=0x8220170) at postmaster.c:797
#17 0x080e1234 in main (argc=1, argv=0xbfffe204) at main.c:217
(gdb) print *att[i]
$20 = {attrelid = 0, attname = {
data = "pageunits_total", '\0' ,
alignmentDummy = 1701273968}, atttypid = 1700, attstattarget = -1,
attlen = -1, attnum = 9, attndims = 0, attcacheoff = -1, atttypmod = 393220,
attbyval = 0 '\0', attstorage = 109 'm', attisset = 0 '\0',
attalign = 105 'i', attnotnull = 0 '\0', atthasdef = 0 '\0',
attisdropped = 0 '\0', attislocal = 1 '\001', attinhcount = 0}
(gdb) print i
$21 = 8
(gdb) x/10 value[i]
0xb7190928: 0x2f0b 0x 0x0020 0x0207
0xb7190938: 0x0314 0x01bf913d 0x1012 0x00090020
0xb7190948: 0xef201553 0x0001
the relevant code again is:
if (att[i]->attbyval)
[...]
else if (att[i]->attlen == -1)
[...]
else if (att[i]->attlen == -2)
[...]
else
{
/* fixed-length pass-by-reference */
Assert(att[i]->attlen > 0);
data_length = att[i]->attlen;
===> memcpy(data, DatumGetPointer(value[i]), data_length);
}
(gdb) print data_length
$25 = 788529163
(gdb) print att[i]->attlen
$26 = -1
how can att[i]->attlen possibly change in the interim? but
data_length looks corrupted, too.
(gdb) print *att[i-1]
$27 = {attrelid = 0, attname = {
data = "pageunits_paid", '\0' ,
alignmentDummy = 1701273968}, atttypid = 1700, attstattarget = -1,
attlen = -1, attnum = 8, attndims = 0, attcacheoff = -1, atttypmod = 393220,
attbyval = 0 '\0', attstorage = 109 'm', attisset = 0 '\0',
attalign = 105 'i', attnotnull = 0 '\0', atthasdef = 0 '\0',
attisdropped = 0 '\0', attislocal = 1 '\001', attinhcount = 0}
also:
(gdb) print data
$39 = 0xb7488fff ""
which doesn't seem very aligned for an integer.
(gdb) print data[1]
Cannot access memory at address 0xb7489000
thank you for any insights.
--
Kjetil T.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [BUGS] PosgreSQL is crashing with a signal 11 - Bug?
Kjetil Torgrim Homme <[EMAIL PROTECTED]> writes: > how can att[i]->attlen possibly change in the interim? but > data_length looks corrupted, too. Unless you compiled with no optimization at all (-O0), the compiler would likely fold the identical memcpy() calls in the different if-branches together. So I wouldn't put too much stock in the reported line number. It does seem striking that a 0x2f got dumped into the high byte of the length word in both cases. Have you checked to see what the page-on-disk looks like? I'd be interested to know if the offset of the damaged byte within the page is again 0x0fff. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] BUG #1249: pg_restore doesnt handle restoring databases not created as a superuser
The following bug has been logged online: Bug reference: 1249 Logged by: William Schaub Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.3 Operating system: Slackware 10 (Linux 2.4.27) Description:pg_restore doesnt handle restoring databases not created as a superuser Details: PostgreSQL 7.4.5 (and possibly many versions before) When restoring databases with pg_restore with the -C option it will connect to template1, set authorization to the user that created the database and then reconnect as the user that created the database to the new database. this is where the trouble starts, from here on it trys to set authorization back to the superuser to do grant and revoke. this will cause the restore to fail. I have prepared a patch to force reconnects to be done as the superuser specified in the -S option if -S if given, otherwise the current behavior is used Since pg_restore seems to use set authorization to go back to the database owner before it creates any objects my patch seems safe to me, but i would like to know if it causes problems elseware. it can be found at http://talon.home.cosmic-cow.net/pg_restore.patch By the way your web form doesnt list 7.4.5 as an available version in the PostgreSQL version drop down list. ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] BUG #1250: compilation fails in src/backend/storage/lmgr/s_lock.c
The following bug has been logged online: Bug reference: 1250 Logged by: Aidan Dixon Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Sun/Solaris9/64bit Description:compilation fails in src/backend/storage/lmgr/s_lock.c Details: Compiler: SUNWspro (Forte Developer 7) cc The code in s_lock.c uses a ".seg" directive where ".section" seems to be in vogue, judging from the output of "cc -S" for a simple "hello world" type program. Build output: make[4]: Entering directory `/share/build/postgresql-8.0.0beta2/src/backend/storage/lmgr' /opt/SUNWspro/bin/cc -xarch=v9 -O -Xa -O -v -I../../../../src/include -I/soft-dist/local/include -c -o s_lock.o s_lock.c "s_lock.c", line 228: warning: asm() statement disables optimization within function cg error (as) : "s_lock.c", line 228 : unknown opcode ".segment" cc: cg failed for s_lock.c make[4]: *** [s_lock.o] Error 2 make[4]: Leaving directory `/share/build/postgresql-8.0.0beta2/src/backend/storage/lmgr' make[3]: *** [lmgr-recursive] Error 2 make[3]: Leaving directory `/share/build/postgresql-8.0.0beta2/src/backend/storage' make[2]: *** [storage-recursive] Error 2 make[2]: Leaving directory `/share/build/postgresql-8.0.0beta2/src/backend' make[1]: *** [all] Error 2 make[1]: Leaving directory `/share/build/postgresql-8.0.0beta2/src' make: *** [all] Error 2 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] BUG #1249: pg_restore doesnt handle restoring databases not created as a superuser
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > When restoring databases with pg_restore with the -C > option it will connect to template1, set authorization to > the user that created the database and then reconnect > as the user that created the database to the new database. this is where the > trouble starts, from here on > it trys to set authorization back to the superuser to > do grant and revoke. this will cause the restore to fail. Hmm. This is still broken in CVS tip, but I think the correct solution is just to replace "\connect db user" with "\connect db" everywhere. This will retain the starting real user authentication throughout the restore process. We have completely abandoned use of \connect to change authorization, and this seems just an unintentional hangover from the old way. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #1250: compilation fails in src/backend/storage/lmgr/s_lock.c
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > The code in s_lock.c uses a ".seg" directive where ".section" seems to be > in vogue, judging from the output of "cc -S" for a simple "hello world" type > program. Hmm. So how can we distinguish your version of Solaris from the ones that want ".seg"? regards, tom lane ---(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] problems with OS X and beta 2
Did I miss something that I should so to make 8.0beta2 for Mac OS X. I read the README and install and I see no specific instructions for OS X. Here is the info where the make fails. OS X 10.3.5 gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1666) What else can I send to you? Ted gcc -no-cpp-precomp -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -L../../src/portaccess/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.o commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o main/SUBSYS.o nodes/SUBSYS.o optimizer/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o regex/SUBSYS.o rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o utils/SUBSYS.o ../../src/timezone/SUBSYS.o -lpgport -lz -lreadline -lresolv -ldl -lm -o postgres ld: utils/SUBSYS.o r_symbolnum (58148) field of external relocation entry 1076 in section (__DATA,__const) out of range make[2]: *** [postgres] Error 1 make[1]: *** [all] Error 2 make: *** [all] Error 2 ___ Do you Yahoo!? Shop for Back-to-School deals on Yahoo! Shopping. http://shopping.yahoo.com/backtoschool ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] problems with OS X and beta 2
Theodore Petrosky <[EMAIL PROTECTED]> writes: > Did I miss something that I should so to make 8.0beta2 > for Mac OS X. Last time I tried it (which was a couple weeks back), our CVS tip built perfectly cleanly on OS X. Other people report success too, modulo that silly minus-zero bit in one regression test. Did you use some unusual configure options? regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] problems with OS X and beta 2
I downloaded the beta 2 source, ./configure --with-rendezvous make no other configurations... I did this same configuration on the beta 1 and it was fine. (other than a make check that we had to add an env line..) I am going to try again by throwing away the folder that starting fresh... Ted --- Tom Lane <[EMAIL PROTECTED]> wrote: > Theodore Petrosky <[EMAIL PROTECTED]> writes: > > Did I miss something that I should so to make > 8.0beta2 > > for Mac OS X. > > Last time I tried it (which was a couple weeks > back), our CVS tip built > perfectly cleanly on OS X. Other people report > success too, modulo that > silly minus-zero bit in one regression test. > > Did you use some unusual configure options? > > regards, tom lane > __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] problems with OS X and beta 2
How's this one... I realized that the machine I was testing on was running '[EMAIL PROTECTED]'.. so I quit it.. Lo and behold beta 2 compiled and made (with make check) just fine. Thanks Ted --- Tom Lane <[EMAIL PROTECTED]> wrote: > Theodore Petrosky <[EMAIL PROTECTED]> writes: > > Did I miss something that I should so to make > 8.0beta2 > > for Mac OS X. > > Last time I tried it (which was a couple weeks > back), our CVS tip built > perfectly cleanly on OS X. Other people report > success too, modulo that > silly minus-zero bit in one regression test. > > Did you use some unusual configure options? > > regards, tom lane > __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] vacuum problem
Got something really odd happening here.
Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat linux
system... app does a heavy loop of a prepared UPDATE, then Commit, 1s
of times. the table has a few columns, nothing fancy at all.On our
Redhat Enterprise 2.1 server (dual xeon, 3GB ram, etc), I can't vacuum the
table it generates, it won't free the 'dead' rows...
$ vacuumdb -f -d test -t test -v
INFO: vacuuming "public.test"
INFO: "test": found 0 removable, 373553 nonremovable row versions in 3492
pages
DETAIL: 373533 dead row versions cannot be removed yet.
Nonremovable row versions range from 72 to 72 bytes long.
There were 0 unused item pointers.
Total free space (including removable row versions) is 146596 bytes.
0 pages are or will become empty, including 0 at the end of the table.
1 pages containing 6956 free bytes are potential move destinations.
CPU 0.05s/0.37u sec elapsed 0.41 sec.
INFO: index "test_pkey" now contains 373553 row versions in 1305 pages
DETAIL: 0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: "test": moved 0 row versions, truncated 3492 to 3492 pages
DETAIL: CPU 0.00s/0.00u sec elapsed 0.00 sec.
VACUUM
yet, on an otherwise identical RH Linux 8 system (same java, same app, same
postgres version), it works fine. vacuum gets the free space, I don't even
have to use -f
there are no other connections to this database. It doesn't matter if the
app is still running or not (on the RHL8 system, I can vacuum it while the
app is running, and the space is freed immediately, and the app returns to
full speed, while on the RHEL2.1 system, I can't vacuum it any which ways,
app running or not).
now, if I STOP the postgres server process, and restart it, THEN I can
vacuum it, but thats not acceptible to my actual application, its a 24/7
data extraction process.
we *have* to use RHEL2.1 for this app due to some 3rd party vendor crud
thats only supported there (had glibc problems on RHEL3 with this crudware
which couldn't be resolved by the libc-compatible libraries)
box that works...
$ uname -a
Linux svxeon1 2.4.20-28.8smp #1 SMP Thu Dec 18 12:25:21 EST 2003 i686 i686
i386 GNU/Linux
box that don't work...
$ uname -a
Linux svxeon2.netsys.stsv.seagate.com 2.4.9-e.43enterprise #1 SMP Tue Jun 29
13:57:26 EDT 2004 i686 unknown
And, finally, here's the schema for the test case that shows this problem...
CREATE TABLE test
(
subject varchar(128) NOT NULL,
seq int4 NOT NULL,
reset_time varchar(32) NOT NULL,
CONSTRAINT test_pkey PRIMARY KEY (subject)
)
WITH OIDS;
and, here's the java app (compiled and run with Sun JRE 1.4.2_something)..
(invoked with command: java -cp . PGTest -r 20 -l 50 -c 4000
//package JavaDBI;
//import Flags;
import java.io.*;
import java.sql.*;
public class PGTest
{
public static void main(String[] args)
{
int rowCnt = 20, loopCnt = 50, cycle = 4000, delay = 0;
try {
Connection con_;
String driver_;
Class.forName( "org.postgresql.Driver" );
con_ = DriverManager.getConnection(
"jdbc:postgresql://localhost:5432/test", "test", "test");
PreparedStatement tstStat, updStmt, insStmt, delStmt;
tstStat = con_.prepareStatement("SELECT subject, seq, reset_time FROM
test");
insStmt = con_.prepareStatement("INSERT INTO test VALUES (?,?,?)");
updStmt = con_.prepareStatement("UPDATE test SET seq = ?, reset_time =
? WHERE subject = ?");
delStmt = con_.prepareStatement("DELETE FROM test");
ResultSet rs1_;
Timestamp ts1;
java.util.Date dt1 , dt2, st1, st2;
st1 = new java.util.Date();
dt1 = new java.util.Date();
ts1 = new Timestamp(dt1.getTime() );
rs1_ = tstStat.executeQuery();
System.out.println( "PGTest App" );
/*
while (rs1_.next())
{
System.out.println("-row read-");
System.out.println("control_id:"+rs1_.getString(1));
}
rs1_.close();
System.out.println( "Read from db");
*/
delStmt.execute();
char tmp = 'A';
String[] rowS = new String[rowCnt];
for (int j = 0; j < rowCnt; j++ )
{
rowS[j] = Character.toString(tmp);
insStmt.setString(1, rowS[j]);
insStmt.setInt(2,0);
insStmt.setString(3, dt1.toString());
insStmt.execute();
tmp++;
}
con_.commit();
for (int h = 0; h < cycle; h++ )
{
dt1 = new java.util.Date();
for (int j = 0; j < loopCnt; j++ )
{
for (int i = 0; i < rowCnt; i++ )
{
updStmt.setInt(1, i);
updStmt.setString(2, dt1.toString() );
updStmt.setString(3, rowS[i]);
updStmt.execute();
con_.commit();
//System.out.println( i );
if (delay > 0)
{
try {
Thread.sleep(delay); // 100 ms sleep
} catch (Exception ex) {
System.out.printl
[BUGS] bug-report-template
POSTGRESQL BUG REPORT TEMPLATE Your name : Ralf Burger Your email address : [EMAIL PROTECTED] System Configuration - Architecture (example: Intel Pentium) : Intel Pentium Operating System (example: Linux 2.4.18) : 2.6.6 PostgreSQL version (example: PostgreSQL-8.0) : PostgreSQL-8.0 beta2 Compiler used (example: gcc 2.95.2) : 2.95.3 Please enter a FULL description of your problem: I am testing beta1 since about 2 weeks - it was working fine. After an update to beta2, I was unable to start the postmaster. So I pg_dumped it all and made a new initdb. The postmaster is now running, but psql does not work: ./postgresql-8.0.0beta2/bin/psql template1 ./postgresql-8.0.0beta2/bin/psql: error while loading shared libraries: ./postgresql-8.0.0beta2/bin/psql: undefined symbol: PQserverVersion So I made the restore basics (database/user-creation) with psql from beta1 and then a restore of the data. The rest of the program seems to work. Applications are running. Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: -- the configs of beta1 and beta2 are the same. the error only occurs, when an existing table is given: [EMAIL PROTECTED]:~ > ./bin/psql psql: FATAL: database "postgres" does not exist [EMAIL PROTECTED]:~ > ./bin/psql template1 ./bin/psql: error while loading shared libraries: ./bin/psql: undefined symbol: PQserverVersion here ist the ldd-output ./postgresql-8.0.0beta2 # ldd ./bin/psql libpq.so.3 => /usr/local/pgsql/lib/libpq.so.3 (0x4001a000) libz.so.1 => /usr/lib/libz.so.1 (0x40043000) libreadline.so.4 => /usr/local/lib/libreadline.so.4 (0x40053000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0x4007a000) libcrypt.so.1 => //lib/libcrypt.so.1 (0x400bb000) libresolv.so.2 => //lib/libresolv.so.2 (0x400ea000) libnsl.so.1 => //lib/libnsl.so.1 (0x400fc000) libdl.so.2 => //lib/libdl.so.2 (0x40112000) libm.so.6 => //lib/libm.so.6 (0x40116000) libc.so.6 => //lib/libc.so.6 (0x40145000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) best regards ralf ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] Error installing on Windows
Here are the steps I am taking during the install of postgresql-8.0-beta1-20040809.msi: Screen 1 (warning): next Screen 2 (license) next Screen 3 (options) leave default next Screen 4 (service config) Service ID: pgsql-8.0-beta1 Service Name: PostgreSQL Database Server 8.0-beta1 Account name: postgres Account password: pg Verify password: pg next Screen 5 (Initialise database cluster) Locale : English Encoding: Unicode Superuser name: postgres Password: postgres Password: postgres next Screen 6 (enable procedural languages) PL/pgsql next Screen 7 (ready to install) next Screen 8 Runs for about 0.1 secs, then: Fatal Error: Installation ended prematurely because of an error. My machine is running Japanese Windows XP. If you need any more information, please let me know. David ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] Failed to connect to database. Procedural languages files are installed,but are not activated in any database.
Noted error appears on windows XP, Serice Pack 1 with postgresql 8.0 beta 1 using the installer. After that, connection attempts via psql end with psql: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. Looking at Service Control Panel, Postgresql is running , within the data directory a PID-File is sitting quietly. The owner of all files within data/ and subdirectories is "postgres" also pg_admin fails with the same error. I was running 7.x pre beta on WIN32 before on the same computer. What can I change to make it work or to help diagnose the problem any further? -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] "make check" failure on 8.0 b2
System: Mac OS X 10.3.5 Pg: 8.0.0 b2 type_sanity ... ok opr_sanity ... ok test geometry ... FAILED test horology ... ok test insert ... ok test create_function_1... ok === 1 of 96 tests failed. === *** ./expected/geometry.out Fri Oct 31 21:07:07 2003 --- ./results/geometry.out Sat Sep 4 23:32:07 2004 *** *** 117,123 | (5.1,34.5) | [(1,2),(3,4)] | (3,4) | (-5,-12) | [(1,2),(3,4)] | (1,2) | (10,10)| [(1,2),(3,4)] | (3,4) ! | (0,0) | [(0,0),(6,6)] | (-0,0) | (-10,0)| [(0,0),(6,6)] | (0,0) | (-3,4) | [(0,0),(6,6)] | (0.5,0.5) | (5.1,34.5) | [(0,0),(6,6)] | (6,6) --- 117,123 | (5.1,34.5) | [(1,2),(3,4)] | (3,4) | (-5,-12) | [(1,2),(3,4)] | (1,2) | (10,10)| [(1,2),(3,4)] | (3,4) ! | (0,0) | [(0,0),(6,6)] | (0,0) | (-10,0)| [(0,0),(6,6)] | (0,0) | (-3,4) | [(0,0),(6,6)] | (0.5,0.5) | (5.1,34.5) | [(0,0),(6,6)] | (6,6) == ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] vacuum problem
"John R Pierce" <[EMAIL PROTECTED]> writes: > Got something really odd happening here. > Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat linux > system... app does a heavy loop of a prepared UPDATE, then Commit, 1s > of times. the table has a few columns, nothing fancy at all.On our > Redhat Enterprise 2.1 server (dual xeon, 3GB ram, etc), I can't vacuum the > table it generates, it won't free the 'dead' rows... You've got some background client holding a transaction open. Or else the test program isn't really committing when you think it is. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] bug-report-template
Ralf Burger <[EMAIL PROTECTED]> writes: > ./postgresql-8.0.0beta2/bin/psql template1 > ./postgresql-8.0.0beta2/bin/psql: error while loading shared libraries: > ./postgresql-8.0.0beta2/bin/psql: undefined symbol: PQserverVersion You're linking against an old (pre-8.0) libpq. Check your ldconfig search path. regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] vacuum problem
"John R Pierce" <[EMAIL PROTECTED]> writes: Got something really odd happening here. Simple test program, in java, with jdbc, postgres 7.4.5, on a redhat linux system... app does a heavy loop of a prepared UPDATE, then Commit, 1s of times. the table has a few columns, nothing fancy at all.On our Redhat Enterprise 2.1 server (dual xeon, 3GB ram, etc), I can't vacuum the table it generates, it won't free the 'dead' rows... You've got some background client holding a transaction open. Or else the test program isn't really committing when you think it is. there are no background programs. I've done all the usual checking of `ps' outputs looking for such. in the test case I mailed to this list, I had created a standalone database with one table, and run the test program directly against it. *HOWEVER*... About an hour after mailing that, I realized that the buggy RHEL2.1 system was running with Intel Hyperthreading enabled (so it appeared as 4 CPUs) while the no-problems RH8.0 system had hyperthreading enabled (we'd previously been benchmarking some multithreaded stuff both ways). So, its *just* possible that the earlier RHEL2.1 (kernel 2.4.9-e.43enterprise) had issues which the later RH8 (2.4.20-28.8smp) were resolved.I'll not be able to test this hypothesis until monday morning. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] Mail Delivery (failure signup@mail.efax.com)
Hello, Thank you for contacting eFax.com. The e-mail address [EMAIL PROTECTED] is used solely for the sending of signup confirmations to eFax Free subscribers. Messages sent to [EMAIL PROTECTED] trigger this automated reply and are not read by our Customer Service team. If your message was intended for the eFax Customer Service team, please visit http://www.efax.com/help to search for an answer to your question or to submit an e-mail inquiry. Sincerely, eFax.com Support Team ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] Permissions problem with sequences
There is, however, an ownership problem with restoring sequences in 8.0.0beta. In 7.4.5, for example, pg_dump issues a SET SESSION AUTHORIZATION command and then creates a table, so implicitly-created sequences are restored with the correct ownership. In 8.0.0beta2, however, pg_dump doesn't issue SET SESSION AUTHORIZATION but rather creates a table and then issues ALTER TABLE ... OWNER TO. Oer. I'd better look at that :( Yeah, we still need to find a solution for that. That was a known problem? No-one had told me! > I'd prefer not to back out the ALTER OWNER TO changes, but I will if nothing else presents itself. I'd say that the OWNER TO mode fixes many more bugs than it created, plus they can always dump in the old way with a command line switch. However, of course the best thing is to just fix it, which I guess I'll have a crack at... Chris ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] Permissions problem with sequences
However, of course the best thing is to just fix it, which I guess I'll have a crack at... Given that pg_dump does put out GRANT/REVOKE operations on the sequence, it's certainly aware that the sequence exists. I suspect this is just a fixable bug (ie, suppression of output of the sequence CREATE command is being done at the wrong place). Hrm. This seems to be a bug introduced when I moved the OWNER TO commands to be dumped after each object's definition is dumped, instead of just before their ACL is dumped. The problem is that although the SERIAL sequence has an ACL, it has no object, so it never has an OWNER TO command dumped. I'm trying to think of the solution here. I guess we can move the OWNER TO commands to be dumped in the ACL phase, or we can make a special exception for serial sequences. Also, are there any other objects that are going to have this problem? Off the top of my head it's only serial sequences. What's the best solution? I guess we have to put them back on the acl_pass? Chris ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] BUG #1240: memory leak in JDBC driver build 215
Fabien COELHO schrieb:
328 [main] DEBUG com.mosaicag.rwa.dbutil.standard.DefaultCsvExport -
executing SQL-Stmt: SELECT * FROM transaction WHERE transaction_date >=
to_timestamp('01.01.2002', 'DD.MM.') AND transaction_date <
to_timestamp('01.01.2003', 'DD.MM.')
java.lang.OutOfMemoryError
Exception in thread "main"
Maybe the JDBC drivier tries to allocate the whole result of the query?
If so, it is not a memory leak, it's a big memory need;-)
You might try using a cursor manually (well, if it is the problem,
then it just shows that jdbc should do it by default).
Using a cursor avoids the out of memory error. I used:
stmt.setFetchSize(1000);
after creation of the statement now.
Thanks, that helped. But for me this behaviour is still a bug.
--
Roland Walter
MOSAIC SOFTWARE AG
Telefon: 02225/882-411 Fax: 02225/882-201
http://www.mosaic-ag.com
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [PATCHES] [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1
> > [ fix broken CHECK_FOR_INTERRUPTS macro ] > > Applied. I see how this might change detection of > statement_timeout, but I do not actually see what it's got to > do with deadlock detection. > In the deadlock situation the process that needs to wake up > is going to be blocked on a semaphore, and so it's not going > to be executing CHECK_FOR_INTERRUPTS at all. How does this > fix that case? It doesn't. This is why the second version of the patch was required, per http://archives.postgresql.org/pgsql-patches/2004-09/msg00039.php. It even specifically says this is so it fixes the deadlock issues and not just statement_timeout :-) //Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Cannot to connect.
Hi there! I just installed PostgresSQL 8 beta1 for Windows ( I have WinXP ). I launched pgAdmin III and created one test DB. So, it was created. Then, I launch my Zend Studio and tryed to connect to this new test DB using next code to check connection: It doesn't work. In the php.ini I uncomment line extension=php_pgsql.dll I have php 4.3.7 and I restart Apache, but it still does not work. I don't understand what I need to do else. Could you help me? -- Sincerely, Dmitry Shirokovskiy. Web-developer of 1ADW Co. www.1adw.com RUSSIA ---(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
Re: [BUGS] PosgreSQL is crashing with a signal 11 - Bug?
[Tom Lane]: > > This evidently corresponds to data starting at offset 0ffc on the > disk page (the last few bytes of the gdb output match the start of > tuple 43, which is in the next higher part of the page --- note > that the bytes are being printed in opposite orders by pg_filedump > and gdb). So somehow, the byte at page offset 0fff got changed > from 00 to 2f in memory, though not on disk. indeed interesting. IMHO 0x0fff sounds more like a write to -1 (relative to the next page) than a random memory error. > If you still have the core dump, would you look at the area > surrounding address 3054556648 and see if there are any other > discrepancies between that and what is on disk? I can't see any further discrepancies: (gdb) x/20 3054556572 0xb610d59c: 0x020c6172 0x 0x 0x00ae 0xb610d5ac: 0x0006002c 0x2f1c0913 0x0404b70c 0x000c 0xb610d5bc: 0x0004 0x6948 0x000c 0x0003 0xb610d5cc: 0x8196 0x000c 0x0003 0x0210 0xb610d5dc: 0x000c 0x0002 0x3012 0x2f0c > 0fb0: 72610c02 ae00 ra.. > 0fc0: 2c000600 13091c2f 0cb70404 0c00 ,../ > 0fd0: 0400 4869 0c00 0300 ..Hi > 0fe0: 9681 0c00 0300 1002 > 0ff0: 0c00 0200 1230 0c00 ...0 > 1000: 0200 1730...0 thank you for your tremendous assistance! -- Kjetil T. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] New PostgreSQL questions...
Hello, I've been testing PostgreSQL v8.0 on my Win2000 machine and it seems pretty stout. However, I have come across some issues that concern me: 1. All earlier versions of PostgreSQL are able to be editted via an ssh Shell or some other Unix-based platform. But when I try to edit any of my data, the only way to edit it is through pgAdmin. I know this may be because I'm running PostgreSQL on my personal machine with no Unix platform, but is there some way, or is a version of a Unix platform included on this latest version? (this is just for all of us who still prefer doing a CREATE TABLE to a point, click, and copy through a wizard.) 2. Is there a way to replicate databases across different servers? One of the positive things that I found with SQL Server 2000 (forgive me) is that it has a pretty good interface, both GUI and backend, for allowing replication. I know that a few different groups are already working on this, but I would like to find out if this functionality is included on this new version of PostgreSQL. 3. Is there a way to cluster servers? Again, taking a page from SQL Server, clustering allows some good functions which help in maintaining that server access is almost completely constant. From keeping up with GBorg, I know that this, too, has been considered by other groups. I'm just not sure if this has been created for this new version. Just a few concerns from an IT guy. Thanks, Chari Clark Database Administrator National Background Data, LLC (352)629-9913 [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] The server closes connetion without reason -3.
This is the last log file Postgresbug.rar Description: Binary data ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1242: Major bug in pgSQL
Thank you very much for a quick answer. Here is our situation:
Query:
select cmax, cmin, xmax, xmin, ctid, oid, *
from unitcontainer where unitcontainername = 'Track';
Result:
oid id_unitcontainerid_basecomb id_unitcontainertype
id_userinstance
unitcontainername
16.995.030 10.464 1.009 1 1.063
'Track'
cmax 102, cmin 126761922, xmax 126761922, xmin 121168748, ctid (84,107)
so, only ONE row. "unitcontainername" has an unique index ("index_12"). Here
is the result for the following query:
Query:
reindex index index_12;
Result:
ERROR: could not create unique index
DETAIL: Table contains duplicated values.
Unable to reindex as well :(.
Now comes the most interesting part.
Query:
select cmax, cmin, xmax, xmin, ctid, oid, * from ds_unitcontainer where oid
= 16995030
Result:
oid id_unitcontainerid_unitcontainertypeid_userinstance
unitcontainername
16.995.030 10.464 1 1.063
'Track'
cmax 121457766, cmin 21, xmax 121168748, xmin 121168748, ctid (83,79)
16.995.030 10.464 1 1.063
'Track'
cmax 102, cmin 126761922, xmax 126761922, xmin 121168748, ctid (84,107)
Now we get TWO rows! The most astonishing thing about it - there are whole 3
uniqueness violations:
1) primary key violation for "id_unitcontainer"
2) unique index violation for "unitcontainername"
3) the most "crazy" one - for "oid" !
Please let us know, what we can do to fix this kind of problems, reindexing
seems to be impossible too :(:( ... Thank you very much !
> Gaetano Mendola <[EMAIL PROTECTED]> writes:
> > When you are experiencing this show us the result of this query:
> > select cmax, cmin, xmax, xmin, * from where ;
>
> Also, please, the ctid and oid columns (but leave out oid if you made
> the table WITHOUT OIDS).
>
> Also, if the condition is one that will normally use an index, try
> the same query with and without "set enable_indexscan = off". It
> could be that a corrupted index would cause the query to visit the
> same rows multiple times (or miss rows!).
>
> It might be a good idea to REINDEX the primary-key index on the table,
> but I would counsel not doing so until we have more data on what's
> happening. If the problem is index corruption then REINDEX would
> destroy all the evidence ...
>
> regards, tom lane
>
>
---(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] The server closes connetion without reason - 2.
This is the socond message (holds logs) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] Results of 8.0.0 beta 2 on Red Hat Advanced Server 2.1 x86
Thought you might like to know: Red Hat Advanced Server 2.1 (based on Red Hat 7.2) on an HP DL380 dual Xeon x86 server Linux 2.4.9-e.41enterprise #1 SMP Wed Jun 16 23:33:07 EDT 2004 i686 unknown gcc version 2.96 2731 (Red Hat Linux 7.2 2.96-128.7.2) glibc-2.2.4-32.15 ./configure make make check All tests PASSED ./configure --enable-thread-safety --with-pam --with-java --with-openssl make make check All tests PASSED We use Postgresql daily, we store a database of over 12 million rows and everything hums along nicely. Keep up the good work. -- Stuart Stock Dresdner Kleinwort Wasserstein (Japan) Ltd. The information contained herein is confidential and is intended solely for the addressee. Access by any other party is unauthorised without the express written permission of the sender. If you are not the intended recipient, please contact the sender either via the company switchboard on +44 (0)20 7623 8000, or via e-mail return. If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] 8.0 beta service won't start
Hi, We’ve been using Postgres for about a year. I recently installed the beta 8.0 Windows version on my XP laptop. It worked fine for about a week, but now the service will not start. Here’s the message I receive: Any ideas? Michael Hornick Insurance Systems Inc. [EMAIL PROTECTED] Free: 877-777-2231 Office: 416-249-2260 ext. 309 Cell: 416-704-9250 www.insurancesystems.ca <>
Re: [BUGS] BUG #1250: compilation fails in src/backend/storage/lmgr/s_lock.c
On Fri, 10 Sep 2004, Tom Lane wrote: >"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: >> The code in s_lock.c uses a ".seg" directive where ".section" seems to be >> in vogue, judging from the output of "cc -S" for a simple "hello world" type >> program. > >Hmm. So how can we distinguish your version of Solaris from the ones >that want ".seg"? The SUNWspro man page for cc(1) contains the following (entries for -xarch=v9 i.e. 64bit sparc apply in my case) ... Predefinitions:unix sparc (SPARC) i386 (x86) sun The above are not predefined in -Xc mode. These predefinitions are valid in all modes: __sun __unix __SUNPRO_C=0x540 __`uname -s`_`uname -r` __sparc (SPARC) __sparcv9 (SPARC with -xarch=v9|v9a|v9b) __i386 (x86) __BUILTIN_VA_ARG_INCR __SVR4 The following is predefined in -Xa and -Xt modes only: __RESTRICT The compiler also predefines the object-like macro __PRAGMA_REDEFINE_EXTNAME, to indicate the pragma will be recognized. ... Guess the ___SUNPRO_C macro is a start. 'fraid the only other compiler I can test against is gcc-3.4.1. Any suggestions, I'll give 'em a try. Regards, -a. -- Aidan Thomas Dixon - [EMAIL PROTECTED] "Whether you believe you can or you can't, you're probably right!" ---(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
Re: [BUGS] BUG #1246: not exist pltcl.so in postgresql rpm package
Hi Tom, The problem is into postgresql-pl. I downloaded all rpm package for RedHat 9 and rhel3 from the postgresql.org site. For redhat 9: -rw-r--r--1 root root 787 Sep 7 11:19 MD5SUM -rw-r--r--1 root root 2037638 Sep 7 11:20 postgresql-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 439688 Sep 7 11:20 postgresql-contrib-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 17284615 Sep 7 11:22 postgresql-debuginfo-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 1763204 Sep 7 11:22 postgresql-devel-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 1239746 Sep 7 11:22 postgresql-docs-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 707019 Sep 7 11:22 postgresql-jdbc-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 142488 Sep 7 11:22 postgresql-libs-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 362000 Sep 7 11:22 postgresql-pl-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root38839 Sep 7 11:22 postgresql-python-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 3162539 Sep 7 11:23 postgresql-server-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 1054430 Sep 7 11:23 postgresql-test-7.4.5-1PGDG.i686.rpm For rhel3 -rw-r--r--1 root root 787 Sep 7 11:23 MD5SUM -rw-r--r--1 root root 2036384 Sep 7 11:23 postgresql-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 439392 Sep 7 11:23 postgresql-contrib-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 8086921 Sep 7 11:24 postgresql-debuginfo-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 917819 Sep 7 11:25 postgresql-devel-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 1193655 Sep 7 11:25 postgresql-docs-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 707040 Sep 7 11:25 postgresql-jdbc-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 142257 Sep 7 11:25 postgresql-libs-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 363493 Sep 7 11:25 postgresql-pl-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root38920 Sep 7 11:25 postgresql-python-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 3159511 Sep 7 11:26 postgresql-server-7.4.5-1PGDG.i686.rpm -rw-r--r--1 root root 1054172 Sep 7 11:26 postgresql-test-7.4.5-1PGDG.i686.rpm and when I execute "rpm -qpl postgresql-pl-7.4.5-1PGDG.i686.rpm" for both, my output command is: /usr/lib/pgsql/plperl.so /usr/lib/pgsql/plpython.so the plctl.so doesn't exist. Regards, Christian Gonzalez -Mensaje original- De: Tom Lane [mailto:[EMAIL PROTECTED] Enviado el: Miércoles, 08 de Septiembre de 2004 03:37 p.m. Para: Christian Gonzalez CC: [EMAIL PROTECTED] Asunto: Re: [BUGS] BUG #1246: not exist pltcl.so in postgresql rpm package "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > Where I can find the pltcl.so library?... Should be in the postgresql-pl RPM. regards, tom lane ---(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] PostgreSQL 8.0 - very good
Was the install very good, however am I needing to do something similar in the subject of the install to create users and services in Windows 2000/xp for an application, will it be that you could order me the script or project that you set up for this version 8.0 beta? Question: Does the version 8.0 already have programmed date to be thrown? Thank you
[BUGS] Pb with ecpg and include file on PG 8.0.0
Hi, I have a set of libraries and C/C++ programs with embedded access to a PG database. I'm using ecpg. I'm working on a Linux RedHat9 platform. Until now I was in PG 7.4.2 : [EMAIL PROTECTED] SrcLib]$ ecpg --version ecpg (PostgreSQL 7.4.2) 3.1.1 [EMAIL PROTECTED] SrcLib]$ g++ --version g++ (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) Copyright (C) 2002 Free Software Foundation, Inc. and without any problem. I installed PG 8.0.0beta2 : [EMAIL PROTECTED] SrcLib]$ ecpg --version ecpg (PostgreSQL 8.0.0beta2) 3.2.0 And if I try to recompile I find pre-compiled errors, variables which are defined in an include file are not "seen". Is there any known problem or bug about this ? Detail : === Precompiling DbTablesFk.pgc === ecpg DbTablesFk.pgc -I/VALE/users/clipg/Server/Include -o DbTablesFk.cc DbTablesFk.pgc:144: ERROR: trying to access an undeclared cursor MAX_FK DbTablesFk.pgc:144: ERROR: syntax error at or near "IN" and in the program : ... EXEC SQL INCLUDE DbTablesUtilPg.hh; ... EXEC SQL PREPARE S FROM :sqlstmt; EXEC SQL DECLARE C_FK_COL CURSOR FOR S; EXEC SQL OPEN C_FK_COL; EXEC SQL FETCH MAX_FK IN C_FK_COL INTO :fk_id_L , :valid_L, :target_t_L; with MAX_FK a variable defined in the file /VALE/users/clipg/Server/Include/DbTablesUtilPg.hh : exec sql define MAX_FK100; If I replace the MAX_FK variable by its value it's OK. If I define the MAX_FK variable directly in the program (and not in an include file) it's OK. Any idea ? Thanks for all, Valerie. -- *Les points de vue exprimes sont strictement personnels et * * n'engagent pas la responsabilite de METEO-FRANCE. * * Valerie SCHNEIDER Tel : +33 (0)5 61 07 81 91 * * METEO-FRANCE / DSI/DEVFax : +33 (0)5 61 07 81 09 * * 42, avenue G. CoriolisEmail : [EMAIL PROTECTED] * * 31057 TOULOUSE Cedex - FRANCE http://www.meteo.fr* ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] Installation failed on Win2k
Dear friends I'm not able to install postgresql on my Windows Machine: RDBMS Version: 8.0.0 beta2-2dev OS: Windows 2k - all patches installed (up to date) After klicking o.k. in the window that displays the Release Notes, installation abords with the following message: "Installation ended prematurely because of an error" Ok. That's it. :-) Please try too improve such errormessages, it would enormous help to find an error. Thanks for postgresql Oliver Leu *** ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] initdb errors, postgresql-8.0-beta
--- Tom Lane <[EMAIL PROTECTED]> wrote: > Did you invoke any of the build steps with a > relative path (eg, > "../configure")? Yep. > There are some known problems in > beta1 with > reducing relative paths to absolute. I think this > probably > explains your issue, though I did not see that > specific misbehavior > while investigating the bug. Should be fixed in > beta2. Thanks, and sorry for the belated response. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Permissions problem with sequences
What if they change the owner of the serial sequence independently anyway? I suppose a complete solution would involve forbidding that. We don't allow you to alter the owner of an index independently of its parent table ... Problem is existing dump files. Oh, hang on - this is new for 8.0. Hmmm...so what do we do then? I have been seriously pressed for time the last few weeks, so I don't have time to make alter table alter all the serial seqeunces on a table as well :( I've got a mostly working fix for the bug that involves alter owner on the sequence, but let me know if you want me to finish it. Chris ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Permissions problem with sequences
Hmm ... I hadn't thought of that approach, but it seems pretty reasonable offhand ... comments? What if they change the owner of the serial sequence independently anyway? Then dumps will be restored incorrectlynot that it matters perhaps... Chris ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] Can't run 8.0 ....
I just installed Postgres 8.0.0 in my PC environment. I created the necessary users and rebooted the system. Saw that the post_svc.exe and the postmaster.exe are running. However, the minute I try to connect to ‘template’ I get “too many clients already. Check your license” What’s this all about? Jon Wheatland Enterprise Information Solutions, Inc. 4910 Main St., Downers Grove, IL 60515 Office: 630.512.0570 - Fax: 630.512.0568 - Mobile: 630.330.3839
[BUGS] bug
Title: bug Hi could you help me resolve the following when trying to start the DB. $ ./postmaster -D /data1/pgdata IpcMemoryCreate: shmget(key=5432001, size=1417216, 03600) failed: Invalid argume nt This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 1417216 bytes), reduce PostgreSQL's shared_buffers parameter (currently 64) and/or its max_connections parameter (currently 32). If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. The PostgreSQL Administrator's Guide contains more information about shared memory configuration. $
[BUGS] affected rows from INSERT INTO view with rules and conditions
POSTGRESQL BUG REPORT TEMPLATE
Your name : Stephan Sachse
Your email address : sachse (at) nugmbh (dot) de
System Configuration
-
Architecture (example: Intel Pentium) : AMD Athlon(tm) Processor
Operating System (example: Linux 2.4.18) : Linux 2.4.25
PostgreSQL version (example: PostgreSQL-7.4.2): PostgreSQL-7.3.4
Compiler used (example: gcc 2.95.2) : gcc 3.2
Please enter a FULL description of your problem:
I have 3 rules an a View to INSERT into the VIEW. 1 rule without condition and
2 other rule with a condition. All INSERT querys works fine. My only problem
ist the number of affected rows for querys. some on it is always zero some it
is 1.
i try this also with v7.4.2 with absolutly the same result
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
--
-- START
-- first way is for affected rows is only 1 with pid = 2
CREATE TABLE rule_test
(
id integer NOT NULL DEFAULT nextval('rule_test_id'::text),
pid integer,
f_1 varchar,
f_2 varchar
) WITH OIDS;
CREATE SEQUENCE rule_test_id;
CREATE VIEW v_rule_test AS
SELECT id AS myid, pid AS mypid, f_1 AS myf_1, f_2 AS myf_2
FROM rule_test;
CREATE RULE v_rule_test_ins AS ON INSERT TO v_rule_test
DO INSTEAD
NOTHING;
CREATE RULE v_rule_test_ins_p1 AS ON INSERT TO v_rule_test WHERE new.mypid=1
DO INSTEAD
INSERT INTO rule_test (pid, f_1, f_2) VALUES (1, NEW.myf_1, NEW.myf_2);
CREATE RULE v_rule_test_ins_p2 AS ON INSERT TO v_rule_test WHERE new.mypid=2
DO INSTEAD
INSERT INTO rule_test (pid, f_1, f_2) VALUES (1, NEW.myf_2, NEW.myf_1);
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (1, 'field 1', 'field 2');
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (2, 'field 1', 'field 2');
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (11, 'field 1', 'field 2');
-- output truncate
-- INSERT 0 0
-- INSERT 34588 1
-- INSERT 0 0
-- ENDE
-- START
-- second way is for affected rows always zero
-- all same as above except the Rules are not INSTEAD
CREATE TABLE rule_test
(
id integer NOT NULL DEFAULT nextval('rule_test_id'::text),
pid integer,
f_1 varchar,
f_2 varchar
) WITH OIDS;
CREATE SEQUENCE rule_test_id;
CREATE VIEW v_rule_test AS
SELECT id AS myid, pid AS mypid, f_1 AS myf_1, f_2 AS myf_2
FROM rule_test;
CREATE RULE v_rule_test_ins AS ON INSERT TO v_rule_test
DO INSTEAD
NOTHING;
CREATE RULE v_rule_test_ins_p1 AS ON INSERT TO v_rule_test WHERE new.mypid=1
DO
INSERT INTO rule_test (pid, f_1, f_2) VALUES (1, NEW.myf_1, NEW.myf_2);
CREATE RULE v_rule_test_ins_p2 AS ON INSERT TO v_rule_test WHERE new.mypid=2
DO
INSERT INTO rule_test (pid, f_1, f_2) VALUES (1, NEW.myf_2, NEW.myf_1);
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (1, 'field 1', 'field 2');
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (2, 'field 1', 'field 2');
INSERT INTO v_rule_test (mypid, myf_1, myf_2) VALUES (11, 'field 1', 'field 2');
-- output truncate
-- INSERT 0 0
-- INSERT 0 0
-- INSERT 0 0
-- ENDE
If you know how this problem might be fixed, list the solution below:
-
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
