Re: [HACKERS] Max inserts / sec ... on any platform?

> Build a file with 100k INSERT statements in it, and run psql -f on that > file ... no BEGIN/END in the file, just straight INSERTs ... what is the > max throughput ppl can see? H Depends. Inserting up to 5,000 of Apache log records takes no longer than a couple of wallclock minut

Re: [HACKERS] Security hole in PL/pgSQL

> Being as I was sort of the person who got EXECUTE into plpgsql... I find > it odd that people think you can execute random shell commands.. AFAICS, > EXECUTE is used to execute SQL queries (for when you don't want to cache > the query plan?) ... Got it. Thanks. Sorry for the hassle. Back lurki

Re: [HACKERS] Security hole in PL/pgSQL

> Huh? This would only be true if all operations inside plpgsql are > executed as superuser, which they are not. Seems to me the existing > defense against non-superuser using COPY is sufficient. Sorry if I missed the point, but if I got it right, Pl/Pgsql EXECUTE will allow execution of any pr

Re: [HACKERS] Security hole in PL/pgSQL

> the new EXECUTE command in PL/pgSQL is a security hole. This actually depends but I must admit that I'm concerned too. However, the responsibility for the results should be split adequately IMHO. DBAs should take care about unathorized access to PGSQL server, that's why pg_hba.conf

[HACKERS] PQprint

Hi all, Re-posting this to -hackers. Will PQprint() remain/disappear/be replaced in the future? Thx Ed -- ÌĤ¯Ç­¤ÏÁͤòÊá¤é¤Ì

Re: [HACKERS] Query cache import?

> My query cache is in usable state and it's efficient for all things > those motivate me to work on this. Well, you know, us application developers are lazy egoists, we want all of that without efforts on our side :) In fact, customers do that. They don't want to pay for both implementin

[HACKERS] Re: libpq needs -lsocket on UnixWare

> (other SVR4's prolly need -lsocket -lnsl) Something like AC_CHECK_LIB(socket,socket) or something like that? In fact, it complains about inet_aton and gethostbyname. -- contaminated fish and microchips huge supertankers on Arabian trips oily propaganda from the leaders' lip

Re: AW: [HACKERS] ALTER TABLE DROP COLUMN

> > Not a big deal, right? > > Yes a big deal. You just lost all your oids. After I hit the wall with oids for the first time, I don't refer to them anymore :) But yes, you're perfectly right, this is one more reason to have DDL completely `automated,' ie no manual substitutions. And here th

[HACKERS] Permissions, was select oid

> This is a known problem in 7.0.x (see mailing list archives for more > information). Peter E has a patch for 7.1 to remove this problem. Thanks and sorry for the hassle. While we're on it, if there's any work going on premissions (separating update/delete etc), I'd be glad to offer my help

[HACKERS] select oid .... for update ....

Here's something I don't understand If I'm missing an obvious, please feel free to kick me in the right direction. We're given two tables, linked with a foreign key. When insert is run on a master table, everything is OK, when trying to insert into a detail table, a strange query appears

RE: AW: [HACKERS] ALTER TABLE DROP COLUMN

Inoue san, > This style of "DROP COLUMN" would change the attribute > numbers whose positons are after the dropped column. > Unfortunately we have no mechanism to invalidate/remove > objects(or prepared plans) which uses such attribute numbers. 1 create table alpha( id int4, payload text ); 2