Re: [HACKERS] 7.3 schedule
> We'll need a good beta period this time, because of: I know it's a sore subject, but how about "ALTER TABLE DROP COLUMN" this time around? I've been hearing about it for years now. :) - brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] -snapshot?
Are snapshots still being generated on ftp.postgresql.org (and rsync)? I've just noticed that the date for the last /dev/*-snapshot* is May 8th. What's the deal? - Brandon c: 917-697-8665h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [mail] Re: [HACKERS] Native Win32 sources
> > D'Arcy, > > > > In production the database servers are seperate multi-processor machines > > with mirrored disks linked via Gigabit ethernet to the app server. > > > > In development I have people extremely familiar with MS, but not very hot > > with Unix in any flavour, who are developing Java and PHP code which is then > > passed into the QA phase where it's run on a replica of the production > > environment. > > > > My goal is to allow my developers to work on the platform they know (MS), > > using as many of the aspects of the production environment as possible (JVM > > version, PHP version, and hopefully database version), without needing to > > buy each new developer two machines, and incur the overhead of them > > familiarising themselves with a flavour of Unix. (from experience in a large .com web site) Can you have a central DB server? Do all the dev DB servers need to be independent? You could even have a machine w/ ip*(# developers) and bind a postgresql to each ip for each developer (assuming you had enough memory, etc). We used oracle once upon a time at my .com and used seperate schemas for the seperate developers. This may be tricky for your environment because the developers would need to know what schema they would connect to if all schemas were under the same pgsql instance. - Brandon c: 917-697-8665h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 7.4 Wishlist
> * Compliant ADD COLUMN I've missed the thread (if there was one), how is it non-compliant? Thanks, - Brandon c: 917-697-8665h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(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: [HACKERS] Wishlist for 7.4: Plan stability
Is someone keeping a "hopeful" todo list? - Brandon c: 917-697-8665h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] broken web server?
I know this isn't really hackers traffic, but... one of the servers in www.postgresql.org is http://postgresql.bbksys.com/ which is giving me 404 errors.. I've mailed webmaster@, but thought this should be mailed on anyway.. - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] v7.1.1 branched and released on Tuesday ...
> > Does anyone have any outstanding fixes for v7.1.x that they want to see in > *before* we do this release? Any points unresolved that anyone knows > about that we need to look at? Is there a list of what IS getting changed? Can this be posted somewhere or is the changelist enough? - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Replication Docs..
I'm starting to throw together a web site relating to postgresql replication, trying to bring together the ideas we have thrown around so far. If anyone has any good docs (on replication not relating to postgresq too), please send me the links. Thanks. - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] Re: New Linux xfs/reiser file systems
> > This behavior raises the question about file system usage in Postgres. Many > > databases, such as Oracle, create table space files and operate directly on the > > raw blocks, bypassing the file system altogether. > > OK, we have considered this, but frankly, the new, modern file systems > like FFS/softupdates have i/o rates near raw speed, with all the > advantages a file system gives us. I believe most commercial dbs are > moving away from raw devices and toward file systems. In the old days > the SysV file system was pretty bad at i/o & fragmentation, so they used > raw devices. I'm starting to like the idea of raw FS for a few reasons: 1) Considering that postgresql now does WAL, the need for a logging FS for the database doesn't seem as needed (is it needed at all?). 2) Given the fact that postgresql is trying to support many OSs, depending on, for example, XFS on a linux system will cause many problems. What about solaris? How about BSD? Etc.. Using raw db MAY be easier than dealing with the problems that will arise from supporting multiple filesystems. That said, the ability to use the system's FS does have it's advantages (backup, moving files, etc). Just some thoughts.. - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Regression tests for OBSD scrammed..
My nightly regression tests for OBSD failed for i386 and sparc. Attached is the regression.diff, I don't know what to make of it.. Looks like problems w/ foreign keys. ... parallel group (5 tests): portals_p2 rules select_views alter_table foreign_key select_views ... ok alter_table ... FAILED portals_p2 ... ok rules... ok foreign_key ... FAILED parallel group (3 tests): limit temp plpgsql ... b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 *** ./expected/alter_table.out Thu May 10 05:02:48 2001 --- ./results/alter_table.out Thu May 10 05:09:16 2001 *** *** 347,372 CREATE TABLE FKTABLE (ftest1 cidr, ftest2 datetime); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable; NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: Unable to identify an operator '=' for types 'cidr' and 'int4' ! You will have to retype this query using an explicit cast -- Again, so should this... DROP TABLE FKTABLE; CREATE TABLE FKTABLE (ftest1 cidr, ftest2 datetime); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest1, ptest2); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: Unable to identify an operator '=' for types 'cidr' and 'int4' ! You will have to retype this query using an explicit cast -- This fails because we mixed up the column ordering DROP TABLE FKTABLE; CREATE TABLE FKTABLE (ftest1 int, ftest2 text); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest2, ptest1); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: Unable to identify an operator '=' for types 'int4' and 'text' ! You will have to retype this query using an explicit cast -- As does this... ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1) references pktable(ptest1, ptest2); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: Unable to identify an operator '=' for types 'text' and 'int4' ! You will have to retype this query using an explicit cast DROP TABLE FKTABLE; DROP TABLE PKTABLE; --- 347,369 CREATE TABLE FKTABLE (ftest1 cidr, ftest2 datetime); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable; NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: RelationClearRelation: relation 144096 deleted while still in use -- Again, so should this... DROP TABLE FKTABLE; CREATE TABLE FKTABLE (ftest1 cidr, ftest2 datetime); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest1, ptest2); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: Relation 'pktable' does not exist -- This fails because we mixed up the column ordering DROP TABLE FKTABLE; CREATE TABLE FKTABLE (ftest1 int, ftest2 text); ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest2, ptest1); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: UNIQUE constraint matching given keys for referenced table "pktable" not found -- As does this... ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1) references pktable(ptest1, ptest2); NOTICE: ALTER TABLE ... ADD CONSTRAINT will create implicit trigger(s) for FOREIGN KEY check(s) ! ERROR: RelationClearRelation: relation 144277 deleted while still in use DROP TABLE FKTABLE; + ERROR: table "fktable" does not exist DROP TABLE PKTABLE; == *** ./expected/foreign_key.out Thu May 10 05:02:48 2001 --- ./results/foreign_key.out Thu May 10 05:09:18 2001 *** *** 574,697 -- set default update / set null delete CREATE TABLE PKTABLE ( ptest1 int, ptest2 int, ptest3 int, ptest4 text, PRIMARY KEY(ptest1, ptest2, ptest3) ); NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable' CREATE TABLE FKTABLE ( ftest1 int DEFAULT 0, ftest2 int DEFAULT -1, ftest3 int, ftest4 int, CONSTRAINT constrname3 FOREIGN KEY(ftest1, ftest2, ftest3) REFERENCES PKTABLE ON DELETE SET NULL ON UPDATE SET DEFAULT); NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s) -- Insert Primary Key values INSERT INTO PKTABLE VALUES (1, 2, 3, 'test1'); INSERT INTO PKTABLE VALUES (1, 3, 3, 'test2'); INSERT INTO PKTABLE VALUES (2, 3, 4, 'test3'); INSERT INTO PKTABLE VALUES (2, 4, 5, 'test4'); INSERT INTO PKTABLE VALUES (2, -1, 5, 'test5'); -- Insert Foreign Key
Re: [HACKERS] developer's website
> The developer's corner will soon be going away. I'm in the process of > putting together a developer's site. Different URL, different look, > beta announcements will be there, regression database will be there, > developement docs, etc. If you want a sneak preview: > > http://developer.postgresql.org/ Right now, a good part of what I mirror (and my traffic) for the web site are of the devel site. Will a third set of mirrors (www / ftp / devel) need to be setup, or will the main site handle all the load? - Brandon b. palmer, [EMAIL PROTECTED]pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] backend hba.c prob
On Fri, 7 Sep 2001, Bruce Momjian wrote: > > gcc -O2 -pipe -g -Wall -Wmissing-prototypes -Wmissing-declarations >-I../../../src/include -c -o hba.o hba.c > > hba.c: In function `ident_unix': > > hba.c:923: sizeof applied to an incomplete type > > hba.c:960: dereferencing pointer to incomplete type > > hba.c:965: dereferencing pointer to incomplete type > > gmake: *** [hba.o] Error 1 > The code currently runs on FreeBSD and BSD/OS. Right now, it tests for > BSD/OS and if it fails, assume it is FreeBSD. That is what the #ifndef > fc_uid is for. Now, I assume you are on a *BSD which is not one of > those. Do you have a struct fcred? I will browse your OS headers as > soon as I know your OS. Yeah, i'm seeing the same problem on OpenBSD-current (and 2.9). No Cred anywhere! This: root@mizer:/usr/src$ egrep -r "fcred" * turned up nothing interesting either. Thoughts? - Brandon b. palmer, [EMAIL PROTECTED]pgp:crimelabs.net/bpalmer.pgp5 ---(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: [HACKERS] autoconf taking forever?
> > I'm working on making some changes to the top level configure.in and m4 > > has now been running for 17 minutes on a 1.4G tbird. Am I missing > > something or is this know to take forever? > > For me, the autoconf run is "instantaneous". Make sure you're using > Autoconf 2.13, and you don't have actual infinite loops in your code. Or > perhaps the problem is in OpenBSD's m4 (which I suspect you are using)? I am running 2.13 (even on a clean checkout of 7.1.3) and the autoconf takes forever. However, m4 is the process that's running forever, so I have no doubs that the problem is there. What version do you use that works? I'll try getting a new version... Any ideas where to look for a solution though? - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.2b1 ...
Is there some formal place to make comments on how 7.2b1 works? I'm about to run it through it's paces on OBSD. Or is this just a 'it's broked' testing time? - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] CVS changes
> Since there have been drastic CVS changes, the web page doc should REALLY > be updated... Withdrawn, I notive Bruce made the changes, but I guess they havn't hit yet. My bad. - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(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
[HACKERS] LOCAL_CREDS -> SCM_CREDS in src/backend/libpq/auth.c:535
For OpenBSD to work, we need a change from LOCAL_CREDS to SCM_CREDS. Bruce, I think you are familure with this one. Care to make the change? (I have no idea where to make it!). Thanks all, - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] CVS changes
Since there have been drastic CVS changes, the web page doc should REALLY be updated... http://www.ca.postgresql.org/devel-corner/docs/postgres/cvs.html - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] autoconf taking forever?
I'm working on making some changes to the top level configure.in and m4 has now been running for 17 minutes on a 1.4G tbird. Am I missing something or is this know to take forever? Thanks guys, - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] Why are ftp mirrors out of sync?
> You can find a snapshot that should be pretty durn close to 7.2beta1 > at ftp://ftp2.us.postgresql.org/pub/dev/postgresql-snapshot.tar.gz > (note that at last word, other mirrors were not up to date --- if > the doc/TODO file doesn't contain a date in October, it's stale). > I think the only thing we're still waiting on is some datetime fixes > from Tom Lockhart... I'm a bit confused. Are you implying that the rest of the mirrors are broken or that ftp2 just has info that hasn't been put out for the rest of the mirrors yet.. I mirror every 4 hours and get: # ./rsync-postgres-ftp receiving file list ... done wrote 110 bytes read 19042 bytes 7660.80 bytes/sec total size is 432138525 speedup is 22563.62 when connecting to hub.org and: @ERROR: Unknown module 'postgresql-ftp' when connecting to rsync.postgresql.org. Did I miss something here? - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Replication
> I've been looking for documents and other info on replication efforts in > PostgreSQL. If anyone here can point me to places where I can find > these, it would be really appreciated. It really depends on your replication needs. I would suggest taking a look at gborg.postgresql.org for any of the replication projects there. There are some that work, some that don't and some that are still in the works. > Also, if any of you have any comments and warnings about current > implementations (if there are any) I'd like to hear those too. Also in the works is adding the ability to postgresql native to do replication. That is, however, at least as far away as the next version (7.3, ~6-8 months). - Brandon c: 646-456-5455h: 201-798-4983 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] beta testing version
Can we PLEASE kill this thread? There are only a handful of people who are making contributions here and nothing really new is being said. I agree that the issue should be discussed, but this does not seem like the right forum. Thanks. - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
[HACKERS] Why vacuum?
I noticed the other day that one of my pg databases was slow, so I ran vacuum on it, which brought a question to mind: why the need? I looked at my oracle server and we aren't doing anything of the sort (that I can find), so why does pg need it? Any info? Thanks, - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] Why vacuum?
> Yes, postgresql requires vacuum quite often otherwise queries and > updates start taking ungodly amounts of time to complete. If you're > having problems because vacuum locks up your tables for too long > you might want to check out: But why? I don't know of other databases that need to be 'vacuum'ed. Do all others just do it internaly on a regular basis? What am I missing here? b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
[HACKERS] 7.1 snapshot on i386 BSD MAJOR failure
Is this bad, or are there expected to be known problems like this for OBSD? 7.1beta1 had roughly the same errors.. - BEGIN --- bpalmer@mizer:~/PG7.1/postgresql-snapshot>uname -a OpenBSD mizer 2.8 GENERIC#399 i386 bpalmer@mizer:~/PG7.1/postgresql-snapshot>gmake check gmake -C doc all gmake[1]: Entering directory `/home/bpalmer/PG7.1/postgresql-snapshot/doc' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/bpalmer/PG7.1/postgresql-snapshot/doc' ... ... (no errors) ... gmake[2]: Entering directory `/home/bpalmer/PG7.1/postgresql-snapshot/src/test/regress' gmake -C ../../../contrib/spi REFINT_VERBOSE=1 refint.so autoinc.so gmake[3]: Entering directory `/home/bpalmer/PG7.1/postgresql-snapshot/contrib/spi' gmake[3]: `refint.so' is up to date. gmake[3]: `autoinc.so' is up to date. gmake[3]: Leaving directory `/home/bpalmer/PG7.1/postgresql-snapshot/contrib/spi' /bin/sh ./pg_regress --temp-install --top-builddir=../../.. --schedule=./parallel_schedule --multibyte= == removing existing temp installation== == creating temporary installation== == initializing database system == == starting postmaster== running on port 65432 with pid 29043 == creating database "regression" == CREATE DATABASE == installing PL/pgSQL== == running regression test queries== parallel group (13 tests): boolean varchar int8 numeric text int4 char oid int2 float4 name float8 bit boolean ... FAILED char ... ok name ... ok varchar ... FAILED text ... ok int2 ... FAILED int4 ... FAILED int8 ... FAILED oid ... ok float4 ... ok float8 ... FAILED bit ... ok numeric ... FAILED test strings ... FAILED test numerology ... ok parallel group (18 tests): box type_sanity point abstime tinterval interval reltime inet oidjoins path comments timestamp date circle time lseg polygon opr_sanity point... ok lseg ... ok box ... FAILED path ... FAILED polygon ... ok circle ... FAILED date ... FAILED time ... FAILED timestamp... FAILED interval ... FAILED abstime ... FAILED reltime ... ok tinterval... FAILED inet ... ok comments ... FAILED oidjoins ... FAILED type_sanity ... FAILED opr_sanity ... ok test geometry ... FAILED test horology ... FAILED test create_function_1... ok test create_type ... ok test create_table ... ok test create_function_2... ok test copy ... ok parallel group (7 tests): inherit create_aggregate create_operator triggers create_misc constraints create_index constraints ... ok triggers ... ok create_misc ... ok create_aggregate ... ok create_operator ... ok create_index ... ok inherit ... FAILED test create_view ... ok test sanity_check ... FAILED test errors ... ok test select ... ok parallel group (16 tests): random union select_distinct select_into arrays portals transactions select_distinct_on select_having subselect select_implicit aggregates case join btree_index hash_index select_into ... ok select_distinct ... FAILED select_distinct_on ... ok select_implicit ... ok select_having... ok subselect... FAILED union... FAILED case ... ok join ... ok aggregates ... ok transactions ... FAILED random ... failed (ignored) portals ... FAILED arrays ... FAILED btree_index ... ok hash_index ... ok test misc ... FAILED parallel group (5 tests): portals_p2 select_views alter_table foreign_key rules select_views ... ok alter_table ... ok portals_p2 ... ok rules... ok foreign_key ... ok parallel group (3 tests): temp limit plpgsql limit... ok plpgsql ... ok temp
[HACKERS] CVS regression test failure on OBSD
When I run 'make check' on the CVS version (today and for the last serveral days), I have been getting interesting failures. Some of the tests fail, but the interesting part is that not the same tests always fail. Example: bpalmer@mizer:~/APPS/pgsql>diff 1 2 1c1 < boolean ... FAILED --- > boolean ... ok 3c3 < name ... ok --- > name ... FAILED 5c5 < text ... FAILED --- > text ... ok 9,10c9,10 < oid ... FAILED < float4 ... ok --- > oid ... ok > float4 ... FAILED In the regression.diff file, I keep seeing this: *** ./expected/name.out Tue Jan 4 11:19:34 2000 --- ./results/name.out Sat Jan 6 16:36:34 2001 *** *** 1,124 ! -- ! -- NAME ! -- all inputs are silently truncated at NAMEDATALEN (32) characters ! -- ! -- fixed-length by reference ! SELECT name 'name string' = name 'name string' AS "True"; ! True ! -- ... ... ... ! (2 rows) ! ! DROP TABLE NAME_TBL; --- 1 ! psql: Backend startup failed == Any ideas where to look for this one? When I run the regression test WITH ANOTHER INSTANCE OF PGSQL running, I got an error telling me that I needed more SEMMNI or SEMMNS. I recompiled my kernel with the values of 1024 and 2048 respectivly, and that seems to have solved the problem, but they may still be related. Any ideas? - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] CVS regression test failure on OBSD
> In the postmaster: the fork() to launch a backend is failing. There
> should be a more detailed message in the postmaster's stderr log,
> but almost certainly it's a resource-exhaustion issue. Does your
> kernel enforce a per-userid limit on the number of processes, for
> example?
Looks like that was part of the problem. Process ulimit and openfile
limit were both problems. I have rolled up the process ulimit (soft /
hard) to 256 and the Open Files to 256.
There are still, however, 4 tests that fail.
Attached.
- Brandon
uname -a
OpenBSD mizer 2.8 a#0 i386 (2.8 snapshot NOV 6 install)
b. palmer, [EMAIL PROTECTED]
pgp: www.crimelabs.net/bpalmer.pgp5
*** ./expected/int2.out Tue Jan 4 11:19:34 2000
--- ./results/int2.out Sat Jan 6 17:56:29 2001
***
*** 14,20
INSERT INTO INT2_TBL(f1) VALUES ('-32767');
-- bad input values -- should give warnings
INSERT INTO INT2_TBL(f1) VALUES ('10');
! ERROR: pg_atoi: error reading "10": Numerical result out of range
INSERT INTO INT2_TBL(f1) VALUES ('asdf');
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
SELECT '' AS five, INT2_TBL.*;
--- 14,20
INSERT INTO INT2_TBL(f1) VALUES ('-32767');
-- bad input values -- should give warnings
INSERT INTO INT2_TBL(f1) VALUES ('10');
! ERROR: pg_atoi: error reading "10": Result too large
INSERT INTO INT2_TBL(f1) VALUES ('asdf');
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
SELECT '' AS five, INT2_TBL.*;
==
*** ./expected/int4.out Tue Mar 14 18:06:56 2000
--- ./results/int4.out Sat Jan 6 17:56:30 2001
***
*** 14,20
INSERT INTO INT4_TBL(f1) VALUES ('-2147483647');
-- bad input values -- should give warnings
INSERT INTO INT4_TBL(f1) VALUES ('1');
! ERROR: pg_atoi: error reading "1": Numerical result out of range
INSERT INTO INT4_TBL(f1) VALUES ('asdf');
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
SELECT '' AS five, INT4_TBL.*;
--- 14,20
INSERT INTO INT4_TBL(f1) VALUES ('-2147483647');
-- bad input values -- should give warnings
INSERT INTO INT4_TBL(f1) VALUES ('1');
! ERROR: pg_atoi: error reading "1": Result too large
INSERT INTO INT4_TBL(f1) VALUES ('asdf');
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
SELECT '' AS five, INT4_TBL.*;
==
*** ./expected/float8.out Mon Mar 20 00:19:10 2000
--- ./results/float8.outSat Jan 6 17:56:30 2001
***
*** 241,249
INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400');
ERROR: Input '-10e400' is out of range for float8
INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400');
- ERROR: Input '10e-400' is out of range for float8
INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400');
- ERROR: Input '-10e-400' is out of range for float8
-- maintain external table consistency across platforms
-- delete all values and reinsert well-behaved ones
DELETE FROM FLOAT8_TBL;
--- 241,247
==
*** ./expected/geometry.out Tue Sep 12 17:07:16 2000
--- ./results/geometry.out Sat Jan 6 17:56:52 2001
***
*** 114,120
| (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)
--- 114,120
| (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)
***
*** 150,160
six |box
-+
| (2.12132034355964,2.12132034355964),(-2.12132034355964,-2.12132034355964)
! | (71.7106781186548,72.7106781186548),(-69.7106781186548,-68.7106781186548)
! | (4.53553390593274,6.53553390593274),(-2.53553390593274,-0.535533905932738)
! | (3.12132034355964,4.12132034355964),(-1.12132034355964,-0.121320343559643)
| (107.071067811865,207.071067811865),(92.9289321881345,192.928932188135)
! | (170.710678118655,70.7106781186548),(29.28932188
Re: [HACKERS] CVS regression test failure on OBSD
> Those all look like trivial platform dependencies. Please read > http://www.postgresql.org/devel-corner/docs/postgres/regress.htm > http://www.postgresql.org/devel-corner/docs/postgres/regress-platform.htm > and submit resultmap patches as required for your platform. Sweet. Thanks, looks like the problem is solved. Should me make note of the changes what were needed for OBSD somewhere? b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 bpalmer@mizer:~/APPS/pgsql/src/test/regress>diff -c resultmap resultmap.orig *** resultmap Sat Jan 6 19:35:02 2001 --- resultmap.orig Sat Jan 6 19:12:57 2001 *** *** 7,13 float4/.*-qnx=float4-exp-three-digits float8/.*-bsdi=float8-small-is-zero float8/.*-freebsd=float8-small-is-zero - float8/.*-openbsd=float8-small-is-zero float8/i.86-.*-netbsd=float8-small-is-zero float8/.*-qnx=float8-exp-three-digits float8/alpha.*-dec-osf.*:cc=float8-fp-exception --- 7,12 *** *** 16,22 geometry/.*-darwin=geometry-powerpc-darwin geometry/.*-freebsd=geometry-positive-zeros geometry/.*-freebsd4=geometry-positive-zeros-bsd - geometry/.*-openbsd=geometry-positive-zeros-bsd geometry/.*-irix6=geometry-irix geometry/.*-netbsd=geometry-positive-zeros geometry/.*-sysv5uw7.*:cc=geometry-uw7-cc --- 15,20 *** *** 45,51 int2/.*-irix6=int2-too-large int2/.*-netbsd=int2-too-large int2/.*-qnx=int2-too-large - int2/.*-openbsd=int2-too-large int2/alpha.*-dec-osf=int2-too-large int2/hppa=int2-too-large int2/i.86-pc-cygwin=int2-math-result-out-of-range --- 43,48 *** *** 62,68 int4/.*-irix6=int4-too-large int4/.*-netbsd=int4-too-large int4/.*-qnx=int4-too-large - int4/.*-openbsd=int4-too-large int4/alpha.*-dec-osf=int4-too-large int4/hppa=int4-too-large int4/i.86-pc-cygwin=int4-math-result-out-of-range --- 59,64
Re: [HACKERS] CVS regression test failure on OBSD
A few problems came up with 7.1CVS for i86 OpenBSD. Here is a writeup on what I learned and how I solved the problems. - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 Added gmake and gettext. (if you don't have it) Added bison and replaced /usr/bin/yacc with /usr/local/bin/bison get source (make sure you don't ./configure before you update yacc) (these above points should ONLY effect the CVS version, not a snapshot) ./configure gmake gmake check - fast make check failed when I had too much else going on. (too many other postgres owned apps). On a fast machine, this will really break fast since some of the postgres instances don't return before others start up and we hit max process (64). edited: /etc/login.conf Changed: default:\ :maxproc-max=128:\ :maxproc-cur=64:\ :openfiles-cur=64:\ to default:\ :maxproc-max=256:\ :maxproc-cur=256:\ :openfiles-cur=256:\ Be warned, however, this this could cause other problems on the machine. Now other processes will get locked out and will no be able to run. This is a safe high number for a box that is ONLY RUNNING POSTGRESQL. Tweak as necessary. - make check with postmaster running (on a non 5432 port) This bombs with: pgql: connectDBStart() -- connect() failed: No such file or directory Is the postmaster running locally and accepting connections on Unix socket '/tmp/.s.PGSQL.65432'? createdb: database creation failed pg_regress: createdb failed When I am running the regression test and I try to start up postmaster, I get: $ bin/postmaster -p -i -D data IpcSemaphoreCreate: semget(key=002, num=17, 03600) failed: No space left on device This error does *not* mean that you have run out of disk space. It occurs either because system limit for the maximum number of semaphore sets (SEMMNI), or the system wide maximum number of semaphores (SEMMNS), would be exceeded. You need to raise the respective kernel parameter. Look into the PostgreSQL documentation for details. Time to change this in the kernel. I added the following 2 lines to a 'GEN.postgres' config (just copied GENERAL to the new name): option SEMMNI=256 option SEMMNS=2048 and recompiled the kernel. Using these settings I am able to run 6 instances of postmaster on a celeron 300 w/ 96M ram before seeing that problem arise again. ** Note that once those 6 are running, make check will again break since it will not be able to have enough SEMMNI/SEMMNS. Also, please note that though 6 are running, we have no idea how many files are open and how this will effect the function of client connections, etc. (5 postmasters + make check DID with this setup on my machine) ** Please mail me any other information that any other people come up with regarding this problem (like what SEMMNI/SEMMNS and ulimits cap out at, etc). Brandon Palmer [EMAIL PROTECTED]
Re: [HACKERS] CVS regression test failure on OBSD
> Can you check > http://www.postgresql.org/devel-corner/docs/postgres/kernel-resources.htm#SYSVIPC > to see if the description for FreeBSD is also applicable (at least in > similar form) to OpenBSD? Close enough. > I'm currently writing up a section about the process and file limit issue, > which will end up nearby the section linked to above. I still don't know how to know what the max allowed (by the system) are. Anyone? - b b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] Re: Beta2 ... ?
Speaking of which.. > > rpm -ivh ftp://ftp.postgresql/pub/whatever/postgresql-\*.rpm > Is there a clearing house for packages? I have made some for OpenBSD (www.crimelabs.net/postgresql.shtml), but I wouldn't even know where to get the rpm or deb files. Should there be a folder on the ftp server for packages for the betas? - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
[HACKERS] $PGDATA/base/???
On older versions of PG, 7.0 included, in the $PDGATA/base folder you could see the names of the databases for that $PGDATA. Now all I see is: $ ls -l total 16 drwx-- 2 postgres wheel 1536 Jan 12 15:42 1 drwx-- 2 postgres wheel 1536 Jan 12 15:41 18719 drwx-- 2 postgres wheel 1536 Jan 12 15:42 18720 drwx-- 2 postgres wheel 1536 Jan 15 15:59 18721 Is there a way to relate this to the names of the databases? Why the change? Or am I missing something key here.. - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] $PGDATA/base/???
> I object. The code displays oids and tablenames or relnames. Oid is just > the initial, default filename for tables, and may change to something other > than the oid. Currently, the reindex code is the only place that could change > the relfilenode without changing the oid, but I think there may be more > in the future. Looks great, and I agree. Did not know that little piece of information. I have made the changed to my code, here's the new version. I have tested this one and updated the web page. - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 oid2name-0.1.1.tar.gz
Re: [HACKERS] $PGDATA/base/???
On Tue, 23 Jan 2001, Bruce Momjian wrote: > I have added this to /contrib for 7.1. > Not sure if you know this, but you checked in the code compiled and w/ the .o file... FYI. b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] beta3 Solaris 7 (SPARC) port report [ Was: Lookingfor . . . ]
Worked fine for me... % uname -a SunOS lancelot 5.7 Generic_106541-14 sun4m sparc SUNW,SPARCstation-4 % ls -l -rw-r--r-- 1 bpalmer staff32860160 Jan 23 16:45 postgresql-snapshot.tar ... ... ... transactions ... ok random ... failed (ignored) portals ... ok ... ... ... == 75 of 76 tests passed, 1 failed test(s) ignored. == On Thu, 25 Jan 2001, Peter Eisentraut wrote: > Frank Joerdens writes: > > [randomly varying set of regression tests fail] > > > Running the tests on my Linux box gives no failed tests. Must I assume > > that those failed tests indicate some issue that is is detrimental to > > the proper functioning of the server on this Solaris installation? Do > > you want the regression.diffs? > > Could you go into src/test/regress/pg_regress.sh and edit around line 162 > > #case $host_platform in > #*-*-qnx* | *beos*) > unix_sockets=no;; > #*) > #unix_sockets=yes;; > #esac > > (i.e., ensure that unix_sockets is set to 'no'), and rerun 'make check'. > > I have experienced before that Unix sockets will cause random connection > abortions on Solaris, which will cause the regression tests to fail > arbitrarily. > > > I also tried using the Sun compiler, which didn't work at all. > > details on "didn't work" requested... > > > now I get scary stuff like: > > > > --- begin scary stuff --- > > test int2 ... ERROR: pg_atoi: error in "34.5": can't > > parse ".5" > > ERROR: pg_atoi: error reading "10": Result too large > > ERROR: pg_atoi: error in "asdf": can't parse "asdf" > > This is normal. The regression tests sometimes involve intentional > invalid input. > > -- > Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/ > > > b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5
Re: [HACKERS] Re: Final Call: RC1 about to go out the door ...
$ uname -a OpenBSD mizer 2.8 a#0 i386 P3, default 2.8 install. Problems w/ TCL, but I think it's a local problem. System needs kernel changes as noted at www.crimelabs.net. (shared mem stuff). OBSD-sparc comming soon. - b b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: Call for platforms
On Thu, 22 Mar 2001, Thomas Lockhart wrote: > > > OpenBSD 2.8 x867.1 2001-03-22, B. Palmer (first name?) > > Though it does work, like FBSD, there are some changes that need to be > > made to the system. Need max proc / files changes and a kernel recompile > > with SEMMNI and SEMMNS changes. Anywhere special to note this? > > So more-or-less the *same* configuration as is required for FBSD? If so, > I could note that in the comments part of the platform support table. The kernel changes are the same, but OBSD needs the max proc, max open file settings changes (no reboot required). > > I'm not sure if either one (OBSD, FBSD) is actually explicitly > documented for PostgreSQL (I don't see a FAQ, and am not sure if there > is something in the sgml docs). Does anyone know if and where these > things are noted? http://www.postgresql.org/devel-corner/docs/postgres/kernel-resources.html This is the closest thing to docs. kernel-resources for specific OSs. - b b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Re: Call for platforms
On Thu, 22 Mar 2001, Thomas Lockhart wrote: > OpenBSD 2.8 x867.1 2001-03-22, B. Palmer (first name?) Though it does work, like FBSD, there are some changes that need to be made to the system. Need max proc / files changes and a kernel recompile with SEMMNI and SEMMNS changes. Anywhere special to note this? b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Re: Call for platforms
> OpenBSD 2.8 x867.1 2001-03-22, Brandon. Palmer OBSD checks out for sparc and i386. We did need to make a change to the resultmap file to make the regression tests clean for the sparc. I have attached the diff. Also, on the sparc that i'm using (sparc4/110), make check takes 1950 seconds. Most of the time is spent in this test: parallel group (13 tests): float4 int2 int4 text name varchar oid boolean char float8 int8 bit numeric There is a long pause between 'bit' and 'numeric'. Same with on i386. Is this a problem that is local to obsd? Is it an expected delay? It works, but seems like a real perf problem. Anyway: Sparc 4/110, 64M, SCSI disk, OBSD 2.8 virgin == All 76 tests passed. == 1941.34s real 130.23s user93.77s system $ uname -a OpenBSD azreal 2.8 GENERIC#0 sparc P2 300, 96M, IDE Disk, OBSD 2.8 virgin == All 76 tests passed. == 262.67s real21.84s user13.56s system $ uname -a OpenBSD orion 2.8 GENERIC#0 i386 I can't get tcl/tk working to same my life, but that's not too important for a release, just a config pain in the rear for obsd I guess. - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 *** resultmap.orig Fri Mar 23 12:34:56 2001 --- resultmap.new Fri Mar 23 12:19:47 2001 *** *** 5,11 float4/.*-qnx=float4-exp-three-digits float8/.*-bsdi=float8-small-is-zero float8/.*-freebsd=float8-small-is-zero ! float8/.*-openbsd=float8-small-is-zero float8/i.86-.*-netbsd=float8-small-is-zero float8/.*-qnx=float8-exp-three-digits float8/alpha.*-dec-osf.*:cc=float8-fp-exception --- 5,11 float4/.*-qnx=float4-exp-three-digits float8/.*-bsdi=float8-small-is-zero float8/.*-freebsd=float8-small-is-zero ! float8/i.86-.*-openbsd=float8-small-is-zero float8/i.86-.*-netbsd=float8-small-is-zero float8/.*-qnx=float8-exp-three-digits float8/alpha.*-dec-osf.*:cc=float8-fp-exception *** *** 14,20 geometry/.*-darwin=geometry-powerpc-darwin geometry/.*-freebsd=geometry-positive-zeros geometry/.*-freebsd4=geometry-positive-zeros-bsd ! geometry/.*-openbsd=geometry-positive-zeros-bsd geometry/.*-irix6=geometry-irix geometry/.*-netbsd=geometry-positive-zeros geometry/.*-sysv5uw7.*:cc=geometry-uw7-cc --- 14,21 geometry/.*-darwin=geometry-powerpc-darwin geometry/.*-freebsd=geometry-positive-zeros geometry/.*-freebsd4=geometry-positive-zeros-bsd ! geometry/i386-.*-openbsd=geometry-positive-zeros-bsd ! geometry/sparc-.*-openbsd=geometry-positive-zeros geometry/.*-irix6=geometry-irix geometry/.*-netbsd=geometry-positive-zeros geometry/.*-sysv5uw7.*:cc=geometry-uw7-cc ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
[HACKERS] OBSD resultmap changes needed.
I posted this to the list a few days ago, but it was not addressed. Can someone please make the changes to the src/test/regress/resultmap? Thanks. - brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 *** resultmap.orig Fri Mar 23 12:34:56 2001 --- resultmap.new Fri Mar 23 12:19:47 2001 *** *** 5,11 float4/.*-qnx=float4-exp-three-digits float8/.*-bsdi=float8-small-is-zero float8/.*-freebsd=float8-small-is-zero ! float8/.*-openbsd=float8-small-is-zero float8/i.86-.*-netbsd=float8-small-is-zero float8/.*-qnx=float8-exp-three-digits float8/alpha.*-dec-osf.*:cc=float8-fp-exception --- 5,11 float4/.*-qnx=float4-exp-three-digits float8/.*-bsdi=float8-small-is-zero float8/.*-freebsd=float8-small-is-zero ! float8/i.86-.*-openbsd=float8-small-is-zero float8/i.86-.*-netbsd=float8-small-is-zero float8/.*-qnx=float8-exp-three-digits float8/alpha.*-dec-osf.*:cc=float8-fp-exception *** *** 14,20 geometry/.*-darwin=geometry-powerpc-darwin geometry/.*-freebsd=geometry-positive-zeros geometry/.*-freebsd4=geometry-positive-zeros-bsd ! geometry/.*-openbsd=geometry-positive-zeros-bsd geometry/.*-irix6=geometry-irix geometry/.*-netbsd=geometry-positive-zeros geometry/.*-sysv5uw7.*:cc=geometry-uw7-cc --- 14,21 geometry/.*-darwin=geometry-powerpc-darwin geometry/.*-freebsd=geometry-positive-zeros geometry/.*-freebsd4=geometry-positive-zeros-bsd ! geometry/i386-.*-openbsd=geometry-positive-zeros-bsd ! geometry/sparc-.*-openbsd=geometry-positive-zeros geometry/.*-irix6=geometry-irix geometry/.*-netbsd=geometry-positive-zeros geometry/.*-sysv5uw7.*:cc=geometry-uw7-cc ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Final call for platform testing
> > I just ran the "make check" (paralell regression tests) - instead of the > "make installcheck" that I'd run previously... > > [nobody@web-cache regress]$ grep 'FAILED' regression.out > test geometry ... FAILED > test horology ... FAILED > > The relevant diff for horology seem to be: I can't speak to the geo test failures, but the horology failures have to do with the change from daylight saving change. Since we lost an hour they will be off. Is this something to be looked at? The failure of the test is to be expected, but it will cause some to worry when their regression tests fail. Thoughts? - Brandon b. palmer, [EMAIL PROTECTED] pgp: www.crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
[HACKERS] source version?
No luck on general, so I'll try here: I'm trying to figure out what version of a source code I have. I know it's a 7.2 release, but how can I find out of it's 7.2, 7.2.3, 7.2.4, etc. FROM THE SOURCE CODE, not from compiling (it doesn't compile, it's testing code). Thanks - Brandon c: 917-697-8665h: 201-435-6226 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(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: [HACKERS] We're finally there ...
> 'k, I just tag'd REL7_4 and built the bundles ... the files are available > under ftp://ftp.postgresql.org/pub/source/v7.4beta, and I've open'd up the > ftp server there to 100 connections so that ppl can get in and test it ... ftp3.us.postgresql.org is in sync as well if anyone is interested. 10M connection. - Brandon c: 917-697-8665h: 201-435-6226 b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5 ---(end of broadcast)--- TIP 8: explain analyze is your friend
[HACKERS] porting from 7.2 -> 7.4
I'm trying to port some replication code from 7.2 -> 7.4 and am running
into a block.
In the file:
/src/backend/tcop/postgres.c
My diff was for:
void
pg_exec_query(char *query_string)
{
pg_exec_query_string(query_string, whereToSendOutput,
QueryContext);
}
But the pg_exec_query_string function seems to have left. Can someone
share with me insight as to what it has been replaced by?
Thanks,
- Brandon
c: 917-697-8665h: 201-435-6226
b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
