Tom,
> The trouble with pg_dump -o is that after reload, the OID
> generator
> will be set to max(any OID in the dumped data). So a
> dump & reload
> doesn't do anything to postpone OID-wraparound Ragnarok.
>
> As for the likelihood of overflow, figure 4G / tuple
> creation rate
> for your inst
Josh Berkus <[EMAIL PROTECTED]> writes:
> SO I'm concerned about the problems you mentioned above. pg_dump has a
> -o option; are there problems with this? And how liekly are counter
> overflow problems?
The trouble with pg_dump -o is that after reload, the OID generator
will be set to max(any
Michael Fork <[EMAIL PROTECTED]> writes:
> Just a thought, but couldn't you create a sequence that is referenced by
> multiple tables,
I was going to suggest exactly that. It's not quite as simple as a
"serial" column declaration, but you can split the use of an ID sequence
generator over just a
Just a thought, but couldn't you create a sequence that is referenced by
multiple tables, ie:
CREATE SEQUENCE test_seq;
CREATE TABLE tblclients {
client_id default nextval('test_seq'::text),
...
}
CREATE TABLE tblbills {
bill_id default nextval('tes
Tom,
> By and large I'd recommend using a serial column in preference to OIDs,
> though, for two reasons:
>
> 1. dump/restore is more practical that way (don't have to worry about
>saving/reloading OIDs).
>
> 2. counter overflow problems hit you only per-table, not
>per-installation.
H
On Tue, 3 Oct 2000, Michael Ansley wrote:
> Hi, Peter,
>
> I suspected as much of the querying, but I can't even get data into the
> tables. I tried this:
>
> insert into client values ('Michael');
> insert into address values ('11 Windsor Close, 'RH16 4QR');
> INSERT 18935 1
> update client s
"Ingram, Bryan" <[EMAIL PROTECTED]> writes:
> What I'd like to do is produce a query that will
> list each app_code and the count of distinct states for that app_code on one
> line. I don't care what the state_code is, I just need to know the number
> of distinct state_codes per app_code.
> So f
Hello ..
I'm having trouble figuring out a good way to return my desired results from
the following table ...
Table= g_state_county_app
app_code | varchar() not null
state_code | int4 not null
county_code
Hi
I would like to get off the pgsql mailing list, so the posts won't come
into my inbox.
How can I do that?
Which email should I mail to?
--
Med venlig hilsen/ Wishes
Mads Jensen
Homepage: http://www.pcfocus.f2s.com
E-Mail: [EMAIL PROTECTED]
--
Josh Berkus <[EMAIL PROTECTED]> writes:
> 1. Is there a performance loss on searches and joins when I use the OID
> as a liniking field as opposed to a SERIAL column?
> 2. Can I define my own index on the OIDs of a table?
There is absolutely no magic about OIDs, except that the system insists
on
Barry Lind <[EMAIL PROTECTED]> writes:
> I have a table that stores a hierarchy. Sometimes in an update I want
> to join back to the same table to get other information related to
> children or parent rows. In Oracle I can do this using the alias, but
> in Postgresql I cannot.
> update table_fo
It is interesting that this should come up now. Just last week I was
trying to port a SQL statement from Oracle to Postgresql that used table
aliases in an update statement. While I can see that this functionality
wouldn't be used very often it can be very useful under certain
circumstances.
I
Title: RE: [SQL] OID Perfomance - Object-Relational databases
Regarding all of this, can someone tell me in a fairly
technical manner what the difference is between searching for a row using it's
primary key, and searching using it's OID. Rumour has it that it's
faster. Technically, what's
Title: RE: [SQL] OID Perfomance - Object-Relational databases
Unsigned, I think you can double it, although I haven't applied much thought to this, so I could well be wrong.
>> -Original Message-
>> From: Mitch Vincent [mailto:[EMAIL PROTECTED]]
>> Sent: 03 October 2000 17:35
Aren't OIDs just integers? Isn't this limit just the limit of the value an
int4 can hold?
2,147,483,647 is the max for an int4 (I think) so at 500 million a day
you're looking at more like 4.29 (and change) days
If I'm correct in all the above, there wouldn't be any way to increase the
limit wi
On Tue, 3 Oct 2000, Mitch Vincent wrote:
> Aren't there a pretty big concerns when using OIDs as IDs to relate records
> in different tables to each other? Wouldn't the OIDs be totally re-assigned
> if you had to dump/restore your database?
Not if you use the -o flag to pg_dump.
-o D
Aren't there a pretty big concerns when using OIDs as IDs to relate records
in different tables to each other? Wouldn't the OIDs be totally re-assigned
if you had to dump/restore your database?
Just a question to satisfy my own curiosity, thanks!
-Mitch
> Folks,
>
> Because it's a very elegant
Tom,
> >> I just noticed that postgres doesn't totally support
> >> column aliases on UPDATE statements, for example
>
> The SQL92 spec very clearly does not allow an alias on the target table:
I have to agree here. The only improvement from a deviation (alllowing
aliasing) would be cosmetic.
Title: RE: [SQL] OID Perfomance - Object-Relational databases
Hi, Josh,
In fact, the last point about OIDs is particularly pertinent, because we are expected to process up to 500 million records daily, thus exhausting the limit in, um, eight days.
Is anybody aware of when this limit will be
On Wed, 4 Oct 2000, Tod McQuillin wrote:
> > I noticed that it's possible to have a table as a field type.
> > For example:
> > create table foo (val1 integer);
> > create table bar (val2 foo);
> >
> > val2 in table bar ends up as an int4, designed for storing an oid from
> > table foo.
> > Is
Folks,
Because it's a very elegant solution to my database structure issues,
I'm using OID's extensively as referents and foriegn keys. However, I
wanted to see if others had previous experience in this (answer as many
as you like):
1. Is there a performance loss on searches and joins w
On Tue, 3 Oct 2000, David Diller wrote:
> I noticed that it's possible to have a table as a field type.
> For example:
> create table foo (val1 integer);
> create table bar (val2 foo);
>
> val2 in table bar ends up as an int4, designed for storing an oid from
> table foo.
> Is there a way to pe
On Tue, 3 Oct 2000, Michael Ansley wrote:
> I suspected as much of the querying, but I can't even get data into the
> tables. I tried this:
>
> insert into client values ('Michael');
> insert into address values ('11 Windsor Close, 'RH16 4QR');
> INSERT 18935 1
> update client set address = 189
Title: RE: [SQL] Object features of pg
Hi, Kenn,
>> It seems that if you want to define a type address that
>> you will need more than a reference in another table. I
>> see what you're trying to do, but don't understand the
>> advantage of having a type address. Especially when y
I noticed that it's possible to have a table as a field type.
For example:
create table foo (val1 integer);
create table bar (val2 foo);
although the following doesn't work: create table bar2 (val2 foo[]);
val2 in table bar ends up as an int4, designed for storing an oid from
table foo.
Is ther
Title: RE: [SQL] Object features of pg
No. I want the address attribute of the client class to be of type address, which is defined by the address table. Perhaps I should have named things a little more clearly ;-)
>> -Original Message-
>> From: Kenn Thompson [mailto:[EMAIL PRO
Title: RE: [SQL] Object features of pg
Is
anybody using the object features of PG? We're busy evaluating databases
for some prototyping projects, and relational, object and OR databases are all
in the mix. What I'm trying to do is to see how closely PG can match the
object functionality of
Title: RE: [SQL] Object features of pg
Hi, Peter,
I suspected as much of the querying, but I can't even get data into the tables. I tried this:
insert into client values ('Michael');
insert into address values ('11 Windsor Close, 'RH16 4QR');
INSERT 18935 1
update client set address = 189
On Tue, 3 Oct 2000, Michael Ansley wrote:
> I've done the following:
>
> create table address (address varchar(50), postcode varchar(9));
> create table client(id integer, name varchar(30), address address);
>
> Now, how the hell do I get information into the address field of client?
> There ap
Title: Object features of pg
I've done the following:
create table address (address varchar(50), postcode varchar(9));
create table client(id integer, name varchar(30), address address);
Now, how the hell do I get information into the address field of client? There appears to be very litt
This is an example script I use to keep a log of all database operations on
my tables.
Hope it helps.
At 05:05 PM 3/10/2000 +1000, Carolyn Lu Wong wrote:
>[EMAIL PROTECTED] wrote:
> >
> > Carolyn Lu Wong wrote:
> > >
> > > I need to write a trigger to create a new record in log table if it's a
>
Antti Linno ([EMAIL PROTECTED]) napisał:
> Hm, I usually use
> pg_dump -f smthng.out dbname -u
> after that program asks for username and password,
> there were some possibilities within postgres too, but you can find them
> yourself. And why not to dump all data as superuser, that way u have no
Hm, I usually use
pg_dump -f smthng.out dbname -u
after that program asks for username and password,
there were some possibilities within postgres too, but you can find them
yourself. And why not to dump all data as superuser, that way u have no
problems with privileges at all.
Antti
On Tue, 3 Oc
From: Fabrice Scemama <[EMAIL PROTECTED]>
> Try this:
> http://www.rkirkpat.net/software/
> > parallel regression testing's initdb stage fails with a core file and
> > message:
> >
> > FATAL: s_lock (2030d360) at spin.c:116, stuck spinlock. Aborting.
> > FATAL: s_lock (2030d360)
Hi,
is something like this possible?
I have to grant select priviliges to dump database, and I was wondering if
there is easer way to do it then name one, by one every table.
maz
Marcin Mazurek
--
Kierownik Działu Systemowego
MULTINET SA o/Poznan
http://www.multinet.pl/
35 matches
Mail list logo
