Greetings,
I'm using pg 7.3.5 and playing with table inheritance, and I've run into the
fact that foreign keys cannot be defined on inherited attributes. (As much
is stated in the documentation, but it didn't sink in until I ran into the
fact.)
The documents say this will probably be fixed in a f
Where I can get the rpms for PostgreSQL 7.4.1?
The ftp://ftp15.us.postgresql.org/binary/v7.4.1/redhat/ only has
subdirectories for redhat-6.2, redhat-7.3, redhat-8.0, rhas-2.1, rhel3
- Original Message -
From: "Lamar Owen" <[EMAIL PROTECTED]>
To: "Manuel Tejada" <[EMAIL PROTECTED]>; <[
John Wells wrote:
> On this page: http://www.compiere.org/technology/independence.html, the
> project leader of Compiere (a popular ERP package) states that the move to
> Postgres failed because of lack of support of embedded
> transactions...something both Oracle and DB2 support.
>
> Can someone
On this page: http://www.compiere.org/technology/independence.html, the
project leader of Compiere (a popular ERP package) states that the move to
Postgres failed because of lack of support of embedded
transactions...something both Oracle and DB2 support.
Can someone explain to me excactly what em
\copy and COPY are still choking on files with crlf's
in them. I'm using the latest 7.4 version - I thought
I saw coping with this on the feature list.
BTW, anybody know where I can get dos2txt?
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Tr
On Sun, Jan 25, 2004 at 03:10:40PM -0800, Richard Schilling wrote:
>
> I'm forwarding this message onto this list because this is where
> the thread belongs.
With all due respect to your efforts, I don't think this list _is_
where the discussion belongs, if for no other reason than that
license
Jeremiah Jahn wrote:
> although it will be taken care of, make sure that initdb sets the
> local language to C or your string indexes will not be used.. Unless
> this has been fixed and en_US works as as well?
It has been fixed. Be sure to read the documentation about details.
-
I think it's fair to say that out of the box and RPM install should not
result in indexes not being used because the LANG is set to something
other than 'C'. I'm all for reading the manual and tuning later, but
that is something that can't be changed without a complete
dump/initdb/restore. It's jus
my column types are and have always been oid, but for some weird reason
when I dump and restore, I can't seem to reference my blobs anymore. I
have done this a zillion times, and just can't figure our what the heck
I'm doing wrong (this time).
On Mon, 2004-01-26 at 14:03, Tom Lane wrote:
> Jerem
Chris Travers wrote:
> RedHat Enterprise IS redistributable, and there are third party distros
> based on it. However there is one major gotcha:
>
> The contract for the enterprise services for RHEL state that every copy of
> RedHat Enterprise Linux in an organization MUST be signed up for the
>
Jeremiah Jahn <[EMAIL PROTECTED]> writes:
> when I run the following two commands all of my OIDs for my blobs (about
> 5.5 million of them) no longer reference anything in pg_largeobject.
> All of the loid values change.
pg_dump/pg_restore do not (and cannot) arrange for large objects to have
the
Mensaje citado por Jeremiah Jahn <[EMAIL PROTECTED]>:
> although it will be taken care of, make sure that initdb sets the local
> language to C or your string indexes will not be used.. Unless this has
> been fixed and en_US works as as well?
I think that if you really need very fast indexes, the
although it will be taken care of, make sure that initdb sets the local
language to C or your string indexes will not be used.. Unless this has
been fixed and en_US works as as well?
On Mon, 2004-01-26 at 13:32, Peter Eisentraut wrote:
> Jerome Lyles wrote:
> > I have installed Postgresql 7.4 on
Jerome Lyles wrote:
> I have installed Postgresql 7.4 on a Suse 9.0 system using apt.
> I cannot do this:
>
> /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
Just run
/etc/init.d/postgresql start
and it will be taken care of. Read the README files in
/usr/share/doc/packages/postgresql-* t
Mensaje citado por Jerome Lyles <[EMAIL PROTECTED]>:
> Hello List,
>
> I have installed Postgresql 7.4 on a Suse 9.0 system using apt.
> I cannot do this:
>
> /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
>
> Because there is no "/pgsql/bin/initdb" nor /pgsql/bin/ on my system.
> Since a
First of all, yes I know that result rows don't have any
intrinsic ordering that I can expect to not change.
I have a table recording vaccinations for patients roughly
like this:
table vaccinations
pk,
patient,
date_given,
disease
Data in that table would look like this:
1,
1742
when I run the following two commands all of my OIDs for my blobs (about
5.5 million of them) no longer reference anything in pg_largeobject.
All of the loid values change.
the relevant output from pg_restore:
pg_restore: restoring data for table "BLOBS"
pg_restore: connecting to database "copa" a
Hello all,
I'm messing around with the Server Programming Interface and the
particular example presented at:
http://www.postgresql.org/docs/current/interactive/spi-examples.html
Ideally, I would want to make the example function return the
information as a "set" and not through elog() so I can
Baldur Norddahl wrote:
> Hi,
>
> I just noticed that I could do this:
>
> webshop=# create table foo (bar text not null primary key);
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "foo_pkey" for
> table "foo"
> CREATE TABLE
> webshop=# create table foo2 (bar text not null, fore
Hello List,
I have installed Postgresql 7.4 on a Suse 9.0 system using apt.
I cannot do this:
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
Because there is no "/pgsql/bin/initdb" nor /pgsql/bin/ on my system.
Since apt did not create these directories how can I do it manually?
Thanks,
Je
20 matches
Mail list logo
