On Tuesday 12 April 2011 01.02:35 Lucas Cotta wrote: Does postgre execute the queries following a execution plan tree, where the leafs are table scans, and the nodes are joins? yes, see the EXPLAIN SQL command (EXPLAIN SELECT * FROM ), it will shwo this tree. http://www.postgresql.org/docs/9.0/static/sql-explain.html cheers -- vbi -- The woman you buy -- and she is the least expensive -- takes a great deal of money. The woman who gives herself takes all your time. -- Balzac signature.asc Description: This is a digitally signed message part.
Hi, On Wednesday 06 April 2011 20.31:38 Joshua D. Drake wrote: postgres:ssl://localhost:5432/template1/?username=jdpassword=foobarssl= true But I don't know if we want to go there. I would expect that *if* an URI syntax becomes implemented, it should support all possible options. Especially things like ssl but also connecting via Unix socket instead of TCP should be covered. Else applications would need to offer one way to specify the usual connection and another way to offer configuration with special requirements such as connection to unix socket or via ssl. (... which would probably not be supported by many applications, since everybody connects to localhost:5432 anyway... -- vbi -- FORTUNE REMEMBERS THE GREAT MOTHERS: #6 Johnny, if you fall and break your leg, don't come running to me! -- Mrs. Emily Barstow, June 16, 1954 signature.asc Description: This is a digitally signed message part.
Heyho! On Friday 01 April 2011 02.39:25 Christopher Browne wrote: An advantage to this uri form is that it allows applications to be configured uniformly - I do not need to ask is this using libpq, needing one sort of configuration, or Java, needing another? Rather, I may say, here is a uri I may use with any of my applications Since URI stings are popular, it might really make sense if pg could recommend a preferred form of postgres URI strings (and obviously implement it in libpq). For the non-libpq APIs (there's at least http://python.projects.postgresql.org/, don't know about others), it would still be just a recommendation that they could follow or not follow, so the situation wouldn't change too much from today, I fear. cheers -- vbi -- East Indians sometimes see Heaven as a giant bureaucracy, and frequently report being sent back because of clerical errors. http://scienceblogs.com/cortex/2007/01/culture_and_neardeath_experien.php signature.asc Description: This is a digitally signed message part.
[adding webmaster to cc] On Tuesday 08 March 2011 21.20:20 Andres Freund wrote: create account, ... Its linked on the mainpage: http://www.postgresql.org/community/signup Hmm. Could it be that this web form doesn't have a mail queue and thus doesn't retry to send the mail when the first attempt was denied by greylisting? And now it says user already exists... (At least: I hven't seen a retry for 4h, first mail was rejected at 08:42 +0100) cheers -- vbi -- featured product: Debian GNU/Linux - http://debian.org signature.asc Description: This is a digitally signed message part.
On Wednesday 09 March 2011 13.05:55 Magnus Hagander wrote: I see a graylisted email that's in the queue... I'll give it a kick, but normally you jsut have to wait... Thanks, it arrived. I'm used to wait when I enable greylisting. 4h delay is rare, though. greets -- vbi -- I liken ISPs to sausage factories. You know what goes in, and you think that what comes out is tasty, but by Apollo's unwashed speedos you DON'T want to know what goes on in between. -- Sid Dabster signature.asc Description: This is a digitally signed message part.
Heyho! I'm poking around a bit in PostgreSQL's source for curiosity's sake. Is there a short howto on how to start / debug postgres from within the unpacked/compiled tar? Are there scripts that set up linker paths and Postgres' environment? thanks in advance -- vbi -- This statement is false. signature.asc Description: This is a digitally signed message part.
Hi, On Tuesday 08 March 2011 15.39:56 Kevin Grittner wrote: http://wiki.postgresql.org/wiki/Developer_FAQ thanks If you still have questions, be sure to mention your OS. Sorry, forgot. Linux. The Basic system testing item is where I'm kinda stuck. You advise to perform run time testing via psql. Which is a bit short, since obviously psql can't be directly started since there is no installation... Aagain, my question: are there wrappers/helpers to do this easily from the source/compile tree? Like: set up PATH, LD_LIBRARY_PATH, PG_WHATEVER, call initdb, ... Or do you advise to just make install and test from there? thanks -- vbi -- [...] if you have to do the occasional model for Japanese collectors, which are covered in reticulated ostrich testicle leather, then by all means continue to do so. -- Michael Reichmann http://www.luminous-landscape.com/essays/leica-open-letter.shtml signature.asc Description: This is a digitally signed message part.
Hi, On Tuesday 08 March 2011 16.58:58 Kevin Grittner wrote: Adrian von Bidder avbid...@fortytwo.ch wrote: Or do you advise to just make install and test from there? Pretty much. Thanks for all your answers. I was just a bit confused because when I write stuff for myself I usually set up stuff to run directly in the build environment, so I was expecting something like that to be available. But make install into ~/pg will do fine as well. (I want to avoid having my trashed version version be available systemwide...) cheers -- vbi -- I've never been DPL (AFAICT) -- Pierre Habouzit on debian-vote, 2007-07-31 signature.asc Description: This is a digitally signed message part.
Heyho again! Now this kind of stuff is what I was after :-) On Tuesday 08 March 2011 19.04:53 Kevin Grittner wrote: That reminds me -- Greg Smith put something together which might make it easier to get started: https://github.com/gregs1104/peg/ Since you don't allow anonymous editing of the wiki, nor have an obvious create account, I leave it to you to add this: +++ How can I easily test my modified postgres version? You'll want to install PostgreSQL into a local directory (in your home directory, for instance) to avoid conflicting with a system wide installation. Use the --prefix=... option to specify an installation location; --with-pgport to specify a non-standard default port may also be helpful. To run this instance, you will need to make sure that the correct binaries are used; depending on your operating system, environment variables like PATH and LD_LIBRARY_PATH (on most Linux/Unix-like systems) need to be set. Setting PGDATA will also be useful. To avoid having to set this environment up manually, you may want to use Greg Smith's [href=https://github.com/gregs1104/peg peg] scripts, or the [https://github.com/PGBuildFarm/client-code scripts] that are used on the buildfarm. +++ ... and you'll never have to answer to this stupid question again ... :-) thanks happy hacking -- vbi P.S.: those who remember me from many months back may guess that I'm trying to implement IMMUTABLE columns. But I'll come back when I actually have to show something, so far I've only managed to break 121 of 124 tests of make check. At least initdb miraculously works again. -- this email is protected by a digital signature: http://fortytwo.ch/gpg signature.asc Description: This is a digitally signed message part.