On Tue, Dec 15, 2009 at 1:23 AM, Pavel Stehule wrote:
> Hello
>
> NEW and OLD is comparable in 8.4. In 8.3 and older you have to use
> little bit different syntax
>
> http://www.postgres.cz/index.php/PostgreSQL_SQL_Tricks#Fast_compare_variables_NEW_and_OLD_in_trigger.27s_body
>
Thanks, Pavel! Thi
Hello.
It seems that this works (I made tests on permanent table, postgresql
8.4.0):
CREATE OR REPLACE FUNCTION track_updates()
RETURNS TRIGGER AS $$
DECLARE
BEGIN
IF TG_OP = 'UPDATE' THEN
IF NEW IS NOT DISTINCT FROM OLD THEN
RAISE NOTICE 'OLD and NEW are the same!';
Hello
NEW and OLD is comparable in 8.4. In 8.3 and older you have to use
little bit different syntax
http://www.postgres.cz/index.php/PostgreSQL_SQL_Tricks#Fast_compare_variables_NEW_and_OLD_in_trigger.27s_body
Regards
Pavel Stehule
2009/12/15 Josh Kupershmidt :
> Hi all,
>
> Short version of m
Hi all,
Short version of my question:
What's the best way to compare arbitrary records (OLD and NEW, in my
case) using PL/pgSQL in Postgres 8.3, without knowing anything about
the structure of the records? If the answer is to cast OLD and NEW to
text, and then compare, as suggested in [1], what fa
On 2009-05-23, Havasvölgyi Ottó wrote:
> --0016364c779590a8c0046a9321b6
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
>
> Hi,
>
> I don't know why this query returns false:
>
> SELECT '20040506 070809.01'::timestamp(6) - '20010203
> 040506.007000'::timestamp(
Thanks Tom for your comments.
I meant the build in this directory:
http://www.postgresql.org/ftp/binary/v8.3.6/win32/, and the builds for win32
of other versions in the binary directory.
What is the trend of these builds regarding floating point timestamps? For
example what about 8.4?
Thanks,
Ott
=?ISO-8859-1?Q?Havasv=F6lgyi_Ott=F3?= writes:
> Thanks, It's off in both 8.2 and 8.3.
As was already stated, that depends on which build you're using.
(And no, "the Win32 distribution on the PgSql site" is not a unique
description, not even for a single PG version.)
> What will be the default in
Thanks, It's off in both 8.2 and 8.3.
What will be the default in 8.4?
Best regards,
Otto
2009/5/23 Alvaro Herrera
> Havasvölgyi Ottó escribió:
> > I mean the Win32 distribution on the PgSql site. I always used that.
>
> If you want to find out whether a particular build used floating point or
Havasvölgyi Ottó escribió:
> I mean the Win32 distribution on the PgSql site. I always used that.
If you want to find out whether a particular build used floating point or
integer datetimes, issue "SHOW integer_datetimes".
If it says "off", then it's floating point.
--
Alvaro Herrera
I mean the Win32 distribution on the PgSql site. I always used that.
It would be very good if these data types were exact by default, even if
that's a bit slower.
Otto
2009/5/23 Christophe
>
> On May 23, 2009, at 10:44 AM, Havasvölgyi Ottó wrote:
>
> Thanks.
>> I tested the standard Win32 distr
On May 23, 2009, at 10:44 AM, Havasvölgyi Ottó wrote:
Thanks.
I tested the standard Win32 distribution of 8.3.6.
The same happens on 8.2. But on 8.0 it works.
When I don't use milliseconds, then it works.
Will 8.4 work fine on Win32 again?
If the issue is using floating point timestamps, th
Hi,
On 8.2 this comparision is also not true:
select '240:0:0.3'::interval = '10 0:0:0.3'::interval;
But without milliseconds it's true.
Is this also because interval is represented internally as a floating point
value?
On 8.3 this test does not fail.
Best regards,
Otto
2009/5/23 Havasvölgyi
Thanks.
I tested the standard Win32 distribution of 8.3.6.
The same happens on 8.2. But on 8.0 it works.
When I don't use milliseconds, then it works.
Will 8.4 work fine on Win32 again?
Thanks,
Otto
2009/5/23 Ludwig Kniprath
> Scott Marlowe schrieb:
>
>> On Sat, May 23, 2009 at 7:18 AM, Chr
Scott Marlowe schrieb:
On Sat, May 23, 2009 at 7:18 AM, Christophe wrote:
On May 23, 2009, at 9:13 AM, Daniel Verite wrote:
I don't know why this query returns false:
SELECT '20040506 070809.01'::timestamp(6) - '20010203
040506.007000'::timestamp(6) = '1188 day 3 hour 3 minute 3 se
On Sat, May 23, 2009 at 7:18 AM, Christophe wrote:
>
> On May 23, 2009, at 9:13 AM, Daniel Verite wrote:
>>>
>>> I don't know why this query returns false:
>>> SELECT '20040506 070809.01'::timestamp(6) - '20010203
>>> 040506.007000'::timestamp(6) = '1188 day 3 hour 3 minute 3 second 3
>>> mill
On May 23, 2009, at 9:13 AM, Daniel Verite wrote:
I don't know why this query returns false:
SELECT '20040506 070809.01'::timestamp(6) - '20010203
040506.007000'::timestamp(6) = '1188 day 3 hour 3 minute 3 second 3
millisecond'::interval;
If I just subtract the two timestamps, its result is
Havasvölgyi Ottó wrote:
I don't know why this query returns false:
SELECT '20040506 070809.01'::timestamp(6) - '20010203
040506.007000'::timestamp(6) = '1188 day 3 hour 3 minute 3 second 3
millisecond'::interval;
If I just subtract the two timestamps, its result is the interval I
sp
Hi,
I don't know why this query returns false:
SELECT '20040506 070809.01'::timestamp(6) - '20010203
040506.007000'::timestamp(6) = '1188 day 3 hour 3 minute 3 second 3
millisecond'::interval;
If I just subtract the two timestamps, its result is the interval I
specified.
What may cause this?
On Feb 13, 2009, at 11:59 AM, Ray Stell wrote:
This is probably the wrong place to mention this, but idunno:
I did a search in the docs of pg_standby and was presented this link:
Based on your search term, we recommend the following links:
* http://developer.postgresql.org/cvsweb.cgi/pgsq
This is probably the wrong place to mention this, but idunno:
I did a search in the docs of pg_standby and was presented this link:
Based on your search term, we recommend the following links:
* http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/
but that link gives a 404
Glyn Astill wrote:
Pretty sure I've used most 8.3.x versions here on both sp2 and 3.
How have you chacked you have all the dependencies? (I like depends.exe)
http://www.dependencywalker.com/
hmm, the problem seems to be that MSVCR71.DLL has a problem with some
versions of Kernel32.DLL,
--- On Sat, 15/11/08, Tony Caduto <[EMAIL PROTECTED]> wrote:
> Hi,
> We have been running into issues where the 8.3.x versions
> of libpq.dll will not load in certain
> versions of windows and WINE(does not load at all on wine).
>
> It seems to be hit and miss on Windows XP, mostly seems to
> affe
Hi,
We have been running into issues where the 8.3.x versions of libpq.dll
will not load in certain
versions of windows and WINE(does not load at all on wine).
It seems to be hit and miss on Windows XP, mostly seems to affect SP3
and some SP2 installs of XP.
I have only been able to get arou
Tom Lane wrote:
Steve Clark <[EMAIL PROTECTED]> writes:
I have postgres logging into data/pg_log/ which works great. My question is
there
and option that tells postgres to only keep the last "n" log files?
The usual solution is to choose a filename pattern that will repeat
after an appropri
Steve Clark <[EMAIL PROTECTED]> writes:
> I have postgres logging into data/pg_log/ which works great. My question is
> there
> and option that tells postgres to only keep the last "n" log files?
The usual solution is to choose a filename pattern that will repeat
after an appropriate interval, eg
On 27/10/2008 13:19, Steve Clark wrote:
> I have postgres logging into data/pg_log/ which works great. My
> question is there and option that tells postgres to only keep the
> last "n" log files? Or does someone have a script that be run daily
> to remove the older log files so that I only end up
Hi,
I have postgres logging into data/pg_log/ which works great. My question is
there
and option that tells postgres to only keep the last "n" log files? Or does
someone
have a script that be run daily to remove the older log files so that I only
end up
with "n" log files?
Thanks,
Steve
log_
On Mon, 8 Sep 2008, Ivan Zolotukhin wrote:
Yep, update_process_title = off if it is important.
Have you considered turning it on so you can see what processes are most
involved in the spike? Normally in your situation I'd try to capture what
the output from top was during the problem period
On 2008-09-09 09:30, Tomasz Ostrowski wrote:
> On 2008-09-08 11:46, Ivan Zolotukhin wrote:
>
>> vmstat 5
>> procs memory page disk faults cpu
>> r b w avmfre flt re pi po fr sr am0 insycs us sy
>> id
>> 28 77 0 2328792 793424 3481
On 2008-09-08 11:46, Ivan Zolotukhin wrote:
> vmstat 5
> procs memory page disk faults cpu
> r b w avmfre flt re pi po fr sr am0 insycs us sy
> id
> 28 77 0 2328792 793424 34813 0 0 0 4351 0 41 1913 21230 20337 14 86 > 0
Hello,
We experience sudden performance degradations on a PostgreSQL server
used as a backend for pretty big web application.
It's 16 GB RAM dedicated PostgreSQL 8.3.3 server with 2 x Quad Core
Xeon 2.33 GHz running 6.3-PRERELEASE FreeBSD. postgresql.conf tweaked
to match current configuration si
On Fri, Jul 04, 2008 at 12:37:48PM -0400, Tom Lane wrote:
> Yeah, estimate_num_groups doesn't have any special knowledge about IS
> NULL -- it just sees this as "an expression involving col". The
> general assumption about that is that the expression doesn't reduce
> the number of groups (think "c
Sam Mason <[EMAIL PROTECTED]> writes:
> I've just noticed that the planner in 8.3.3 doesn't seem to realize the
> difference in the result of the following:
> GROUP BY col;
> GROUP BY col IS NULL;
Yeah, estimate_num_groups doesn't have any special knowledge about IS
NULL -- it just sees this a
Hi,
I've just noticed that the planner in 8.3.3 doesn't seem to realize the
difference in the result of the following:
SELECT col, COUNT(*)
FROM tbl
GROUP BY col;
and
SELECT col IS NULL, COUNT(*)
FROM tbl
GROUP BY col IS NULL;
For a table with several million distinct values in "co
Whenever I try to install version 8.3 on w2k, using an existing windows account
, the installer returns the error "Invalid username specified: A required
privilege is not held by the client".
I have since installed version 8.2 successfully, using the same account that
failed with the 8.3 inst
>From the 8.3.0 INSTALL file:
| Upgrading
|
| 1. If making a backup, make sure that your database is being updated.
Ouch. Revert to the language in 8.2, perhaps:
1. Make sure that your database is not updated during or after the backup.
---(end of broadcast)
Giorgio Valoti wrote:
> When I try to install the uuid functions I get this error:
>
> psql:share/contrib/uuid-ossp.sql:9: ERROR: could not load library "/
> opt/local/pgsql/lib/uuid-ossp.so": libuuid.so.16: cannot open shared
> object file: No such file or directory
Make sure the libuuid.so.
Hi all,
I’m trying to enable the uuid module with a SUSE Linux. I’ve
installed the uuid library with the default settings and configured/
compiled/installed pgsql with these flags:
./configure --prefix=/opt/local/pgsql --with-perl --with-tcl --with-
tclconfig=/opt/local/lib --with-openssl --
> > My database uses tsearch2. I was about to follow the conversions
> > instructions found at Appendix F31 (on the new tsearch module).
> > http://www.postgresql.org/docs/8.3/static/tsearch2.html
> The docs will need to be updated because tsearch2 is now in the core and
> should already be availa
"Pierre Thibaudeau" <[EMAIL PROTECTED]> writes:
> I am assuming that the "replacement tsearch2 module" is some file
> "tsearch2.sql" found in the folder share/contrib. However, no such
> file, or anything that looks remotely like it, in that folder or in
> any folder around.
Hmm, it's definitely
Pierre Thibaudeau wrote:
I just downloaded the 8.3 Windows installation (binary with installer).
My database uses tsearch2. I was about to follow the conversions
instructions found at Appendix F31 (on the new tsearch module).
http://www.postgresql.org/docs/8.3/static/tsearch2.html
However, I h
I just downloaded the 8.3 Windows installation (binary with installer).
My database uses tsearch2. I was about to follow the conversions
instructions found at Appendix F31 (on the new tsearch module).
http://www.postgresql.org/docs/8.3/static/tsearch2.html
However, I hit a problem when I get to
This is really a web site error report, but I don't see any links on the
site to report such errors. On the 8.3 Features List page here:
http://www.postgresql.org/about/press/features83.html, it mentions
"Version 2.0 of Slony-I, our most popular replication system, now uses
the new replication
peter pilsl wrote:
#make
/usr/bin/ld:exports.list:1: parse error in VERSION script
collect2: ld returned 1 exit status
make[3]: *** [libpq.so.5.1] Error 1
The machine is a very old machine, that uses GNU ld 2.11.90.0.8 but it
was able to compile and run postgres8.0.13 without any troubles.
Am Dienstag, 5. Februar 2008 schrieb peter pilsl:
> The machine is a very old machine, that uses GNU ld 2.11.90.0.8 but it
> was able to compile and run postgres8.0.13 without any troubles.
Yes, it is a known problem that "old" Linux systems can't build newer
PostgreSQL releases. You can edit th
#make
make[3]: Entering directory
`/opt_noraid/src/postgresql-8.3.0/src/interfaces/libpq'
echo '{ global:' >exports.list
gawk '/^[^#]/ {printf "%s;\n",$1}' exports.txt >>exports.list
echo ' local: *; };' >>exports.list
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-fno-strict-al
Clodoaldo escribió:
> > > fahstats=> analyze;
> > > WARNING: skipping "pg_authid" --- only table or database owner can
> > > analyze it
> The problem with that warning message is that it implies that the db
> owner can analyze them which can not be done according to your
> comment. The message,
The cvs/svn worked I managed to dump out of beta 1 and now have my database
restored in RC1. Many thanks to all.
--
Mark Walker
Joshua D. Drake wrote:
Mark Walker wrote:
What can I do, a dump is impossible because I cannot re-install the
version that the database was last used with (it should have been
first initialised on 8.2, as I went to the beta to experiment with
enum having recently returned from MySQL).
Any h
Mark Walker wrote:
What can I do, a dump is impossible because I cannot re-install the
version that the database was last used with (it should have been first
initialised on 8.2, as I went to the beta to experiment with enum having
recently returned from MySQL).
Any help appreciated, includi
Mark Walker escribió:
> Ignoring the warnings not to use a beta product on a production database I
> had been running 8.3beta1. When I saw that it had hit 8.3RC1 I decided to
> upgrade and folowing the usual data compatibility within major versions I
> did not do a pg_dump, in fact my last dump was
On Thu, Jan 10, 2008 at 11:36:04AM +, Mark Walker wrote:
> Ignoring the warnings not to use a beta product on a production database I
> had been running 8.3beta1. When I saw that it had hit 8.3RC1 I decided to
> upgrade and folowing the usual data compatibility within major versions I
> did not
Ignoring the warnings not to use a beta product on a production database I
had been running 8.3beta1. When I saw that it had hit 8.3RC1 I decided to
upgrade and folowing the usual data compatibility within major versions I
did not do a pg_dump, in fact my last dump was when I loaded the beta on
10t
2008/1/6, Magnus Hagander <[EMAIL PROTECTED]>:
> Clodoaldo wrote:
> > I'm the owner of a database and when i issue an analyze command on it,
> > the pg tables are skipped with the message that only the owner can
> > analyze them:
> >
> > $ psql fahstats -U cpn
> > Welcome to psql 8.3beta4, the Post
Clodoaldo wrote:
I'm the owner of a database and when i issue an analyze command on it,
the pg tables are skipped with the message that only the owner can
analyze them:
$ psql fahstats -U cpn
Welcome to psql 8.3beta4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
I'm the owner of a database and when i issue an analyze command on it,
the pg tables are skipped with the message that only the owner can
analyze them:
$ psql fahstats -U cpn
Welcome to psql 8.3beta4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help
Robert Treat wrote:
> > However, neither one of them show what redirect_stderr was renamed to. It
> > says something like "... was renamed to foo. redirect_stderr was renamed
> > to bar was renamed to ..."
>
> Yeah, that should get cleaned up.
Looks OK now:
http://www.postgresql.org
Alvaro ,folks
--- Alvaro Herrera <[EMAIL PROTECTED]> escribió:
> marcelo Cortez escribió:
> > folks
> >
> >
> > i've installed 8.3beta but at start up receive
> >
> > FATAL: invalid value for parameter
> > "timezone_abbreviations": "Default"
>
> Do you have a file named "Default" on the
>
marcelo Cortez escribió:
> folks
>
>
> i've installed 8.3beta but at start up receive
>
> FATAL: invalid value for parameter
> "timezone_abbreviations": "Default"
Do you have a file named "Default" on the share/timezonesets dir?
I'm wondering if your installation is being mistakenly trying t
marcelo Cortez escribió:
> folks
>
>
> i've installed 8.3beta but at start up receive
>
> FATAL: invalid value for parameter
> "timezone_abbreviations": "Default"
Wow, strange. Mismatching case, perhaps?
--
Alvaro Herrerahttp://www.advogato.org/person/alvherre
"Cua
folks
i've installed 8.3beta but at start up receive
FATAL: invalid value for parameter
"timezone_abbreviations": "Default"
any clue?
best regards.
MDC
info:
Linux richelet-internet 2.6.21.6 #9 SMP Sun Dec 2
17:52:20 ART 2007 i686 Pentium III (Coppermine)
GenuineIntel GNU/Linux
gp_confi
On Monday 03 December 2007 18:24, Matthew Dennis wrote:
> The release notes seem to be in two places, with slightly different
> information.
>
> The page Google sends back for most 8.3 queries
> http://www.postgresql.org/docs/8.3/static/release-8-3.html
>
This is the docs distributed with the late
The release notes seem to be in two places, with slightly different
information.
The page Google sends back for most 8.3 queries
http://www.postgresql.org/docs/8.3/static/release-8-3.html
and the one you get from the PostgreSQL beta program link
http://developer.postgresql.org/pgdocs/postgres/rel
On Mon, Dec 03, 2007 at 04:41:35PM +0100, Enrico Sirola wrote:
> Dear all,
> I'd like to use the upcoming release 8.3 for my next project. When is it
> expected to be finalized? My deadline is 2nd quarter 2008, do you think
> there is a chance for me to use it?
Most likely. While there is no pro
Dear all,
I'd like to use the upcoming release 8.3 for my next project. When is it
expected to be finalized? My deadline is 2nd quarter 2008, do you think
there is a chance for me to use it?
A second question (more technical). Is it possible to put an index on an
xpath expression of an XML ty
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tony Caduto <[EMAIL PROTECTED]> wrote:
>> I am actually getting a lot of these operator does not exist errors
>> in 8.3 another one I get is operator does not exist for char=integer
> This appears to be a classic example of:
> Casts to text that form
Tom Lane wrote:
> Tony Caduto <[EMAIL PROTECTED]> writes:
> > case when cast(a.attnum as text) IN( select array_to_string(conkey,',')
> > from pg_constraint where
>
> Surely that's the worst bit of SQL code I've seen in awhile.
Wow, you really are lucky.
--
Alvaro Herrera http
Tony Caduto <[EMAIL PROTECTED]> writes:
> it was this line:
> case when a.attnum as text IN( select array_to_string(conkey,',') from
> pg_constraint where
> which is fixed by adding a cast:
> case when cast(a.attnum as text) IN( select array_to_string(conkey,',')
> from pg_constraint where
Su
Tom Lane wrote:
That's no doubt got something to do with it, but I think Tony is mighty
confused about exactly what is failing. pg_constraint.conkey is not
text, for instance; it's smallint[] and so the quoted bit should still
work just fine. I'd suggest trying the query in some client that giv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Nov 2007 12:03:27 -0600
Tony Caduto <[EMAIL PROTECTED]> wrote:
> I am actually getting a lot of these operator does not exist errors
> in 8.3 another one I get is operator does not exist for char=integer
>
This appears to be a classic ex
Hi,
Just running some queries that have worked from 7.4 through 8.2 and they
don't seem to work on 8.3.
select case when a.attnum = any(conkey) then true else false end from
pg_constraint where contype = 'p' and conrelid = c.oid
This one is puking on a.attnum = any(conkey)
returns the fo
Tom Lane pisze:
I'm wondering if you have an example that doesn't work well with the
gist page-splitting heuristic changes that Teodor put in awhile back.
Those are all in 8.2.5 already, though you might have to REINDEX to
really notice a change if the index was first built with an older
8.2.x re
Marek Lewczuk <[EMAIL PROTECTED]> writes:
>> I'm testing 8.3beta and I think that there is a problem with gist/gin
>> indexes. The performance of 8.3 is very bad comparing to 8.2.
Comparing to 8.2.which-exactly?
I'm wondering if you have an example that doesn't work well with the
gist page-split
2007/10/16, Marek Lewczuk <[EMAIL PROTECTED]>:
> Hello,
> I'm testing 8.3beta and I think that there is a problem with gist/gin
> indexes. The performance of 8.3 is very bad comparing to 8.2. I have a
> table with an int[] column indexed using gin (or gist with intarray
> module). Table contains ab
Marek Lewczuk pisze:
Hello,
I'm testing 8.3beta and I think that there is a problem with gist/gin
indexes. The performance of 8.3 is very bad comparing to 8.2. I have a
table with an int[] column indexed using gin (or gist with intarray
module). Table contains about 1.5m rows, int[] length is
Hello,
I'm testing 8.3beta and I think that there is a problem with gist/gin
indexes. The performance of 8.3 is very bad comparing to 8.2. I have a
table with an int[] column indexed using gin (or gist with intarray
module). Table contains about 1.5m rows, int[] length is from 2 to 6
elements.
I came upon this article
http://www.internetnews.com/dev-news/article.php/3647376
The last 2 paragraphs caught my eyes:
"Among the improvements expected in PostgreSQL 8.3 are
further performance gains.
"'The most exciting of these is an optimization that
would improve performance on OLTP system
On Wed, May 30, 2007 at 08:04:19AM -0700, Joshua D. Drake wrote:
> I would like to submit that, that is likely not true at all.
Possibly. I was just pointing out that the last estimate any
developer gave was "beta in Sept."
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The whole tendency of moder
Andrew Sullivan wrote:
On Wed, May 30, 2007 at 12:05:18AM +0100, Raymond O'Donnell wrote:
I realise that (i) this is something of a FAQ, and (ii) the definitive
answer is "When it's ready", but when (roughly) is 8.3 planned to be
released?
According to a recent post on -hackers by Bruce, at t
On Wed, May 30, 2007 at 12:05:18AM +0100, Raymond O'Donnell wrote:
> I realise that (i) this is something of a FAQ, and (ii) the definitive
> answer is "When it's ready", but when (roughly) is 8.3 planned to be
> released?
According to a recent post on -hackers by Bruce, at the current rate
of p
ginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Raymond
O'Donnell
Sent: Tuesday, May 29, 2007 5:25 PM
To: Guy Rouillier
Cc: 'PostgreSQL'
Subject: Re: [GENERAL] 8.3
On 30/05/2007 00:11, Guy Rouillier wrote:
> I'm not one of the developer
On 30/05/2007 00:11, Guy Rouillier wrote:
I'm not one of the developers, but I found the following information
here http://www.postgresql.org/developer/roadmap:
That's great - thanks.
Ray.
---
Raymond O'Donnell, Director of Music, G
Raymond O'Donnell wrote:
I realise that (i) this is something of a FAQ, and (ii) the definitive
answer is "When it's ready", but when (roughly) is 8.3 planned to be
released?
I'm not one of the developers, but I found the following information
here http://www.postgresql.org/developer/roadmap:
I realise that (i) this is something of a FAQ, and (ii) the definitive
answer is "When it's ready", but when (roughly) is 8.3 planned to be
released?
I'm planning a server upgrade in the next 4-5 months, and a ballpark
guess would be helpful.
Thanks,
Ray.
--
84 matches
Mail list logo
