Re: [PATCHES] [HACKERS] Fix linking of OpenLDAP libraries
[EMAIL PROTECTED] (Tom Lane) wrote: Albe Laurenz [EMAIL PROTECTED] writes: Here is a new patch that replaces the previous one; it adds two macros LDAP_LIBS_FE and LDAP_LIBS_BE for frontend and backend, respectively. I did not only add them to the Makefile for interfaces/libpq, but also everywhere something is linked against libpq in case somebody links static. Applied, but without that last part. It builds OK for me on Darwin, which is moderately picky about that sort of thing, but someone should try AIX. I'd like to, but that has to take second place to Slony-I activity next week; I'll see about putting that on my ToDo list. (After SSL, readline...) -- output = (cbbrowne @ gmail.com) http://linuxdatabases.info/info/emacs.html Send messages calling for fonts not available to the recipient(s). This can (in the case of Zmail) totally disable the user's machine and mail system for up to a whole day in some circumstances. -- from the Symbolics Guidelines for Sending Mail ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] New variable server_version_num
Quoth [EMAIL PROTECTED] (David Fetter): On Tue, Aug 01, 2006 at 12:37:48PM -0500, Jim C. Nasby wrote: On Sun, Jul 30, 2006 at 11:27:33AM -0400, Tom Lane wrote: David Fetter [EMAIL PROTECTED] writes: On Sat, Jul 29, 2006 at 09:44:10PM -0400, Tom Lane wrote: The correct solution is for client-side libraries to provide the feature. Not if the app is written in SQL, as the bootstrap, regression test, etc. code for modules frequently is. SQL doesn't really have any conditional ability strong enough to deal with existence or non-existence of features. What are you hoping to do, a CASE expression? Both arms of the CASE still have to parse, so I remain unconvinced that there are real world uses. CREATE OR REPLACE FUNCTION version_new_enough( in_version INTEGER ) RETURNS BOOLEAN LANGUAGE sql AS $$ SELECT COALESCE( s.setting::INTEGER, /* Cast setting to integer if it's there */ $1 - 1 /* Otherwise, guarantee a lower number than the input */ ) = $1 FROM (SELECT 'server_version_num'::text AS name) AS foo LEFT JOIN pg_catalog.pg_settings s ON (foo.name = s.name) $$; There's also plpgsql, which afaik has no way to get the version number (other than slogging though the output of version()). Right. String-mashing is great when you have to do it, but this patch sets it up so you don't have to. :) There's *some* data to be gotten from select setting from pg_catalog.pg_settings where name = 'server_version'; Seems to me that value isn't without its uses... [EMAIL PROTECTED]:pgsql-HEAD/doc/src/sgml for port in 5432 5533 5532 5882; do for psql -p $port -h localhost -d template1 -c select '$port', setting from pg_catalog.pg_settings where name like 'server_version'; for done ?column? | setting --+- 5432 | 7.4.13 (1 row) ?column? | setting --+- 5533 | 7.4.10 (1 row) ?column? | setting --+- 5532 | 8.0.5 (1 row) ?column? | setting --+-- 5882 | 8.2devel (1 row) If I wanted to, it oughtn't be difficult to string smash those settings into something very nearly useful... -- cbbrowne,@,gmail.com http://linuxfinances.info/info/rdbms.html in your opinion which is the best programming tools ? The human brain and a keyboard. -- Nathan Wagner ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] Replication Documentation
[EMAIL PROTECTED] (Peter Eisentraut) wrote: Chris Browne wrote: Here's a patch to add in the material on replication recently discussed on pgsql.docs. I'm not thrilled that there were only a few comments made; I'd be happy to see slicing and dicing to see this made more useful. The agreed-to process was 1. post information on pgsql-general 1.a. solicit comments 2. put information page on web site 3. link from documentation to web site You seem to have short-circuited all that. I don't think this sort of material belongs directly into the PostgreSQL documentation. I don't recall that anyone agreed to do anything in particular, let alone the process being formalized thus. Bruce was looking for there to be some form of overview of the free replication options so he'd have some kind of tale to tell about it. Apparently the issue comes up fairly frequently. 1. I posted information on pgsql-docs 1.a. I solicited comments 2. There being not many of those, I have put together something that could fit into the documentation. I frankly don't care all that much where the material goes; if it ought to be some place else other than in the documentation tree proper, I'm fine with that. -- select 'cbbrowne' || '@' || 'gmail.com'; http://linuxdatabases.info/info/postgresql.html How much more helpful could I be than to provide you with the appropriate e-mail address? I could engrave it on a clue-by-four and deliver it to you in Chicago, I suppose. -- Seen on Slashdot... ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PATCHES] AIX FAQ addition
Chris Browne wrote:
We haven't seen any agreement emerge as to what is causing AIX 5.3 ML3
to fail to successfully build the release candidates.
However, a patch has emerged (thanks, Seneca!) that does allow it to
work, and which I'd expect to be portable (better still!).
We are still actively pursuing why it breaks, but supposing that still
remains outstanding, at least the following would allow AIX users to
better survive a build...
I can confirm that with that patch applied 8.1RC1 builds and passes a
complete run of the buildfarm-script(including plpython and with a
simple makefile-fix plperl) compiled with gcc 4.0.2 and xlc.
So I think we should definitly add this to the FAQ at least.
Actually, there is a reason NOT to apply the patch in general on all
platforms; it introduces logic (an if {} else {} statement) in a place
where there wasn't previously one, which *presumably* slows things
down somewhat. I don't know if the memcpy() calls are invoked so
often as to make this material; it's hard to tell.
--
(reverse (concatenate 'string moc.liamg @ enworbbc))
http://linuxfinances.info/info/wp.html
Whenever you find that you are on the side of the majority, it is
time to reform. -- Mark Twain
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Re: [PATCHES] CVS should die
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Tom Lane)
transmitted:
Alvaro Herrera [EMAIL PROTECTED] writes:
Can this be discussed for 8.1?
It's been discussed, and rejected, several times already. There
aren't any alternatives that are enough better than CVS to be worth
the changeover effort.
Subversion may be getting close to the point where it may be worth
thinking of, and there is a pretty full-featured conversion scheme,
cvs2svn, allowing considerable choice as to what aspects of the CVS
branches will be included.
The one traditional _enormous_ problem with it was that while
much-lauded, it suffered interoperability issues. People running
different versions of {Debian|RHAT|FreeBSD|...} could have versions
that couldn't talk to one another. That appears to have been
alleviated:
Now that subversion has reached 1.0.0 our compatibility guarantees
require forward and backward compatible repository formats for all
patch releases and backward compatible for minor releases. So
until 2.0.0 comes out there will be no change that should require a
dump for upgrading to newer versions.
I'll buy the argument that it'll take some work for people familiar
with CVS to get familiar with SVN. Of course...
Generally, Subversion's interface to a particular feature is
similar to CVS's, except where there's a compelling reason to do
otherwise.
I have been watching Subversion develop for quite some time, and have
always felt it the right idea to put usage off because it did not
appear mature enough. I have always thought in another year, it may
be ready. As far as maturity is concerned, it looks like it's there
now. The formerly compelling reasons for instant rejection are no
longer there.
If it's plausible to run a SVN archive, in parallel, that can accept
patches coming out of the present CVS, it must surely be time for some
intrepid fan of Subversion to put up an an archive and start showing
off how much better it is. Proving it's viable by demonstration is a
pretty ideal methodology, no?
By the way, one of the longer term goals is for SVN to support a SQL
repository backend; there's probably merit to some common dogfood
usage ;-).
--
(reverse (concatenate 'string gro.gultn @ enworbbc))
http://linuxfinances.info/info/unix.html
Are we worried about Linux? ... Sure we are worried.
-- Steve Ballmer, VP of MICROS~1 at Seybold publishing conference
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [PATCHES] pg_generate_sequence and info_schema patch (Was: SELECT
Clinging to sanity, [EMAIL PROTECTED] (Christopher Kings-Lynne) mumbled into her beard:
I think you can provide a precise specification without losing
simplicity of explanation. Maybe something like
When step is positive, zero rows are returned if start stop.
Conversely, when step is negative, zero rows are returned if
start stop. It is an error for step to be zero.
Having something that generates a list of dates would be handy,
however I guess you can do it with the current series generator by
adding that many day intervals to a base date...
Yes, that would be the way to do it.
Having generators (I'm not clear yet on whether it's more like Icon
generators or Common Lisp SERIES, or APL iota :-)) is a very useful
thing indeed.
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','ntlug.org').
http://www3.sympatico.ca/cbbrowne/wp.html
One often contradicts an opinion when what is uncongenial is really
the tone in which it was conveyed. -- Nietzsche
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
[PATCHES] Some Documentation Changes
was observed by Great Britain and Dominions + (including what is now the USA) in 1752. Thus 2 September 1752 was + followed by 14 September 1752./para - This is why Unix systems have the commandcal/command program - produce the following: + para This is why Unix systems have the commandcal/command + program produce the following: screen $ userinputcal 9 1752/userinput @@ -1094,19 +1094,24 @@ /para /note - para - Different calendars have been developed in various parts of the - world, many predating the Gregorian system. + para Different calendars have been developed in various parts of + the world, many predating the Gregorian system./para - For example, - the beginnings of the Chinese calendar can be traced back to the 14th - century BC. Legend has it that the Emperor Huangdi invented the - calendar in 2637 BC. + para For example, the beginnings of the Chinese calendar can be + traced back to the 14th century BC. Legend has it that the Emperor + Huangdi invented the calendar in 2637 BC./para - The People's Republic of China uses the Gregorian calendar - for civil purposes. The Chinese calendar is used for determining - festivals. + para The People's Republic of China uses the Gregorian calendar + for civil purposes. The Chinese calendar is used for determining + festivals. /para + + para If you are interested in this sort of thing, citation + Calendrical Calculations: The Millennium Edition /citation by by + Edward M. Reingold and Nachum Dershowitz is an excellent reference, + describing some 25 calendars, and providing software for displaying + them and converting between them./para + /sect1 /appendix -- let name=cbbrowne and tld=libertyrms.info in String.concat @ [name;tld];; http://dev6.int.libertyrms.com/ Christopher Browne (416) 646 3304 x124 (land) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
