Clinging to sanity, [EMAIL PROTECTED] (Hannu Krosing) mumbled into her beard:
> Ühel kenal päeval, T, 2006-06-06 kell 08:42, kirjutas Mark Woodward:
>> OK, here's my problem, I have a nature study where we have about 10 video
>> cameras taking 15 frames per second.
>> For each frame we make a few t
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Bruno
Wolff III) transmitted:
> On Tue, May 30, 2006 at 16:52:09 -0400,
> Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>>
>>
>> One of the first things an IT Executive Recruiter needs to learn is
>> where to post job info -
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (John F
Rizzo) transmitted:
> I posted this in other lists with no response... Can anyone help?
> I'm having trouble getting plperl to work on AIX 5.3.2.
> Postgresql Version: 8.1.1
> Perl Version: 5.8.7
> I've rebuilt perl a
The world rejoiced as [EMAIL PROTECTED] ("Gustavo Tonini") wrote:
> Ozsu show us some solution for the problem in the book "Principles of
> distributed database systems".
Would it be "telling" to outline some of the solutions he suggests?
--
(format nil "[EMAIL PROTECTED]" "cbbrowne" "gmail.com")
Quoth [EMAIL PROTECTED] ("Marc G. Fournier"):
> Just curious, but how do ppl come to Canada as tourists from other
> countries? I don't imagine they need to be "invited" by a Canadian,
> do they?
Well, the "invitation" thing doesn't apply at all to people from North
America or Western Europe; it'
In an attempt to throw the authorities off his trail, pgman@candle.pha.pa.us
(Bruce Momjian) transmitted:
> Jan Wieck wrote:
>> We've been there before, and not only once. I wonder why we still find
>> more of these, because every time it comes up I agree to removal of it.
>
> Perhaps your name r
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Greg Stark)
wrote:
> Are you sure that "Temporary Resident Visa" is what you need?
> Isn't the regular visa people get called just a "Guest Visa"?
That's possible too... It is probably a good idea to contact a local
Canadian embassy
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] ("Zeugswetter Andreas
DCP SD") would write:
>> > But what about index clearing? When do you scan each index?
>>
>> At the end of each iteration (or earlier, depending on
>> maintenance_work_mem). So for each iteration you would need
>>
The world rejoiced as [EMAIL PROTECTED] ("Marc G. Fournier") wrote:
> Just curious, but what is involved in these "invitations"? For
> instance, is there a limit on # of invitations any one person(?) or
> company can issue? Are there any legal implications of issuing such
> an invitation? I coul
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Tom Lane) would
write:
> I thought we had sufficiently destroyed that "reuse a tuple" meme
> yesterday. You can't do that: there are too many aspects of the system
> design that are predicated on the assumption that dead tuples do not
> c
[EMAIL PROTECTED] (Mark Kirkwood) wrote:
> Do you need name, value pairs? I was thinking that something like:
>
> # Postgres Cluster Registration
> #
> # PG_HOME PGDATA PORT
> /usr/local/pg7.4.1 /vol01/pggeo 5435
> /usr/local/pg7.4.1 /vol01/pgicdmdb 5434
> /usr/local/pg7.4.1 /vol03/pg7
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] ("Mark Woodward")
belched out:
>> Mark Woodward wrote:
> Like I have repeated a number of times, sometimes, there is more than one
> database cluster on a machine. The proposed pg_clusters.conf, could look
> like this:
>
> pg_clusters.con
In the last exciting episode, [EMAIL PROTECTED] (Mark Kirkwood) wrote:
> Mark Woodward wrote:
>> I'm not sure that I agree. At least in my experience, I wouldn't
>> have more than one installation of PostgreSQL in a production
>> machine. It is potentially problematic.
>
> I agree with you for prod
Quoth [EMAIL PROTECTED] ("Mark Woodward"):
>> Mark Woodward wrote:
>>> As a guy who administers a lot of systems, sometimes over the span of
>>> years, I can not understate the need for "a" place for the admin to
>>> find
>>> what databases are on the machine and where they are located.
>>>
>>> Yo
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED]
("Joshua D. Drake") transmitted:
>>>
>>> Slony-I would move there fairly quickly upon availability of SVN; a
>>> lot of our folks would be pretty keen on storing things in SVN.
>>> *That* is about the only thing holding off mi
A long time ago, in a galaxy far, far away, pgman@candle.pha.pa.us (Bruce
Momjian) wrote:
> Tom Lane wrote:
>> Thomas Hallgren <[EMAIL PROTECTED]> writes:
>> > Bruce Momjian wrote:
>> >> Having run had both pgfoundary and gborg for several years, I think we
>> >> have to conclude that any clean mi
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Andrew Dunstan)
would write:
> If we could get to be running pgFoundry on the latest GForge, with
> PHP/CGI enabled project web pages, a database per project available,
> SVN as well as CVS, and a known stable mailman release we'd be in
>
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Tom Lane) would
write:
> I said:
>> The oldest thing I can actually document at the moment
>
> After further digging, I found something older: conclusive proof that
> I was present at the invention of the smiley. I've been heard to asser
>> On Feb 8, 2006, at 11:17 , Merlin Moncure wrote:
>>
>> > The proper SQL construct without row constructor is:
>> >
>> > select * from t where
>> > a >= a1 and
>> > (a > a1 or b>= b1) and
>> > (a > a1 or b > b1 or c > c1)
>> > order by a,b,c limit 1^ no offset necessary
>> >
>> > confus
> Josh Berkus writes:
>> It's esoteric enough that I don't know what you're talking about. Can
>> you give us an example?
>
> He's talking about this:
> http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
Hmm...
So the example would be that if you have just read a record fr
> Devrim GUNDUZ wrote:
>> Hi,
>> On Mon, 2006-01-30 at 21:27 -0500, Jonah H. Harris wrote:
>>> I had to deal with an installer written in python and several in
>>> Java... IMHO, Java would be a better language for this and you could
>>> build off some nice OSS installers that already exist (such as
> Hi,
>
> On Mon, 2006-01-30 at 22:45 -0500, Vivek Khera wrote:
>> > However none of them are PostgreSQL Installers, none of them has the
>> > ability to customize the packages and none of them has the ability to
>> > install the community packages, etc. :)
>>
>> You need to take a sniff over at
> Hi,
>
> On Mon, 2006-01-30 at 19:35 -0800, Christopher Browne wrote:
>> > We are actively looking for developers for the project. Please
>> > drop me an e-mail if you want to join this project. We will use
>> > Python, so you need to be a Python guy to join
> We are actively looking for developers for the project. Please drop me
> an e-mail if you want to join this project. We will use Python, so you
> need to be a Python guy to join the project. We are in planning phase,
> if you join us earlier, we will be able to share more ideas.
You'd better de
> On 1/19/06, Pollard, Mike <[EMAIL PROTECTED]> wrote:
>> Martijn van Oosterhout wrote:
>>
>> > Please provides natural keys for any of the following:
>> >
>> > - A Person
>> > - A phone call: (from,to,date,time,duration) is not enough
>> > - A physical address
>> > - A phone line: (phone numbers a
> Chris Browne wrote:
>> Lukas Smith <[EMAIL PROTECTED]> writes:
>> > Bruce Momjian wrote:
>> >
>> >> * Flush cached query plans when the dependent objects change,
>> >> when the cardinality of parameters changes dramatically, or
>> >> when new ANALYZE statistics are available
>> >
>> > W
> Lukas Smith <[EMAIL PROTECTED]> writes:
>> Bruce Momjian wrote:
>>> * Flush cached query plans when the dependent objects change,
>>> when the cardinality of parameters changes dramatically, or
>>> when new ANALYZE statistics are available
>
>> Wouldn't it also make sense to flush a cached query
>> Ofcourse, this is another can of worms. To do this you would have to be
>> able to have the failed query provide hints to the planner telling it
>> where it went wrong. Now, it may be possible to provide (via
>> post-mortem of an execution) a list of actual selectivites like:
>
> Just being able
> http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=297
I saw it in print; the only thing that seemed interesting about it was
the recommendation that query optimization be biased towards the
notion of "stable plans," query plans that may not be the most
"aggressively fast," but whi
> Are you sure that no way to implement a generic aproach on the
> backend? What does specification say?
What specification are you talking about?
> Does Oracle 10g have a core implementation of replication (cluster)?
Since replication is sold as a separate product from Oracle 10g,
obviously not
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] ("Jonah H.
Harris") wrote:
> I don't recommend discussion for this in this thread, but it could
> also tie in with the packages support we've discussed and (although
> some may argue this), compiling the PL to bytecode and using that.
In the last exciting episode, dpage@vale-housing.co.uk ("Dave Page") wrote:
>> But then dbas will block off access to that db, or drop it and
>> we're back to square one...
>
> That's their choice though, and it would then be up to them to
> provide an alternative for their users (there's nothing t
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Andreas Pflug)
wrote:
> Magnus Hagander wrote:
>>> I dislike the name pg_system because it implies that that DB is
>>> somehow special from the point of view of the system ... which is
>>> exactly what it would *not* be.
>> That I can c
[EMAIL PROTECTED] (Gavin Sherry) wrote:
> I guess the main point is, if something major like this ships in the
> backend it says to users that the problem has gone away. pg_autovacuum is
> a good contrib style solution: it addresses a problem users have and
> attempts to solve it the way other user
> > Incidentally I havent seen any objections, if there are none should we
> > go ahead and whip up an email to google? Do we want to run this through
> > the foundation? ISTM we would, though I don't know the full extent of
> > what ramifications that would have.
>
> No, the Foundation wasn't
[EMAIL PROTECTED] ("Jeffrey W. Baker") wrote:
> On Mon, 2005-05-30 at 21:38 -0700, Luke Lonergan wrote:
> After reading this very comprehensive benchmark:
>
> http://print.tweakers.net/?reviews/557
>
> I purchased one of the Areca controllers with a large battery-backed
> cache. It is unholy fast.
Centuries ago, Nostradamus foresaw when josh@agliodbs.com (Josh Berkus) would
write:
> Look at other large projects with lots of options. Apache, Perl, Linux,
> Java,
> emacs, KDE, etc., all of them strike a balance between including stuff and
> leaving stuff as add-ins (some more narrowly tha
The world rejoiced as [EMAIL PROTECTED] ("Andrew Dunstan") wrote:
> As for CVS - if we can't do development the way we want using it
> then it's time to replace it. I have been convinced for quite a
> while that it is living on borrowed time, but I am far less certain
> about what should be used to
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] belched out:
> On Sun, 1 May 2005 14:35:37 -0500
> Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>>On Sun, May 01, 2005 at 19:57:37 +0300,
>> [EMAIL PROTECTED] wrote:
>>>
>>> Listen Tom, write a client software that releases the
>>> resour
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] would write:
> We sometime discuss here for geographic system datatypes
> and feature. First, a database must have real database
> features, not extreme features.
Oh, but it would be so much better if we could call the next version
"Postg
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] ("Jim C. Nasby")
wrote:
> Anyone interested in pooling funds for features should take a look at
> http://people.freebsd.org/~phk/funding.html, which is about a FreeBSD
> developer who offered to work full-time on developing some specific
The world rejoiced as matthew@zeut.net ("Matthew T. O'Connor") wrote:
> Marc G. Fournier wrote:
>
>> On Fri, 29 Apr 2005, Christopher Browne wrote:
>>
>>> Some reasonable approximations might include:
>>> - How much disk I/O was recorded
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] ("Marc G.
Fournier") wrote:
> I know one person was talking about being able to target only those
> that pages that have changes, instead of the whole table ... but some
> sort of "load monitoring" that checks # of active connections and
In the last exciting episode, pgman@candle.pha.pa.us (Bruce Momjian) wrote:
> o integrated auto-vacuum (Bruce)
If this can kick off a vacuum of a Very Large Table at an unfortunate
time, this can turn out to be a prety painful misfeature.
What I'd _really_ love to see (and alas, it's beyond
The world rejoiced as [EMAIL PROTECTED] ("Jim C. Nasby") wrote:
> On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
>> >Is it really an important area to improve, or are there other
>> >priorities? I know some people wished we had better support for
>> >inheritance, but how strong
Clinging to sanity, [EMAIL PROTECTED] (ElayaRaja S) mumbled into her beard:
> Hi,
> I am using Redhat Linux 9, I need to uninstall postfesql 7.3.2 and
> i have to install postgresql 7.4.5. Plz let me know how to uninstall
> completely - postfesql 7.3.2
>
> I am getting as [EMAIL PROTECTED] root]
The problem that persists with this is that it throws in extra
processing at the time that the system is the _most_ busy doing
updates, thereby worsening latency at times when the system may
already be reeling at the load.
I think, as a result, that VACUUM will _have_ to be done
asynchronously.
W
[EMAIL PROTECTED] (Rod Taylor) wrote:
> It's a fairly limited case and by no means removes the requirement for
> regular vacuums, but for an update heavy structure perhaps it would be
> worth while? Even if it could only keep indexes clean it would help.
The problem that persists with this is that
[EMAIL PROTECTED] (Gaetano Mendola) wrote:
> Hi all,
> running a 7.4.5 it happen to me with another table
> where a single vacuum full was not freeing enough pages,
> here the verbose vacuum full, as you can see only at
> the end: truncated 8504 to 621 pages.
>
> I use pg_autovacuum and it's not e
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] ("Qu Tianlian")
wrote:
> Hi all:
> I have a question.
> How to add table in slony.
> I try to add table in already being database that using slony . but it's not
> realize table's replication.
> I used postgresql version 7.4.2 and slony
I can see this function available in the backend:
TransactionId GetOldestXmin(bool alldbs);
The cost is based on walking thru each backend process, which I guess
is obvious, as if there are 47 backends, that means 47 xids.
Presumably not _too_ expensive; certainly something that has to be run
In an attempt to throw the authorities off his trail, Christopher Browne
<[EMAIL PROTECTED]> transmitted:
> It sure would be nice to be able to have a way to query the start
> time of the eldest transaction on the system.
I can see this function available in the backend:
T
I was thinking about one of the "pathological cases" where Slony-I
behaves badly, and had an optimization thought...
There is a cleanup loop that (commonly) runs every 10 minutes or so
and vacuums the tables that are used by the replication application.
If there is some long-running transaction k
There is a cleanup loop that (commonly) runs every 10 minutes or so
and vacuums the tables that are used by the replication application.
If there is some long-running transaction kicking around, this will
keep that from actually cleaning things out.
Consider the scenario where the system is prett
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Hans-Jürgen
Schönig) wrote:
> I think it is important not to think in dogmas (in this case this
> means SQL syntax is always better) - there should be a reasonable
> compromise between compatibility and standard.
> My compromise would
Oops! [EMAIL PROTECTED] (Tommi Maekitalo) was seen spray-painting on a wall:
> Hi,
>
> I just read about this IBM-patent-issue at www.heise.de. IBM grants
> this patens to all projects, which follow one of the licenses, which
> are approved by the open-source-initiative. And the BSD-license is
> as
[EMAIL PROTECTED] (Mark Wong) wrote:
> http://www.linuxsymposium.org/2005/
I'd be interested in being in on a BOF there; that's already a
convenient time for me to seek to be in Ottawa, as one brother will be
"conferencing" (as it were) at Connaught Ranges that week.
I notice, by the way, t
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Manfred Koizar)
would write:
> On Mon, 24 Jan 2005 08:28:09 -0700, "Jonah H. Harris" <[EMAIL PROTECTED]>
> wrote:
>>UPDATE pg_user_table_counts
>>SET rowcount = rowcount + 1
>>WHERE schemaname =
After a long battle with technology, [EMAIL PROTECTED] (Benjamin Arai), an
earthling, wrote:
> What are the goals for 8.1?
8.0.0 was only just released, so attention is focused for now on
whatever falls out as early returns...
It's early for the future work to be overly clear.
Things that look
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Jeff Davis) wrote:
> I almost think to not supply an MVCC system would break the "I" in ACID,
> would it not? I can't think of any other obvious way to isolate the
> transactions, but on the other hand, wouldn't DB2 want to be ACID
> com
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Travis P) would
write:
> Now, on my AIX 5.1 system, /usr/bin/ cc and cc_r are both just
> symlinks back to /usr/vac/bin/xlc. The different program names just
> invoke the different settings. Brad: can you make such a symlink and
> compi
That would require that xlc be installed. Neither cc, cc_r, xlc, nor
xlcc (or maybe it was xlcpp?) are available on the systems Brad and I
are using, so that symlink will not work.
As a result, _none_ of these may be remotely considered to be
"universal answers" on AIX.
In effect, there are two
ed a "standard component" that you can expect to find
available on AIX systems in general. It's only available if it has
been purchased.
--
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
---(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
Oops! [EMAIL PROTECTED] (Bruce Momjian) was seen spray-painting on a wall:
> That could be part of auto-vacuum. Vacuum itself would still
> sequential scan, I think. The idea is to easily grab expire tuples
> when they are most cheaply found.
The nifty handling of this would be to introduce "VAC
Oops! vertigo <[EMAIL PROTECTED]> was seen spray-painting on a wall:
> Hello
> I need to "pg_dump" my database, but i want only to receive sql
> commands which will insert row which were inserted into database
> today. Is there any way to do it ?
> I have large database and i want to make "incremen
[EMAIL PROTECTED] ("Ed L.") wrote:
> Wow. First, thanks again for all your efforts, Jan. Second, I'm
> disappointed to hear the slony author and lead developer is leaving
> the slony leadership. When is that going to happen? And what does
> that mean with respect to your future involvement in s
Clinging to sanity, [EMAIL PROTECTED] mumbled into her beard:
> I would like to know if there are any discussions about
> creating an embedded version on postgresql. My thoughts
> go towards building/porting a sqlite equivalent of pg.
People periodically "drive by" and suggest that PostgreSQL woul
In the last exciting episode, [EMAIL PROTECTED] (Yui Hiroaki) wrote:
> I would like to install PostgreSQL. But my pc does not have much
> space. So I would like to make compact PostgreSQL. Does anyone know
> how to make compact PostgreSQL? For example, to make comment out
> source code and compile
After a long battle with technology, [EMAIL PROTECTED] (Bruce Momjian), an earthling,
wrote:
> config/acx_pthread.m4 should be testing all those thread flags and
> defining proper Makefile.global values for them. Do you want to
> send me your config.log offline or check ourself why the tests
> ar
Quoth [EMAIL PROTECTED] (Tom Lane):
> Chris Browne <[EMAIL PROTECTED]> writes:
>> We have discovered an interesting locking scenario with Slony-I that
>> is pointing to a use for the ability to exclude certain schemas from
>> pg_dump.
>
>> The situation is that when a "full" pg_dump kicks off, a Sl
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] ("Marc G. Fournier") would
write:
> On Sat, 4 Sep 2004, Gaetano Mendola wrote:
>> Hi all,
>> now that Apache Portable Runtime was release why don't
>> use it on Postgres?
>
> Short question: why? what does it give us, other then potential
Centuries ago, Nostradamus foresaw when Murat Kantarcioglu <[EMAIL PROTECTED]> would
write:
> For our research project, I need to implement an encryption support
> for Postgressql. At this current phase, I need to at least support
> page level encryption In other words, each page that belongs to
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Jaime Casanova) would write:
> By the way, will be a way in postgresql 8 to add a
> column in a middle of a table. just curious.
What do you mean by "in a middle of a table?" A relation is simply a
set of attributes that _don't_ forcibly
After a long battle with technology, [EMAIL PROTECTED] (Andrew Dunstan), an earthling,
wrote:
> Bruce Momjian wrote:
>
>>I have shortened your paragraph to:
>>
>>Because Win32 is significantly different from the Unix platforms
>>supported in previous releases, this port might have
Clinging to sanity, [EMAIL PROTECTED] (Shahbaz Javeed) mumbled into her beard:
> # This message was accidentally sent only to Bruce. It's pasted here
> for comment from the rest of the list too :)
>
> Folks,
>
> While on the topic of Ingres and open source, I was wondering
> whether there's intere
In the last exciting episode, [EMAIL PROTECTED] (Bruce Momjian) wrote:
> Tom Lane wrote:
>> Christopher Browne <[EMAIL PROTECTED]> writes:
>> > Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
>> >> Why? I understood that usin
Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
> On Mon, Aug 09, 2004 at 09:30:09AM +0200, Peter Eisentraut wrote:
>> Tom Lane wrote:
>> > I haven't seen any particular reason why we should adopt another SCM.
>> > Perhaps BitKeeper or SubVersion would be better for
After takin a swig o' Arrakan spice grog, Gaetano Mendola <[EMAIL PROTECTED]> belched
out:
> Peter Eisentraut wrote:
>
>> Alvaro Herrera wrote:
>>
>>>What was the rule for increasing the first number after just before
>>>7.0?
>> That was just to avoid having to release a 6.6.6, which Jan had
>> cl
[EMAIL PROTECTED] (Tom Lane) wrote:
> Does anyone have a problem with this macro syntax? The try/catch
> names are stolen from Java, so I'm figuring they won't terribly
> surprise any modern programmer, but I'm open to different names if
> anyone has a better idea.
Mitch Bradley, once of Sun, onc
A long time ago, in a galaxy far, far away, Gaetano Mendola <[EMAIL PROTECTED]> wrote:
>> I was thinking of something much simpler where Jan would create an
>> ARC patch against 7.4.X and have it either in /contrib for 7.4.X or
>> on our ftp servers, or on a web site. I could create a mechanism
>>
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Jaime Casanova) would write:
> Can anyone tell me if postgresql has problems with xeon processors?
>
> If so, there is any fix or project of fix it?
Well, there's a known issue that IA-32 systems with more than 4GB of
memory use an extensi
Quoth [EMAIL PROTECTED] (Bruce Momjian):
> Andrew Sullivan wrote:
>> On Thu, Jun 17, 2004 at 01:12:10PM -0400, Bruce Momjian wrote:
>>
>> > Well, the bad news is that this backtrace isn't very useful.
>>
>> No kidding. It's pretty frustrating.
>>
>> > My only guess is that getaddrinfo in your
In the last exciting episode, [EMAIL PROTECTED] wrote:
>> [EMAIL PROTECTED] writes:
>>> Anyway, I'm not quite getting the idea of caching sequence values. I
>>> understand the performance benefits, but it seems problematic across
>>> multiple backends, almost ensuring "holes" in the sequence of num
The world rejoiced as [EMAIL PROTECTED] (Greg Stark) wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
>> Greg Stark <[EMAIL PROTECTED]> writes:
>> > This is the only place where I see hardly any movement on major
>> > items the whole development cycle, then a rush of radical changes
>> > just before
[EMAIL PROTECTED] (Bruce Momjian) wrote:
> Win32 has 98% of its code in CVS, so it will make it
> Tablespaces - Christopher says it is ready, and has run tests
> PITR - some functionality might be in 7.5, but we aren't sure
> Nested transactions - Alvaro thinks it is close,
Quoth [EMAIL PROTECTED] (Christopher Kings-Lynne):
>> Ingres is to be released as open source:
>>
>> http://developers.slashdot.org/article.pl?sid=04/05/25/0043219&mode=nested&tid=126&tid=137&tid=163&tid=185&tid=198
>
> Like the article says, I wonder if these is any synergy between the
> products.
After a long battle with technology, [EMAIL PROTECTED] ("Magnus Hagander"), an
earthling, wrote:
> 2) Pick upt he default OS timezone. This still need a little bit more
> work. But the code as it stands on Win32 will give you GMT on startup
> unless you specify a TZ in postgresql.conf. On Unix, it
After takin a swig o' Arrakan spice grog, "Anonymous" <[EMAIL PROTECTED]> belched out:
> Does anybody here know how to hack into a mysql database?
You might want to visit a mailing list devoted to MySQL; they might
know...
--
output = reverse("gro.gultn" "@" "enworbbc")
http://www.ntlug.org/~cbbr
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] ("Joshua D. Drake") would
write:
> Personally, plpgSQL is only useful to those who are coming from
> Oracle. People are more likely to be comfortable with plPython or
> plPerl than plpgSQL.
I beg to differ.
In order to use pl/Python or p
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] transmitted:
> Is anyone really ready for this sort of commitment?
By that, I presume you mean...
"Are people prepared to stop working on the doubtless useful things
that they are working on in favor of spending their time i
[EMAIL PROTECTED] ("Matthew T. O'Connor") wrote:
>> Bruce Momjian wrote:
>> Should pg_autovacuum be vacuuming temporary tables?
>
> This is a good question, and I would like some opinions from some other
> people more informed than I.
>
>> Secondly, why would
>> a temporary table for another sessio
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Tom Lane) wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> My personal opinion is that contrib should be removed entirely.
>
> That's not real workable for code that is tightly tied to the backend,
> such as the various GIST in
[EMAIL PROTECTED] (Tom Lane) wrote:
> The cure is to cast the literal to some specific type when you
> do the CREATE.
I figured that was the case, and pointed that cure back to the
developer.
What I was hoping to hear was some way of coercing the data into a
more usable type after the fact. The
In the last exciting episode, [EMAIL PROTECTED] (Kevin Brown) wrote:
> If we want to be a bit paranoid (justifiable if you've got really
> important data on the line), we could also require that a version
> string exist in the config file. If the version string doesn't match
> the version of the p
Oops! [EMAIL PROTECTED] ("J. Andrew Rogers") was seen spray-painting on a wall:
> I may be completely missing the point here, but it looks to me as
> though the PITR archival mechanism is also most of a native
> replication facility. Is there anyone reason this couldn't be
> extended to replicatio
After a long battle with technology, [EMAIL PROTECTED] ("Marc G. Fournier"), an
earthling, wrote:
> On Tue, 23 Mar 2004, Sailesh Krishnamurthy wrote:
>
>> Which brings me to another question .. has anybody considered using
>> subversion instead of CVS ?
>
> Why? not that I'm for a chance from som
In the last exciting episode, [EMAIL PROTECTED] (Jochem van Dieten) wrote:
> Josh Berkus wrote:
>> I personally don't think that a GUI tool should be the province of
>> the Slony project. Seriously. I think that Slony should focus on
>> a command-line api and catalogs, and allow the existing GUI
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Bruce Momjian) would write:
> I guess my question is that now that we have the new cache
> replacement policy, is the vacuum delay worth while. I looked at
> http://developer.postgresql.org/~wieck/vacuum_cost/ and does seem
> useful.
They
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Bruce Momjian) wrote:
> Austin Gonyou wrote:
>> As previously stated by Bruce I believe, the mindshare department needs
>> some work. For this, the PITR is a necessity, but also when comparing
>> features with other DBs that people and
Clinging to sanity, [EMAIL PROTECTED] (Andrew Rawnsley) mumbled into her beard:
> I haven't had any problems with it so far, although I haven't really
> stressed it yet. I was going to make this very plea...
>
> I agree that the syntax can probably be improved, but its familiar to
> those of us un
301 - 400 of 483 matches
Mail list logo
