Marc G. Fournier wrote:
> Peter, I tried the make man.tar.gz, and it failed to find sgmlspl ...
> haven't been able to find a port that has it, so will install from
> scratch ... is there a specific version I should be installing?
I usually used 0.6.1 with a patch [1], but I just read that he's ba
Will be on the ftp site within the hour ...
Peter, I tried the make man.tar.gz, and it failed to find sgmlspl ...
haven't been able to find a port that has it, so will install from scratch
... is there a specific version I should be installing?
Marc G. Fournier Hub.Org Networking
Andrew Rawnsley <[EMAIL PROTECTED]> writes:
> If I were loony enough to want to make an attempt at a version updater
> (i.e. migrate a 7.4 database to 8.0 without an initdb), any
> suggestions on where to poke first?
pg_upgrade is the way to go IMHO. I would not try to "dust off" the old
shell-sc
If I were loony enough to want to make an attempt at a version updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system catalog changes exist anywhere? Any really gross
problems immediately
present themselves? Is dustin
On Monday 30 August 2004 09:50, [EMAIL PROTECTED] wrote:
> > On Sun, Aug 29, 2004 at 09:24:59AM -0400, [EMAIL PROTECTED] wrote:
> > What's the advantage of instead stuffing these in-memory variables
> > into PostgreSQL? That it still works correctly and simply even if you
> > have a farm of 10 sep
> Mohawksoft,
>
>> One of the most common SQL database applications is as the backend of
>> some
>> higher level system, like a web site. In these systems, ususlly done in
>> Java, PHP, or heaven help us, .NET, you have multiple front end machine
>> communicating with a SQL database backend.
>
> Le
Try using a bytea field instead of a text one.
Chris
Mamta Singh wrote:
Hi,
I have created a table
create table temp1(a varchar(200));
and then I tried running the following code.
String msg1 = "\umamta";
PreparedStatement preparedStmt =
pgConnection.prepareStatement("insert into mamtanow
value
On Mon, 30 Aug 2004 19:09:34 -0500
"Ramy M. Hassan" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there any updated implementation guide for postgresql 7.x ? I've
> been using the postgres95 guide at
> http://pluto.iis.nsk.su/postgres95/impl-guide/
>
> but it is incomplete and also it does not ref
Thomas Swan wrote:
> The 7.4 release increased the maximum length for column and table
> identifiers to 64 characters. Are there any plans to increase the
> maximum length out to the SQL spec of 128 characters? I remembered
> some performance penalties for the longer name lengths for hash jo
Hi all,
Is there any updated implementation guide for postgresql 7.x ? I've been
using the postgres95 guide at http://pluto.iis.nsk.su/postgres95/impl-guide/
but it is incomplete and also it does not reflect the current state of the
code. I can see many structures were modified since postgres95
The 7.4 release increased the maximum length for column and table
identifiers to 64 characters. Are there any plans to increase the
maximum length out to the SQL spec of 128 characters? I remembered
some performance penalties for the longer name lengths for hash joins
but I don't know if an
Mohawksoft,
> One of the most common SQL database applications is as the backend of some
> higher level system, like a web site. In these systems, ususlly done in
> Java, PHP, or heaven help us, .NET, you have multiple front end machine
> communicating with a SQL database backend.
Leaving aside t
> > I've compiled 8.0 beta 1 on a R5900 V3.1 (a playstation 2) running
> > Linux (PS2 Linux 1) for portability testing.
> > ...
> > I'm wondering: would it be hard to fix the assembly spinlock code
> > for the R5900?
>
> According to the previous port report from Red Hat, the PS2 chip simply
> d
Dear Bruce,
Just my 0.02 euro cents:
On Sat, 28 Aug 2004, Bruce Momjian wrote:
> This is going to have to wait for 8.1. If it was so important, someone
> would have asked for it long before we went beta.
I'm not sure it works that way. Not that simply anyway.
Those having a say BEFORE beta ar
Robert Treat <[EMAIL PROTECTED]> writes:
> OTOH I know that I sometimes use /df to look up built in functions that I
> don't exactly remember, so keeping a way to access the system functions is
> handy.
>
> Given a third hand I'd look for some way to do both... perhaps \df can show
> all func
15 matches
Mail list logo
