>> I am loathe to even bring this up, but with two messages today about
>> it, I am going to be short and sweet:
>>
>> We don't have a reasonable upgrade path.
This is one of many, many things that need work. It happens to be a
thing that requires a *lot* of work for, well, not so much payback
Nils Zonneveld <[EMAIL PROTECTED]> writes:
> support. If not, there are workarounds. At the moment PostgreSQL doesn't
> have schema support. But there's light at the end of the tunnel: I've
> heard Tom Lane mention schema support several times (can you give us an
> estimate when schema support wil
On Wed, 16 May 2001, Lamar Owen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I am loathe to even bring this up, but with two messages today about it, I am
> going to be short and sweet:
>
> We don't have a reasonable upgrade path. ASCII dump->install
> new->initdb->restore is not
Tom Lane wrote:
> is included in every Postgres source file (via c.h).
>
Yep. That's what I expected.
SGI technical support seems to think that the problem is with the POSIX flag.
" Have you defined any POSIX variables, such as -D_POSIX_SOURCE
or included pthread.h? When you enable POSI
Hi,
l see that a lot of people have the same problem and have posted questions
but I couldn't find an answer on the web.
I have Postgresql 6.5.3 running on Debian Linux.
And I use the iODBC driver manager 2.50.3 to make the ODBC calls.
Am not able to insert data into Postgres tables across ODBC
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> My best guess is that the trigger fmgr lookup in trigger.c:846
> if (trigger->tgfunc.fn_oid == InvalidOid)
> fmgr_info(trigger->tgfoid, &trigger->tgfunc);
> might be reading out of an incompletely initialized trigger->tgfunc
> stru
"G. Anthony Reina" <[EMAIL PROTECTED]> writes:
>> I noticed in your code string.h is not included. The man page for strdup
>> specifies the inclusion of this header. Please advise.
> Any comments?
is included in every Postgres source file (via c.h).
regards, tom lane
I've been talking with SGI tech support about my problem with installing
Postgres 7.1.1 on the SGI (IRIX 6.5.12 using the MIPSPro 7.3 compiler).
Fortunately, one of my SGI's (an octane) built PG without any problem so
this is just academic now (but probably useful for others wanting to
install PG
I was looking for some way via standard SQL (I use perl DBI) to list
these variables. I don't believe the SHOW command is available via DBI
Jim
>
> I think the way to do this is for SHOW ALL to show all setttings.
>
> [ Charset ISO-8859-1 unsupported, converting... ]
> >
> > Hi all (I hope t
Hi all (I hope this is the correct list),
Under Oracle there is v$parameter which list ALL config varables. Under
psql there is the SHOW command, but this only lists 1 variable. I have
written a shell script (attached) that shows ALL know variables. My
questions is can this script get include
Hi,
I want to learn, how the pl/plsql-parser/compiler works. Therefore I planned
to implement a simple ELSIF, like oracle does.
I added the following K_ELSIF branch to gram.y, in the hope that, when ELSIF
is parsed, simply another if-structure in inserted.
11 matches
Mail list logo