> Tom Lane wrote:
>> This isn't PQreset()'s fault that I can see. This is a race condition
>> caused by bogosity in PostgresMain --- it enables SIGUSR1 before it's
>> set up the correct signal handler for same. The postmaster should have
>> started the child process with all signals blocked, so
> in general yes, I couldn't say what is adding support variable size of
> index keys
Oleg, the correct answer at this point is always "yes Marc it is just
bug fixes" ;)
The GiST stuff is *really great*, but as you've noticed was also sorely
neglected. It will be A Good Thing to get this stuff a
> where and is this already availiable?
It is already in the current PostgreSQL code tree, to be included in the
7.1 release. I can get it posted elsewhere if you would find that
helpful.
- Thomas
> > I've committed to contrib/mysql/ a utility called mysql2pgsql to help
>
> > I've committed contrib/rserv/ which provides replication capabilities to
> > PostgreSQL. The code was developed by Vadim, with some script and
> > wrapper support from myself.
> How does this jive with www.erserver.com? Completely seperate projects?
> Have you already explored working togethe
> I suggest that each such benchmark script include code to check if
> the sample database is present and, if not, download it from its
> canonical site, massage it into shape and import it. Then there
> would be no need to limit the number and variety of large sample
> databases that a build may
> We finished (cross fingers) our changes in GiST code for 7.0.3
> and in next 2 days we plan to send patches for upcoming 7.1 release.
> Isn't this too late ? What else we need to submit ?
Not too late, especially if it is fixing bugs. And even if not, anything
we can do to encourage active deve
On Wed, 20 Dec 2000, The Hermit Hacker wrote:
> Date: Wed, 20 Dec 2000 18:48:03 -0400 (AST)
> From: The Hermit Hacker <[EMAIL PROTECTED]>
> To: Oleg Bartunov <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Future beta releases ...
>
>
> the GiST changes are more fixes ...
On Wed, 20 Dec 2000, Tom Lane wrote:
> Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> > INSERT INTO OID_TBL(f1) VALUES ('-1040');
> > ERROR: oidin: error reading "-1040": value too large
>
> That's coming from a possibly-misguided error check that I put into
> oidin():
...
> On a 32-bit machine
ListAdmin: Ignore the stalled/delayed posts from me earlier.
Accidently posted with the wrong from address :(
On Wed, 20 Dec 2000, Tom Lane wrote:
> Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> > INSERT INTO OID_TBL(f1) VALUES ('-1040');
> > ERROR: oidin: error reading "-1040": va
Hello,
Anyone have any clues why such crap can happend?
slygreetings=# vacuum verbose analyze statistic;
NOTICE: --Relation statistic --
NOTICE: Pages 498: Changed 1, reaped 490, Empty 0, New 0; Tup 1167: Vac 0,
Keep/VTL 1110/1110, Crash 0, UnUsed 76888, MinLen 48, MaxLen 48; Re-using:
Free/
Tom Lane wrote:
>
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> > postmaster: BackendStartup: pid 395 user reindex db reindex socket 5
> > DEBUG: exit(2)
> > postmaster: reaping dead processes...
> > postmaster: CleanupProc: pid 394 exited with status 512
> > Server process (pid 394) exited wit
try to go to http://208.160.255.143 there's a compiled postgresql
server...
On Tue, 19 Dec 2000, Luis [UNKNOWN] Magaña wrote:
> Hello:
>
> while compiling in windows 2000 got this error:
>
> YS.o hash/SUBSYS.o init/SUBSYS.o misc/SUBSYS.o mmgr/SUBSYS.o
> sort/SUBSYS.o time/
> SUBSYS.o
> ma
Tom Lane wrote:
>
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> > It seems that init_irels() should be called after
> > InitializeTransactionSystem() was called.
>
> Can we just swap the order of the RelationCacheInitialize() and
> InitializeTransactionSystem() calls in InitPostgres? If that
>
On Wed, 20 Dec 2000, Dan wrote:
> > I've committed contrib/rserv/ which provides replication capabilities to
> > PostgreSQL. The code was developed by Vadim, with some script and
> > wrapper support from myself.
> [snip]
> > - Thomas
>
> How does this jive with www.erserver
> I've committed contrib/rserv/ which provides replication capabilities to
> PostgreSQL. The code was developed by Vadim, with some script and
> wrapper support from myself.
[snip]
> - Thomas
How does this jive with www.erserver.com? Completely seperate projects?
Have you a
On Wed, Dec 20, 2000 at 12:41:01AM +, Josh Rovero wrote:
> mlw wrote:
> > I am doing some testing and development on Postgres.
> >
> > Is there, by chance, a good source of data which can be used as a test
> > database? I have been using a music database, but it is proprietary, and
> > makes
the GiST changes are more fixes ... no?
On Thu, 21 Dec 2000, Oleg Bartunov wrote:
> I'd like to get into some beta release with GiST changes.
> I want people who use GiST (not so much expected) to test
> changes. I've posted a list of changes.
>
> Regards,
> Oleg
>
> On Wed, 20 Dec 200
I'd like to get into some beta release with GiST changes.
I want people who use GiST (not so much expected) to test
changes. I've posted a list of changes.
Regards,
Oleg
On Wed, 20 Dec 2000, The Hermit Hacker wrote:
> Date: Wed, 20 Dec 2000 17:04:16 -0400 (AST)
> From: The Hermit Hacker
On Wed, 20 Dec 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > beta2 - vadim finishes WAL stuff he's currently working on
>
> I think the TOAST-table-vacuuming issue is a "must fix for beta2", also.
> I'm on it now...
Agreed ... that list wasn't a "beta2 happens as soo
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> beta2 - vadim finishes WAL stuff he's currently working on
I think the TOAST-table-vacuuming issue is a "must fix for beta2", also.
I'm on it now...
regards, tom lane
Morning ...
Just to let ppl know what I'm using as milestones for beta
releases:
beta2 - vadim finishes WAL stuff he's currently working on
beta3 - vadim incorporates LAZY extension to VACUUM
beta4 - a week later to clean out any bugs as a result of beta3
beta5 - first release candidate
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> Probably we need to add regression test for GiST.
That would be nice, but let's not hold up the patches for it.
regards, tom lane
We finished (cross fingers) our changes in GiST code for 7.0.3
and in next 2 days we plan to send patches for upcoming 7.1 release.
Isn't this too late ? What else we need to submit ?
We have int4array contribution package which added index support for
integer arrays and it's probably should come
INSERT INTO ciudad (ciudad) VALUES
("Villa Guillermina")
Use single quotes instead of double quotes.
--
- Thomas Swan
- Graduate Student - Computer Science
- The University of Mississippi
-
- "People can be categorized into two fundamental
- groups, those
Hi, I have this table on postgres-7.0.3
CREATE TABLE ciudad (
id_ciudadSERIAL,
ciudad VARCHAR(60)
);
GRANT ALL ON ciudad TO martin;
CREATE INDEX ciudad_idx ON ciudad (ciudad);
And I try to insert a value using this query:
INSERT INTO ciudad (ciudad) VALUES ("Villa Guil
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> ISTM that correlation names aren't allowed after joined tables in the
> first place.
> ::=
> [ [ AS ]
> [] ]
> | [ AS ]
> []
> |
> :
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> seems rtree doesn't ignore NULL ?
Hm, maybe not. There are explicit tests to ignore null inputs in hash
indexes (hash/hash.c), and I'd just sort of assumed that rtree and gist
do the same.
FWIW, your example doesn't seem to provoke an error in current
mlw <[EMAIL PROTECTED]> writes:
> There are three basic types of SQL behaviors that should be able to be
> performed.
> (1) "function()" returns a single value. Postgres should be able to
> understand how to optimize this to be: "select * from table where col =
> value" where value is the datum r
where and is this already availiable?
Mike
> I've committed to contrib/mysql/ a utility called mysql2pgsql to help
> with database conversions from MySQL. It requires perl5 and not much
> else besides a MySQL schema dump file.
>
> Thanks to Tim Perdue for testing and feedback.
>
>
mlw <[EMAIL PROTECTED]> writes:
> Perhaps we can create a substantial test database? (Millions of records,
> many tables, and a number of relations.) So when we see a problem, we
> can all see it right away. I like "real world" data, because it is often
> more organic than randomized test data, an
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> postmaster: BackendStartup: pid 395 user reindex db reindex socket 5
> DEBUG: exit(2)
> postmaster: reaping dead processes...
> postmaster: CleanupProc: pid 394 exited with status 512
> Server process (pid 394) exited with status 512 at Tue Dec 19 20:
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> It seems that init_irels() should be called after
> InitializeTransactionSystem() was called.
Can we just swap the order of the RelationCacheInitialize() and
InitializeTransactionSystem() calls in InitPostgres? If that
works, I'd have no objection.
* Paul A Vixie <[EMAIL PROTECTED]> [001220 10:28]:
> > Question is whether proper (standard/most-commonly-used) format for
> > printing CIDR network address is 10/8 or 10.0.0.0/8 (i.e. should all
> > octets be printed even if they are 0). After search of RFCs, there's
> > nothing that specifies th
Paul A Vixie <[EMAIL PROTECTED]> writes:
> http://www.vix.com/~vixie/results-psql.png shows a gnuplot of the wall time
> of 70K executions of "pgcat" (shown below) using a CIDR key and TEXT value.
I get a 404 on that URL :-(
> anybody know what i could be doing wrong? (i'm also wondering why SE
Paul A Vixie <[EMAIL PROTECTED]> writes:
> cisco IOS just won't take 10/8 and insists on 10.0.0.0/8. you will never,
> ever go wrong if you try to use 10.0.0.0/8, since everything that understands
> CIDR understands that. 10/8 is a pleasant-appearing alternative format, but
> it is not universal
I've committed to contrib/mysql/ a utility called mysql2pgsql to help
with database conversions from MySQL. It requires perl5 and not much
else besides a MySQL schema dump file.
Thanks to Tim Perdue for testing and feedback.
- Thomas
> VACUUM ANALYZE after the INSERTs made no performance difference at all,
> which is good since no other modern database requires anything to be done
> to improve performance after a large number of INSERTs. (i can understand
> why COPY would need it, but not INSERT.)
afaik every modern database
Paul A Vixie <[EMAIL PROTECTED]> writes:
> the occasional 1.2sec has got to be due to some kind of scheduling or I/O
> irregularity.
Hmm, could it just be delay when your syncer process runs? Under WAL,
I believe we don't fsync anything except the WAL log file, so a bulk
insert operation would p
> > anybody know what i could be doing wrong? (i'm also wondering why SELECT
> > takes ~250ms whereas INSERT takes ~70ms... seems counterintuitive, unless
> > TOAST is doing a LOT better than i think.)
>
> I would think that this is entirely due to planning the query. An INSERT
> has no decision
The NIMA web site has tab-delimited version of the
Airfield Information database files. Lots of data,
many tables to relate. Some elements are geographic,
others are text and numeric feature attributes.
mlw wrote:
> I am doing some testing and development on Postgres.
>
> Is there, by chance,
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Here, we've just dropped the testttype that the operator ^^^ uses. This
> does not cause the operator to be deleted, it simply reverts its left and
> right args to 'NONE'.
No, it doesn't "revert the types to NONE", because there isn't any s
Hello:
while compiling in windows 2000 got this error:
YS.o hash/SUBSYS.o init/SUBSYS.o misc/SUBSYS.o mmgr/SUBSYS.o
sort/SUBSYS.o time/
SUBSYS.o
make[2]: Leaving directory `/usr/src/postgresql-7.0.
3/src/backend/utils'
make -C ../utils dllinit.o
make[2]: Entering directory `/usr/src/postgresql-
the prior results (http://www.vix.com/~vixie/pgsql-results.png) showed:
~70ms usual INSERT time (~1.5sec -> ~1.25sec occasional)
~250ms usual SELECT time (~1.5sec occasional)
changing the attribute i key by to be PRIMARY KEY improved things a lot;
the new results (http://www.vix.
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> [ "CREATE OPERATOR testbit" is accepted ]
Not only that, but it looks like you can create aggregate functions and
types that have operator-like names :-(. Someone was way too eager to
save a production or two, I think:
DefineStmt: CREATE
I've committed contrib/rserv/ which provides replication capabilities to
PostgreSQL. The code was developed by Vadim, with some script and
wrapper support from myself. The current version has been tested under
Linux only, though I know of no reason why it won't work elsewhere.
Requires PostgreSQL,
Hi,there,
I hope it helps;
1. postgres by default allows 16 sessiones(if I don't remember wrong)
at same time. You can change the setting according to the doccument.
open too many sessiones at same time will more or less affect the
performance.
2. I believe that using Pg module will be
""Christopher Kings-Lynne"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > Reading the documentation, I see that OIDs are unique through
> the
> > > whole database.
> > > But since OIDs are int4, does that limit the number of rows I
> can
>
bpalmer <[EMAIL PROTECTED]> writes:
> [ lots of regress failures ]
Doesn't look good, but it's impossible to tell what's wrong from that
amount of info...
regards, tom lane
>
> CREATE OPERATOR testbit (
> leftarg = bitset,
> rightarg = int4,
> procedure = testbit,
> commutator = testbit
> );
>
> Now we have a big problem, as the DROP OPERATOR command
> cannot delete the illegally named operator.
Have you tried deleting it directly from pg_operator in
The constraint naming isn't really terribly sensible right now. The
names generated should be unique within I think schema according to
the spec and I think that should be true even if users name a constraint
such that it would cause a collision (so, if i name a constraint what
an automatic cons
> Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> > INSERT INTO OID_TBL(f1) VALUES ('-1040');
> > ERROR: oidin: error reading "-1040": value too large
>
> That's coming from a possibly-misguided error check that I put into
> oidin():
>
> unsigned long cvt;
> char *endptr;
>
>
From: "Ryan Kirkpatrick" <[EMAIL PROTECTED]>
> On Sat, 16 Dec 2000, Bruce Momjian wrote:
>
> > Here is the list of features in 7.1.
>
> One thing that I think ought to be added is that with 7.1,
> PostgreSQL will compile out of the box (i.e. without any extra patches)
> for Linux/Alpha.
What pa
Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> INSERT INTO OID_TBL(f1) VALUES ('-1040');
> ERROR: oidin: error reading "-1040": value too large
That's coming from a possibly-misguided error check that I put into
oidin():
unsigned long cvt;
char *endptr;
cvt = strt
> > Has anyone successfully done this? and if so, how is the
> documentation
> > quoted above inforrect?
>
> When I did my testing, I just took some cert's that I had generated
> through Apache's make certificate command - just don't enter
> a passphrase,
> then copy the certificate and key. Wo
> 1) Have you ran vacuum analyze after all these inserts to update database
> statistics? :) Without vacuum, pgsql will opt to table scan even when
> there's an index.
i hadn't, but i did, and it didn't make that particular difference:
vixie=# explain select file from rss where addr = '1
On Wed, 20 Dec 2000, Oliver Elphick wrote:
> Has anyone successfully done this? and if so, how is the documentation
> quoted above inforrect?
When I did my testing, I just took some cert's that I had generated
through Apache's make certificate command - just don't enter a passphrase,
then copy t
I've been experimenting with the SSL connection support. Unfortunately I can't
get the postmaster to start because the instructions in the documentation for
setting up a certificate don't work.
They say:
=
For details on
I think i already discovered what's the problem !! At least the problem is not
happening again.
It was some problems in some triggers that are implementend in the database.
Anyway, i appreciatte all the time that you took with my problem
Best Regards
Luis Sousa
Stephan Szabo wrote:
> Actu
Ok, after being a little quiet recently things are picking up (well at least
for now).
Anyhow, here's whats happening on the JDBC front:
1) ANT vs Make
As someone (sorry forgotten your name) suggested using ANT instead of Make
for building the driver. Well yesterday was pretty quiet here so I f
Karel Zak wrote:
>
> On Tue, 19 Dec 2000, Bruce Momjian wrote:
>
> > > PS. -hackers: What happen with PL/Python? Before 1/2 of year I ask if
> > > anyone works on this and answer was: "yes, but 'he' is waiting for new
> > > fmgr design". Tom's fmgr is done... IMHO it's big worse - The Py
Hi
On LM 7.2-devel pgsql7.03 needs libc.so.6 GLIB2_2.
Would anybody reply what packages do I need to download with
glibc-2.2.21.rpm ?
Thanks
Lucian
In our test environment, we performed the following set of commands (given
that the in/out functions already exist):
CREATE TYPE testtype (
internallength = 4,
input = test_in,
output = test_out
);
CREATE FUNCTION test_function(testtype, testtype)
RETURNS bool
AS '/usr/local/
Hi,
I think it would be convenient to add a sequence number on each mail
on the list. I have been always annoyed by identifying a mail in the
archive, "the mail is from foo around 2000/12/20..." Rather than
that, it would be nice to say "the mail is 1234567th mail on the
hackers list." How do yo
As part of our development, one of our programmers created a new database
type, plus operators and functions to go with it. One of the things he did
was this:
CREATE OPERATOR testbit (
leftarg = bitset,
rightarg = int4,
procedure = testbit,
commutator = testbit
);
Notice that th
64 matches
Mail list logo
