Hi,
Can you have persistant objects in PostgreSQL? In
Oracle you can have create Object types. e.g
create type ADDRESS as object
(street_name VARCHAR2(30),
house_noNUMBER);
In Oracle you can even have references to these
objects from other tables.
Is persistant objects and refe
Hello,
On the production server I have PostgreSql 7.4.3 , on Mandrake Linux 9.2.
In the message log on 29 july I have received several "shared buffer
hash table
corrupted" errors .
What could cause this error ? (bad RAM maybe?)
Best wishes,
Adrian Maier
---(end of br
I just remembered that although we now have COMMENT ON LARGE OBJECT
, we haven't changed pg_dump to dump and restore these comments.
I went ahead and did this, but then realised that I cannot just dump the
comments normally as the oid the lob is assigned when it's restored is
not necessarily go
On Sun, 1 Aug 2004, Marc G. Fournier wrote:
>
> Not sure why we don't have a doc/7.4 directory though ... but, looking in
> the other directories, those are the PDF versions, and I don't believe
> anyone submitted PDF versions of the 7.4 docs ... anyone?
>
http://www.postgresql.org/docs/#pdf
I notice that we can now tick some more stuff off this list:
http://developer.postgresql.org/docs/postgres/unsupported-features-sql99.html
eg. savepoints.
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://
Marc G. Fournier wrote:
On Mon, 2 Aug 2004, Gaetano Mendola wrote:
Hi all,
I'm seeing that a link is missing inside the src directory,
the last version is 7.4.1 !! There is also something wrong
with the doc directory.
Please provide an exact path for what you are seeing ... everything I
see point
k, /pub/src links fixed ...
Not sure why we don't have a doc/7.4 directory though ... but, looking in
the other directories, those are the PDF versions, and I don't believe
anyone submitted PDF versions of the 7.4 docs ... anyone?
On Mon, 2 Aug 2004, Gaetano Mendola wrote:
Marc G. Fournier wrote
Tom Lane <[EMAIL PROTECTED]> writes:
> Huh? That is exactly counter to most people's expectations about
> version numbering. N.0 is the unstable release, N.1 is the one
> with some bugs shaken out. If we release a 7.5 people will expect
> it to be less buggy than 7.4, and I'm not sure we can pr
Just a quick note that the various VMs for *.postgresql.org will be moved
this week to the new server ... I'm hoping to get the main CVS moved over
on Wednesday night, and the web site(s) over on Thursday ... it all
depends on any problems getting the server into the rack on Wednesday ...
For t
On Mon, 2 Aug 2004, Gaetano Mendola wrote:
Hi all,
I'm seeing that a link is missing inside the src directory,
the last version is 7.4.1 !! There is also something wrong
with the doc directory.
Please provide an exact path for what you are seeing ... everything I see
points to 7.4.3, at least at t
Christopher Browne <[EMAIL PROTECTED]> writes:
> I think that the set of new features here will fairly likely warrant
> the "8.0" moniker; the 'consistent' way to go would be to call this
> version 7.5, and then 8.0 would soon follow, and be the release where
> some degree of improved "maturity" ha
Christopher Browne wrote:
After takin a swig o' Arrakan spice grog, Gaetano Mendola <[EMAIL PROTECTED]> belched
out:
Peter Eisentraut wrote:
Alvaro Herrera wrote:
What was the rule for increasing the first number after just before
7.0?
That was just to avoid having to release a 6.6.6, which Jan
Hi all,
I'm seeing that a link is missing inside the src directory,
the last version is 7.4.1 !! There is also something wrong
with the doc directory.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space ma
After takin a swig o' Arrakan spice grog, Gaetano Mendola <[EMAIL PROTECTED]> belched
out:
> Peter Eisentraut wrote:
>
>> Alvaro Herrera wrote:
>>
>>>What was the rule for increasing the first number after just before
>>>7.0?
>> That was just to avoid having to release a 6.6.6, which Jan had
>> cl
[EMAIL PROTECTED] (Tom Lane) wrote:
> Does anyone have a problem with this macro syntax? The try/catch
> names are stolen from Java, so I'm figuring they won't terribly
> surprise any modern programmer, but I'm open to different names if
> anyone has a better idea.
Mitch Bradley, once of Sun, onc
[EMAIL PROTECTED] (chinni) writes:
> Postgres-R is a multi server (write anywhere) replication tool
> which is possibly important for any enterprise if they want to shift
> to postgres.
>
> Did you guys debate on merging it.
I seem to recall there being a licensing issue; Postgres-R uses the
Peter,
> Eventually we'll do the Sun switcheroo and follow release 7.12 by 13.0.
Even better, we can have two different, parallel version numbers, so that the
next version can be 7.5 *and* 13.0.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast
On Sun, 1 Aug 2004, Peter Eisentraut wrote:
Alvaro Herrera wrote:
What was the rule for increasing the first number after just before
7.0?
That was just to avoid having to release a 6.6.6, which Jan had clearly
been working towards. :-)
Seriously, major version jumps correspond to epoch-like change
On Sat, Jul 31, 2004 at 22:40:52 -0700,
Steve Atkins <[EMAIL PROTECTED]> wrote:
>
> 8.0.0 suggests, to my customers at least, a brand new release with
> either massive re-architecting, many new features or both and that's
> likely to be riddled with bugs. While it would be unlikely that we'd
> s
Fixed.
---
Devrim GUNDUZ wrote:
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Hi,
>
> On Sun, 1 Aug 2004, Christopher Kings-Lynne wrote:
>
> > I'm seeing this:
> >
> > g
Peter Eisentraut wrote:
Alvaro Herrera wrote:
What was the rule for increasing the first number after just before
7.0?
That was just to avoid having to release a 6.6.6, which Jan had clearly
been working towards. :-)
Seriously, major version jumps correspond to epoch-like changes, like
when the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sun, 1 Aug 2004, Christopher Kings-Lynne wrote:
> I'm seeing this:
>
> gmake[4]: Leaving directory `/usr/home/chriskl/pgsql-server/src/port'
> gmake[3]: *** No rule to make target `pg_config.o', needed by `pg_config'.
> Stop.
> gmake[3]: Lea
I'm seeing this:
gmake[4]: Leaving directory `/usr/home/chriskl/pgsql-server/src/port'
gmake[3]: *** No rule to make target `pg_config.o', needed by `pg_config'.
Stop.
gmake[3]: Leaving directory
`/usr/home/chriskl/pgsql-server/src/bin/pg_config'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving direc
Since not only \ but also other characters that have special meaning
to compiler are used by Big5 Chinese characters. Adding an extra \
can make non-Big5 aware environment happy. I think we can get rid of
this dirty work by using UTF-8 instead of the annoying Big5 problem.
On Sun, 1 Aug 2004 01:17
> OK, we scheduled beta for August 1, and we are close, but we should get
> a few more patches in before bundling beta. I have applied all I could
> from the patch queue. Tom needs to review the rest.
Of my three patches, they are all "bug fixes", however the USING INDEX
TABLESPACE one should pr
> OK, we scheduled beta for August 1, and we are close, but we should get
> a few more patches in before bundling beta. I have applied all I could
> from the patch queue. Tom needs to review the rest.
Oh, and perhaps once the owner/acl fix patch is in, then whoever commits
Fabien's patch to fix
OK, we scheduled beta for August 1, and we are close, but we should get
a few more patches in before bundling beta. I have applied all I could
from the patch queue. Tom needs to review the rest.
Plus we have a nested transaction patch to apply and a little PITR work
left to do. We should be abl
27 matches
Mail list logo
