jprem wrote:
> hello ,
>postgreqsl 6.5.3 does not support nested transactions.
> so i don't think it will be suitable for e-com application.isn't it ?
> does postgreqsl 7.0 support nested transacions ? is postgresql 7.0 a
> stable version ?
Hi,
I have around 4000 online shop runnin
On Tue, 25 Jul 2000, anuj wrote:
> My table name is tblpg.
> I want to see the table structure.
> Like oracle have Describe .
> What PG have ? or any command.
> Thank in advance.
> Anuj
>
> pg=> \d
> Database= pg
> +--+--+--+
> | Own
Steve Heaven wrote:
>
> At 20:18 24/07/00 -0400, you wrote:
> >Sigh, forgot to mention the solution. There's an undocumented function:
> >
> > * bool oidrand (oid o, int4 X)-
> > * takes in an oid and a int4 X, and will return 'true'
> > * about 1/X of the time.
> >
> >typically used l
Title: RE: [GENERAL] Describe structure.
While we're on the topic, can someone tell me where '\d *' went, and what to use instead?
That particular command seems to have disappeared in PG7.
Thanks for any light-shedding...
-cw-
> -Original Message-
> From: Poul L. Christiansen [ma
Thanks for pointing me in the right direction. I started to look at the
db.out file and I noticed the pg_shadow variables. When I looked at the
newly built postgres 7.0.2 the usesysid for postgres was the same as the
usesysid for sys_request, one of the new accounts I was moving over. I
fixed a
"Fetter, David M" <[EMAIL PROTECTED]> writes:
> Thanks for pointing me in the right direction. I started to look at the
> db.out file and I noticed the pg_shadow variables. When I looked at the
> newly built postgres 7.0.2 the usesysid for postgres was the same as the
> usesysid for sys_request,
...the list for inadvertently solving my problem about subscripting. I asked
for a suggestion about rephrasing a query with "...peopcode[1,2] = my_var".
The obvious solution was "...substr(peopcode,1,2)"
Thanks for the unrelated question about updates.
Scott
Tom Lane wrote:
>
> Chris Bitmead <[EMAIL PROTECTED]> writes:
> > Paul Caskey wrote:
> >> 1. This implies a hard limit of 4 billion records on a server, right?
>
> > Basically, yes.
>
> It's only a hard limit if your application assumes OIDs are unique.
> If you don't assume that, then I think
hi,
we wish to have a database that is history so we
want to make the disks read only after loading.
would this cause any problems with POSTGRES? it's on
a linux 6.2 box with POSTGRES 7.0.2. what we're
looking for here is that if the system crashes we
can do a fast boot and not have the
Does anyone know if it's possible to suppress the comment '
#line nn ...' which appear in the C file, after pre-processing with
ecpg.
Thanks
Michaël Fiey wrote:
> Does anyone know if it's possible to suppress the comment ' #line nn ...' which
>appear in the C file, after pre-processing with ecpg.
> Thanks
>
That's not a comment.
It's a mechanism used by cpp (and other preprocessors as
well) to tell cc1 (the real C c
Hi,
Is there a way to write a "generic" trigger function in postgres
that can loop thru a table's cloumns (using TG_RELNAME)
and perform certain activities based on, say, certain column-types?
In other words, is it possible to assign OLD.
and NEW. to a variable inside triggers?
Thanks,
Morey Par
Wilkinson Charlie E writes:
> While we're on the topic, can someone tell me where '\d *' went, and what to
> use instead?
> That particular command seems to have disappeared in PG7.
Hmm, that must have been me. What did it do? Describe all tables at once?
--
Peter Eisentraut
Chris Bitmead writes:
> Is this behaviour some kind of standard? Can it be changed?
In the past the answer to the question "Does a statement-level error
warrant a transaction abort?" has usually hinged on the interpretation of
the following clauses of the SQL92 standard.
3.3.4.1 Exceptions
Philip Warner writes:
> >The read eventually dies with a parse error. I'm sure there must be
> >something wrong in my source database that I'm getting this, but I don't
> >even know where to begin tracking down the problem. I've dumped and re-read
> >this database before, but I've added the dat
Joseph Shraibman writes:
> I'm not too familiar with the postgres internals, but the oid tells
> postgres where the row is stored in the filesystem. So by the time
> you've run out of oid's you've probably run out of space on your
> filesystem.
The `tid' specifies the storage location. The `oid'
> > Here's a bothersome issue: I've got the most recent versions of
> > Postgres, ODBC client for Win32, and Access 97. My client can
enter
> > new records fine via a linked table. However, when she goes
back to
> > add data to a column, she gets the following error:
> >
> > message box title
Gilles DAROLD wrote:
>
> jprem wrote:
>
> > hello ,
> >postgreqsl 6.5.3 does not support nested transactions.
> > so i don't think it will be suitable for e-com application.isn't it ?
> > does postgreqsl 7.0 support nested transacions ? is postgresql 7.0 a
> > stable version ?
>
>
mikeo <[EMAIL PROTECTED]> writes:
> we wish to have a database that is history so we
> want to make the disks read only after loading.
> would this cause any problems with POSTGRES?
In theory you could do it given that you vacuum the tables
before locking down the files. (The vacuum is need
[EMAIL PROTECTED] wrote:
> Hi,
>
> Is there a way to write a "generic" trigger function in postgres
> that can loop thru a table's cloumns (using TG_RELNAME)
> and perform certain activities based on, say, certain column-types?
> In other words, is it possible to assign OLD.
> and NEW. to a variab
Paul Caskey <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It's only a hard limit if your application assumes OIDs are unique.
>> If you don't assume that, then I think it's not a big problem.
>>
>> It's possible (though obviously not especially likely) that you might
>> get OID collisions in t
Does anyone know how to make an attribute a collection of
OIDs?
I haven't found any reference of this object-oriented
feature in Postgres online manuals.
Please, let me know any hints/links or anything that could help me doing the following:
===
Assume that each row of tables is identified by OI
22 matches
Mail list logo
