I don't believe anyone would work against this, nor could I imagine that
anyone would think it was a bad idea, I'm just curious as to how
possible it is to do ...
For most things probably not that possible. For things like:
Simple feature enhancements (preloading of libs)
Fixing pl/Language
then maybe they would be willing to donate some small amount each ($500 or
so) to pay for backporting issues. Since mostly what I'd want on an older
version would be bug / security fixes, that $500 should go a long way
towards backporting.
Sure.
I was under the imporession that 7.4
months.
Yes a commercial company could just pick it up and say ... hey we will
support it for x (Mammoth 7.3.4 is supported until 2005 for example)
but I was more looking at this from an overall community perspective.
Sincerely,
Joshua D. Drake
Robert Treat
--
Command Prompt, Inc., home
not be the case, to wit I responded:
Tom, am I on crack?
Sincerely,
Joshua Drake
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
... having to reindex the database (which 7.4 doesn't fix),
It's supposed to fix it. What are you expecting not to be fixed?
regards, tom lane
.
Separate mailing list for 7.3 issues, concerns etc... Which would help
develop it's own temporary community.
Thoughts?
Joshua D. Drake
Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
and the question as i thought was being discussed (or should be
discussed) was what is the level
,
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC
Yes, please. Please, please do not force all users to accept new
features in stable trees.
What if the feature does break compatibility with old features?
What if it is truly a new feature?
One example would be that we are considering reworking
pg_dump/restore a bit to support batch uploads
If we are going to back-patch more aggressively, we _have_ to be sure
that those back-patched releases have the same quality as all our other
releases.
I know that I am probably being semantic here but I in know way want to
be more aggressive with back patching. My
thoughts for 98% of things
Anyone see a better way?
Switch everything to mmap and pthreads and dump all this antiquated SysV IPC
and semaphore junk? *DUCK*
You are a brave soult. I salute you.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC
Postgresql support
Hello,
It seems to me that the below should not be able to happen.
postgres=# create user with encrypted password '98wq7912a';
CREATE USER
postgres=# create user with encrypted password '98wq7912a';
ERROR: CREATE USER: user name with already exists
Sincerley,
Joshua D. Drake
--
Command
Hello,
I believe that the Int8/BigInt items are known issues but I have a
knew programmer that ran into it
over the weekend (he didn't call me when he encountered the problem,
when he should of) and we have a
customer that burned some significant time on it as well. Will this be
fixed in 7.4?
Hello,
O.k. so everyone is basically in agreement of no new features to be
backported.
How do we implement a stable release maintainer for back releases? I assume
we set a scope of of what would go in security/bug fixes only?
Sincerely,
Joshua Drake
--
Command Prompt, Inc., home of Mammoth
But the kernel goes through this reliable/unreliable cycle --- they
would be better off just making the old kernel more and more reliable
and focusing on the new kernel for features.
The reliable/unreliable cycle will kill your user base.
The popularity of Linux would argue that statement a
Hello,
I have a solaris machine we could throw up for the community as well
if required.
Sincerely,
Joshua Drake
Bruce Momjian wrote:
I signed up for an account, and it has already been helpful. I wish I
had known about this years ago. I will probably put together a little
sourceforge
writer validity.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http
counts.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http
Hello,
Based on the current open items... when do we expect release?
Sincerely,
Joshua Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - [EMAIL PROTECTED] -
Hello,
Well the reason I brought it up was the rather interesting discussion
that Jan had today about Vacuum.
I was wondering if we were going to explore that before the 7.4 release?
Sincerely,
Joshua Drake
Bruce Momjian wrote:
Marc G. Fournier wrote:
On Mon, 27 Oct 2003, Joshua D. Drake
.
If I am totally off my rocker, so be it but if we were to hit the
streets with 7.4 and a vacuum that was 70% (ex)
less brutal on the machine it would be a pretty significant statement.
Yes all the other fixes are great and cool.
Sincerely,
Joshua D. Drake
Tom Lane wrote:
Barring the discovery
Sooner or later you have to say this release is done, let's ship it.
It's way too late to go back into invention mode for 7.4.
I agree with the argument. It is just that the Vacuum one... well is
very tempting.
On the 7.5 cycle though... I thought 7.5 was basically for win32?
Sincerely,
If I understood correctly, Josh was complaining about VACUUM sucking too
much of his disk bandwidth. autovacuum wouldn't help that --- in fact
would likely make it worse, since a cron-driven vacuum script can at
least be scheduled for low-load times of day. autovacuum is likely to
kick in at
the code and everything
after browser is the CVS source tree so you can look for yourself within
your copy of HEAD or 8.1 or whatever.
Sincerely,
Joshua D. Drake
Thanks
___ Navegue com o
Yahoo! Acesso Grátis, assista aos jogos
, checkpoint would
take entirely too long.
We ended up doing checkpoints every two minutes which with the increase
in checkpoint_segments and adjustment of bgwriter settings would level
out the load.
Sincerely,
Joshua D. Drake
---(end of broadcast
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
I was recently involved in a project where we had to decrease the
checkpoint_timeout . The problem was, that the database was performing
so many transactions that if we waiting for 5 minutes, checkpoint would
take entirely too long
libpg_crypto.so.0.0
Is this correct? If so I personally would like to claim this TODO.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
Joshua D. Drake wrote:
Hello,
I read this as:
1. Fix makefiles so that contrib modules such as pgcrypto are not pg_crypto
err are now
2. Move directories to reflect above
3. Fix source and makefiles within sub project directories to create
binaries and libs with correct output.. thus
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
1. Fix makefiles so that contrib modules such as pgcrypto are not pg_crypto
2. Move directories to reflect above
3. Fix source and makefiles within sub project directories to create
binaries and libs with correct output.. thus
Doesn't this exist in:
src/tools/fsync?
Do we just need to make it more user friendly?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since
.
So could I get some further definition?
Joshua D. Drake
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
So could I get some further definition?
There are two fairly strong reasons for NOT trying to push more logic
into the backend from pg_dump:
1. It would remove the freedom we currently have to make pg_dump adapt
dumps from old servers
as you can if they
are hardcoded in pg_dump, but we our existing functions seems to work
fine.
O.k. so now what I am getting from this thread is, the functions exist
now in pg_dump but we want to pull them out of pg_dump and push them
into the backend?
Joshua D. Drake
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
O.k. so now what I am getting from this thread is, the functions exist
now in pg_dump but we want to pull them out of pg_dump and push them
into the backend?
That's exactly what I *don't* want to do. If you can think of a
use-case
but I would like to get a clear definition of
what we are looking for here. Maybe:
pg_get_tabledef is the actual SQL and pg_get_tabledesc() is the column,
datatype output?
I guess I don't see the advantage of putting pg_dump -s -t in the backend.
Joshua D. Drake
user space
usable information.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
idea which I agree.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
If all you want is column, datatype, why not just use info_schema, or
newsysviews? Or even the base catalogs?
Where do I look in the info_schema? How do I know exactly what I need?
What is newsysviews?
Exactly the same arguments can
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Name and datatype was just an example. I am trying to get people to
actually provide feedback (thank you). Andrew brought up that also
including the constraints would be a good idea which I agree.
You also need rules, triggers, inheritance
functions in
pg_dump?
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Trying to get back on point. What is the scope of work for the TODO
item? Forget everything else I brought up. What is the goal of the
existing TODO?
I'm not sure that the TODO item has a reason to live at all, but surely
the first
perspective.
Anything that is going to put the stability and integrity of
pg_dump/pg_restore in *any* way, is a no op.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
it the delimiter is a tab.
Joshua D. Drake
thoughts?
cheers
andrew
---(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
No it won't, not if there are tabs in the data.
snipping noise
Hmmm then would just double quoting the data work? At least in OOCalc
(and IIRC Excel) there is the ability to select a text delimiter.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc
Bill Bartlett wrote:
Here's me speaking up -- I'd definitely use it! As a quick way to pull
data into Excel to do basic reports or analysis, a CSV format would be
great.
Why not just use ODBC?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales
two if you include the already tab delimited)
csv output it would be a large amount of bloat.
Perhaps we could pick 1 output, say comma delimted with quoted fields?
foo,bar ,baz
Joshua D. Drake
---
Tom Lane wrote
it to delimit on tabs and thus you have four columns as far as
Excel is concerned.
An alternative although I don't know what kind of headaches it would
cause is to have a text delimiter as well as a field delimter, e.g;
foo bar baz bing
Sincerely,
Joshua D. Drake
-Original
,
Joshua D. Drake
Cheers,
Steve
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
x86 and PPC.
Having said that, this may well expose a bug in the MAX-optimization
code that has consequences for more useful queries. I'll take a look
later today if no one beats me to it.
Sincerely,
Joshua D. Drake
regards, tom lane
running it in MySQL ;)
Well as the host, I guarantee you that it is NOT running mySQL :)
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
---(end of broadcast
is that constantly updating a single row
steadily degrades performance, would delete/insery also do the same?
Yes. Delete still creates a dead row. There are programatic ways around this
but keeping a delete table that can be truncated at intervals.
Joshua D. Drake
---(end
that revoking usage on a schema is not sufficient to
prevent a user from accessing things within that schema, a property that
makes me quite uncomfortable.
Then the public schema must drive you nuts :). If you were to create the
function as a non-super user you would probably be good.
Joshua D
over pgFoundry is that it will be packaged by the
major distributions. Every distribution includes a package of the contrib
modules.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
use patches for patch submission and keep all
discussion on hackers.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
it they can
pull the sources from anythin = 8.2 yes?
So I vote nuke!
Joshua D. Drake
The problem is,
adddepend is broken when run against 8.1. It breaks on serial, I think.
Gavin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Tuesday 11 July 2006 13:49, Andrew Dunstan wrote:
Joshua D. Drake wrote:
... and before you say it, No. I do not wear a tie.
Maybe you need to ... ;-)
/me bows before the gods who thoust commit.
cheers
andrew
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
that carries
much weight here ;)).
Having pl/Java helps PostgreSQL in the minds of all those tie wearing decision
making freaks... and before you say it, No. I do not wear a tie.
Sincerely,
Joshua D. Drake
regards, tom lane
---(end of broadcast
pointed at adddepends even today... certainly no one will do
anything with these projects if you nuke them, but I like giving people
options... your call though.
They will always be able to pull down the source from a previous release.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL
even the front of PgFoundry and or PostgreSQL.Org?) that
asks if anyone would like to take over maintainership of the handful?
Have a closing date for it, e.g; leave it open for a week and then if no one
steps up --- its over and we nuke them with prejudice.
Sincerely,
Joshua D. Drake
it could make a good reference implementation for other equally
advanced language mappings.
What is the actual concern with having PL/Java in core, versus say PL/Perl?
Sincerely,
Joshua D. Drake
Regards,
Thomas Hallgren
---(end of broadcast
and stable.
Sincerely,
Joshua D. Drake
Dave
On 11-Jul-06, at 12:50 PM, Josh Berkus wrote:
David,
It's good to integrate things with the core as needed. What plans do
we have to integrate PL/J?
None, if the PL/J team doesn't speak up. So far I have yet to see
a request for PL/J
and such... Soon.
Sincerely,
Joshua D. Drake
Regards,
Thomas Hallgren
---(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
under the GPL. See LIBGCJ_LICENSE in the source tree for
more details.
Sincerely,
Joshua D. Drake
Dave,
What JVM requirements does PL/J currently have? What license
implications are imposed by the components that it depends upon?
Regards,
Thomas Hallgren
--
=== The PostgreSQL
:(
Sincerely,
Joshua D. Drake
but what of people who use some other JVM?
It's not like gcj works for everyone yet.
What of them? If they decide to use another JVM, well, then let them. I
don't see where that becomes a licensing problem from PostgreSQL.
Regards,
Thomas Hallgren
) in a closed source
product without issue right?
If so... then wouldn't our argument be to strongly suggest that they use
the Sun JVM (or IBM if that is relevant?).
Sincerely,
Joshua D. Drake
Regards,
Thomas Hallgren
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
Thomas Hallgren wrote:
Joshua D. Drake wrote:
What happens when the FSF inevitably removes the license clause and
makes it pure GPL?
I'm sorry but I don't follow. You're saying that it's inevitable that
FSF will remove the 'libgcc' exception from libgcj? Why on earth would
they do that? My
the installer
from PgFoundry.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com
-user to use Sun's JVM with GPL'd Java code.
Now I'm completely confused... what GPL code ? Is PL/Java licensed under
the GPL ? Or what GPL code do you talk about ?
What was a mistake on my part. I was tired when I wrote the part about GPL.
Sincerely,
Joshua D. Drake
The PL/Java code is likely
to me, is including two projects that provide near
functionality.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
by exposure.
It is a valid reason if it is going to be in core.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
to be that?
Lukas, that is what www.mammothpostgresql.org is :)
Sincerely,
Joshua D. Drake
What I mean is I think it makes absolute sense to keep a very stable,
very well maintained core PostgreSQL distribution which is that anyone
should base their distributions on. However I do think
is in core.
What packagers? Every packager I see (Ubuntu, Fedora, *BSD, even
Solaris) contain just about every conceivable package there is for
PostgreSQL :)
O.k. not every, but all of the really important stuff.
Joshua D. Drake
cheers
andrew
---(end of broadcast
In essence the PostgreSQL SDK.
If I read what Thomas wrote (late) last night correctly.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions
heck... I still think we should introduce new features into back
branches as long as it doesn't require an initdb but most (including my
own developers) don't agree with me.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
...
Yes and my understanding is that PLjava can do the same.
Sincerely,
Joshua D. Drake
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org
familiar with commercial-class database systems.
Uhmmm that is what CMD and EDB are supposed to be doing. Educating their
customers, gaining more customers and educating them.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
:)
Joshua D. Drake
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.orgICQ . 7615664
---(end of broadcast
So why put the load on the Core distro?
Agreed ... but, maybe on our FTP/download pages, we should add a link
for 'Distributions', that would include mammothpostgresql.org and
Ubuntu? so that ppl knew about them? We do it for support related
stuff ...
That is a great idea :)
Joshua D
Marc G. Fournier wrote:
On Thu, 13 Jul 2006, Joshua D. Drake wrote:
Aside from obviously the big issue of who maintains all the pgfoundry
stuff, I also think that the PostgreSQL family would benefit from a
distribution that is more and the kitchen sink style. I do not know
exactly if Bizgres
don't expect
everything just to be right out of the box (o.k. maybe MSSQL does.)
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
is more
mature.
I also currently endorse Slony-I for 8.1 installations but that is only
because we don't have a 8.1 release yet (4 weeks W00t!).
I on the other hand, do not endorse Perl or anything to do with Perl :)
Sincerely,
Joshua D. Drake
Marc G. Fournier Hub.Org
Hey JD, I notice that we don't have a port for plphp either ... if one
of your guys wants to create one, I can get it committed ...
DarcyB is supposed to be handling that :)
Joshua D. Drake
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Were trying man :) I have people building for most major distributions
at this point. We should have FreeBSD soon, as well as MacOSX.
How is this different (or better) than what is already in FreeBSD ports?
There is no functional difference
I believe it was Lukas who mentioned elsewhere, this is not a vendor nuetral
project. I actually am already working on a adding a list of os/package
options to the download page based on other feedback, are people comfortable
allowing mammothpostgresql to go on that list? (I wouldn't be
Marc G. Fournier wrote:
On Thu, 13 Jul 2006, Joshua D. Drake wrote:
Most people who run FreeBSD have no need for Mammoth, until possibly
they want to upgrade via ports to a new version of PostgreSQL but they
don't want to upgrade FreeBSD.
'k, up to now, you had me ... but what does
I believe it was Lukas who mentioned elsewhere, this is not a vendor
nuetral
project. I actually am already working on a adding a list of os/package
options to the download page based on other feedback, are people
comfortable
allowing mammothpostgresql to go on that list? (I wouldn't be
Peter Eisentraut wrote:
Joshua D. Drake wrote:
For example there is NOT an PostgreSQL 8.1 for Ubuntu Breezy.
http://packages.ubuntu.com/breezy-backports/misc/
Thanks Peter :), I knew about backports but didn't know what was in
there. But what about when 8.2 comes out? Doubtful
Since I appreantly like monologs .. MySQL also has other features that
are not available via pgfoundery like being able to determine the
default charset on the database, table and column level, as well as
COLLATE support to determine the sort order at runtime.
SHOW ALL; ?
Anyways what I
a crypto-free version of
postgres for use someplace with benighted laws, they would be screwed.
Doesn't our inclusion of md5() pretty much blow that argument away?
(Just asking).
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
or any of
the other i/o operations.
Well from a DBA perspective, just knowing that something productive is
happening is useful.
When using vacuum I almost always use vacuum verbose, just so I have an
idea of what is going on.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt
they
are.
Joshua D. Drake
Kris Jurka
---(end of broadcast)---
TIP 1: 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
confident that it does not meat the
PostgreSQL style guidelines.
Is there enough interest in plRuby to get it where it needs to be for
possible inclusion into core?
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7
(of
which I am apart) is using the SPI non-profit status to allow for tax
deductible donations to the PostgreSQL project.
Sincerely,
Joshua D. Drake
-M
On Jul 16, 2006, at 2:10 PM, Josh Berkus wrote:
Folks,
Hopefully by now a bunch of you have joined as Software in the Public
Interest
Peter Eisentraut wrote:
Am Montag, 17. Juli 2006 03:18 schrieb Joshua D. Drake:
We were going to submit plPHP to core for inclusion but it is not ready
yet.
Is there enough interest in plRuby to get it where it needs to be for
possible inclusion into core?
Considering that PL/Java
perl and python guys really don't like the
other ;)).
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
Peter Eisentraut wrote:
Joshua D. Drake wrote:
PLRuby is written in C.
Specifically on the matter of PL/Ruby -- and if you're trying to be such
an advocate about it, you should at least spell it right -- I have
never seen the author particularly active within this community, so I
have my
talking
about? Actually as I look at this, the only major distribution (that is
not commercial) that doesn't support a lot of PostgreSQL packages is Fedora.
Ubuntu
Debian
Gentoo
FreeBSD
All have a ton of packages (including plruby).
Sincerely,
Joshua D. Drake
cheers
andrew
:).
That being said, we may want to check and see if he participates in
PostgreSQLFR (he is french).
Also note, that if it were included, CMD would dedicate resources to
help keeping it stable etc...
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc
is going to be able to maintain his work?
Yes, this was one of my concerns.
Sincerely,
Joshua D. Drake
regards, tom lane
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
and it would actually fetch the latest plruby sources from the net and
build. Ala Ports.
This would take some organization of course, but it would be an
relatively easy way to increase our core base without bloating core.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales
.
Joshua D. Drake
Full merge into core would fix this also, but indeed there is not many
techical reasons for it. (And editing pg_proc.h is PITA - I'd consider
it technical reason against it ;)
--
marko
---(end of broadcast)---
TIP 6: explain
that could be used to architect such a thing.
Well it works fine depending on how you set it up :) Please feel free to
submit a patch to the docs.
Sincerely,
Joshua D. Drake
Thanks!
- Chris
[1] http://www.postgresql.org/docs/8.1/interactive/backup-online.html
501 - 600 of 2933 matches
Mail list logo
