Ryan Bradetich said:
the table would look like:
1 | Mon Feb 17 00:34:24 MST 2003 | p101 | user x has an invalid shell.
1 | Mon Feb 17 00:34:24 MST 2003 | p101 | user y has an invalid shell.
1 | Mon Feb 17 00:34:24 MST 2003 | p101 | user y has expired password.
2 | Mon Feb 17 00:34:24 MST
I ended up with few only indexes on the operations table, because the
processes that fill it up do minimal lookups to see if data is already in the
table, if not do inserts. Then at regular intervals, the table is cleaned up -
that is, a process to remove the duplicate is run. This
On Sun, Feb 16, 2003 at 23:51:49 -0500,
Greg Stark [EMAIL PROTECTED] wrote:
Hm, odd, nobody mentioned this solution:
If you don't have a primary key already, create a unique index on the
combination you want to be unique. Then:
. Try to insert the record
. If you get a duplicate key
But this argument is mostly irrelevant if the proposed change will not
affect behavior in a default installation. I guess I'm not entirely
clear on exactly which cases it will affect. What will your proposed
change do in each possible combination (database encoding is SQL_ASCII
or not,
Hi,
I've seen this (see below) in the postmaster's log-file.
I doubt this is normal behaviour.
I'm using PostgreSQL 7.2.3 on hppa-hp-hpux10.20, compiled by GCC 2.95.2
Does anybody know what may cause calls to semctl resp. shmctl
(semaphore control resp. shared memory control) to fail?
The
Greetings,
I am doing a project for college developing a java
system utilizing a RDBMS. The choice is between PostgreSQL and Oracle and I'm
wondering exactly how impossible would it be to make it compatible with both.
Postgre is said to be completely ANSI SQL complaint, is it feasible to
Ryan Bradetich [EMAIL PROTECTED] writes:
the table would look like:
1 | Mon Feb 17 00:34:24 MST 2003 | p101 | user x has an invalid shell.
1 | Mon Feb 17 00:34:24 MST 2003 | p101 | user y has an invalid shell.
Ah, I see your point now. (Thinks: what about separating the anomaly
column into an
Christoph Haller [EMAIL PROTECTED] writes:
I've seen this (see below) in the postmaster's log-file.
I doubt this is normal behaviour.
I'm using PostgreSQL 7.2.3 on hppa-hp-hpux10.20, compiled by GCC 2.95.2
Does anybody know what may cause calls to semctl resp. shmctl
(semaphore control resp.
This is a fairly spectacular failure :-(. As far as I can see from
the
semctl and shmctl man pages, the only plausible reason for EINVAL is
that something had deleted the semaphores and shared memory out from
under Postgres. I do not believe that Postgres itself could have done
that ---
On Mon, 16 Feb 2003, Ryan Bradetich wrote:
I am not sure why all the data is duplicated in the index ...
Well, you have to have the full key in the index, or how would you know,
when you look at a particular index item, if it actually matches what
you're searching for?
MS SQL server does have
Martin Matusiak kirjutas E, 17.02.2003 kell 16:53:
Greetings,
I am doing a project for college developing a java system utilizing a
RDBMS. The choice is between PostgreSQL and Oracle and I'm wondering
exactly how impossible would it be to make it compatible with both.
Postgre is said to be
This is a patch that allows PostgreSQL to use a configuration
file that is outside the main database directory.
It adds one more command line parameter, -C which
specifies the location of the postgres configuration file.
A patched version of PostgreSQL will function as:
postmaster -C
Kevin Brown [EMAIL PROTECTED] writes:
Is it possible for the database engine to properly deal with a
database when it is told to use a different database encoding than the
one the database was initdb'd with?
It can't be told to use a different database encoding. However, the
default *client*
mlw [EMAIL PROTECTED] writes:
If no hba_conf and/or ident_conf setting is specified, the default
$PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
If you are trying to keep your config files out of the data
On Fri, Feb 14, 2003 at 10:35:41AM -0500, Tom Lane wrote:
FHS or no FHS, I would think that the preferred arrangement would be to
keep Postgres' config files in a postgres-owned subdirectory, not
directly in /etc. That way you need not be root to edit them. (My idea
Besides, what are you
On Sun, Feb 16, 2003 at 12:16:44AM -0500, Tom Lane wrote:
Nor will I buy an argument that only a few developers have need for test
installations. Ordinary users will want to do that anytime they are
doing preliminary tests on a new PG version before migrating their
production database to it.
Christoph Haller wrote:
No, I'm not sure at all about a loose-cannon script running around
issuing ipcrm commands.
I have to ask the other staff members what scripts are running.
I already had a suspicion that something like an ipcrm command is
causing this,
but it was denied. Now, with your
Tom Lane wrote:
mlw [EMAIL PROTECTED] writes:
If no hba_conf and/or ident_conf setting is specified, the default
$PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
If you are trying to keep your config
Curt Sampson wrote:
On Mon, 16 Feb 2003, Ryan Bradetich wrote:
Since my only requirement is that the rows be unique, I have developed a
custom MD5 function in C, and created an index on the MD5 hash of the
concatanation of all the fields.
Well, that won't guarantee uniqueness, since it's
Postgres has a bad habit of becoming very confused if the page header of
a page on disk has become corrupted. In particular, bogus values in the
pd_lower field tend to make it look like there are many more tuples than
there really are, and of course these tuples contain garbage. That
leads to
Tom == Tom Lane [EMAIL PROTECTED] writes:
Tom Postgres has a bad habit of becoming very confused if the
Tom page header of a page on disk has become corrupted. In
Tom particular, bogus values in the pd_lower field tend to make
I haven't read this piece of pgsql code very carefully
On Thu, Feb 13, 2003 at 03:27:01PM +1000, Paul L Daniels wrote:
Good evening, tonight while running my routine vacuum, the following came up on my
screen:
---8---
NOTICE: Rel xamefiles: Uninitialized page 708135 - fixing
NOTICE: Rel xamefiles: Uninitialized page 708136 -
I noticed a pretty obscure deadlock condition with REINDEX in CVS HEAD:
client1:
nconway=# create table a (b int unique, c int unique);
CREATE TABLE
nconway=# begin;
BEGIN
nconway=# lock table a in access exclusive mode;
LOCK TABLE
client2:
nconway=# reindex index a_b_key;
blocks, waiting to
Andrew Sullivan [EMAIL PROTECTED] writes:
On Thu, Feb 13, 2003 at 03:27:01PM +1000, Paul L Daniels wrote:
NOTICE: Rel xamefiles: Uninitialized page 708135 - fixing
NOTICE: Rel xamefiles: Uninitialized page 708136 - fixing
NOTICE: Rel xamefiles: Uninitialized page 708137 - fixing
This is a
I'm preparing a patch to make more psql slash commands
tab-completable (\di, \dv etc-) and have come across the following dilemma:
- only relations visible in the current search path should be returned [*]
- to determine visibilty via pg_catalog.pg_table_is_visible(), the
relation's OID is
Hello,
I was wondering what kind of functions/constants exist in Postgre to dig
up
metadata. I barely scratched the surface of Oracle but I know you find
things like user_tables there that can be used to extract info about your
tables. What I'm looking for is some kind of functions to
On Mon, 17 Feb 2003, Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
On Mon, 2003-02-17 at 18:39, Tom Lane wrote:
If you release the lock then I think you are opening yourself to worse
troubles than this one, having to do with someone renaming/deleting the
table and/or index out
This is a fairly spectacular failure :-(. As far as I can see from the
semctl and shmctl man pages, the only plausible reason for EINVAL is
that something had deleted the semaphores and shared memory out from
under Postgres. I do not believe that Postgres itself could have done
that --- it
On Mon, 17 Feb 2003, Tom Lane wrote:
Postgres has a bad habit of becoming very confused if the page header of
a page on disk has become corrupted.
What typically causes this corruption?
If it's any kind of a serious problem, maybe it would be worth keeping
a CRC of the header at the end of
I didn't think pgstattuple had proper visibility checks.
---
Hans-Jürgen Schönig wrote:
This patch adds a note to the documentation describing why the
performance of min() and max() is slow when applied to the entire
Curt Sampson [EMAIL PROTECTED] writes:
On Mon, 17 Feb 2003, Tom Lane wrote:
Postgres has a bad habit of becoming very confused if the page header of
a page on disk has become corrupted.
What typically causes this corruption?
Well, I'd like to know that too. I have seen some cases that were
[EMAIL PROTECTED] (Martin Matusiak) wrote:
Would it be possible to create some sort of transparent API based on
ODBC to be used with PostgreSQL and Oracle? I know there exists a
JDBC - ODBC bridge for java.
If you wrote your application exclusively using JDBC using functions
existing in both
On Mon, 17 Feb 2003, Tom Lane wrote:
Curt Sampson [EMAIL PROTECTED] writes:
If it's any kind of a serious problem, maybe it would be worth keeping
a CRC of the header at the end of the page somewhere.
See past discussions about keeping CRCs of page contents. Ultimately
I think it's a
Curt Sampson [EMAIL PROTECTED] writes:
Well, I wasn't proposing the whole page, just the header. That would be
significantly cheaper (in fact, there's no real need even for a CRC;
probably just xoring all of the words in the header into one word would
be fine) and would tell you if the page
On Tue, 18 Feb 2003, Tom Lane wrote:
The header is only a dozen or two bytes long, so torn-page syndrome
won't result in header corruption.
No. But the checksum would detect both header corruption and torn pages.
Two for the price of one. But I don't think it's worth changing the page
layout
Added to TODO:
* Allow CIDR format to be used in pg_hba.conf
---
Kurt Roeckx wrote:
Currently in pg_hba.conf you specify the ip addresses that can
connect with 2 fields: the ip address and the mask.
What do
Can this improvement get merged up into CVS current, or did you already
do that Tom?
---
Tatsuo Ishii wrote:
Nice work, Tatsuo! Wade, can you confirm that this patch solves your
problem?
Tatsuo, please commit into
Tatsuo Ishii [EMAIL PROTECTED] writes:
The database encoding is set to the encoding when the database was
created and the default value of the client encoding is set to same as
the database encoding. This behavior will not be changed by the change
I proposed.
As long as it still behaves that
Christopher Kings-Lynne wrote:
If you don't have a primary key already, create a unique index on the
combination you want to be unique. Then:
. Try to insert the record
. If you get a duplicate key error
then do update instead
No possibilities of duplicate records due to race
Tom Lane wrote:
mlw [EMAIL PROTECTED] writes:
If no hba_conf and/or ident_conf setting is specified, the default
$PGDATA/pg_hba.conf and/or $PGDATA/pg_ident.conf will be used.
Doesn't anybody see the (a) inconsistency and (b) uselessness of this?
If you are trying to keep your config
mlw wrote:
I don't like the idea of specifying a directory, per se' because if you
have multiple database installations, how would you share the
configuration without symlinks?
Oh, for example, you would be sharing postgresql.conf, perhaps, but not
pg_hba.conf.
--
Bruce Momjian
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Oleg Bartunov wrote:
Bruce,
we just
Bruce Momjian [EMAIL PROTECTED] writes:
Can this improvement get merged up into CVS current, or did you already
do that Tom?
It's irrelevant to current.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off
Bruce Momjian [EMAIL PROTECTED] writes:
I didn't think pgstattuple had proper visibility checks.
It doesn't, see followup discussion.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
I am not sure about this patch. First, src/bin/pg_dump/po/pt_BR.po
isn't in CVS anymore. Seems we don't have a Portugese translation file
anymore for this. As far as Kerberos, you are the first to mention
those additional libraries. Perhaps something for LIBS in
Makefile.global would fix this,
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Teodor Sigaev wrote:
Please apply
People seemed to like the idea:
Add a script to ask system configuration questions and tune
postgresql.conf.
---
Bruce Momjian wrote:
Peter Eisentraut wrote:
Tom Lane writes:
Well, as I commented
Would it be possible to create some sort of transparent API based on ODBC to
be used with PostgreSQL and Oracle? I know there exists a JDBC - ODBC bridge
for java.
Martin
- Original Message -
From: Hannu Krosing [EMAIL PROTECTED]
To: Martin Matusiak [EMAIL PROTECTED]
Cc: [EMAIL
Have you read the README file in storage/lmgr/README?
---
Sumaira Ali wrote:
[ text/html is unsupported, treating like TEXT/PLAIN ]
htmldiv style='background-color:'DIVhi, does anyone know what lockmethod means
in the
My 3rd attempt to post ...
Consider this query on a large table with lots of different IDs:
SELECT id FROM my_table GROUP BY id ORDER BY count(id) LIMIT 10;
It has an index on id. Obviously, the index helps to evaluate count(id)
for a given value of id, but count()s for all the `id's
Tom Lane wrote:
Curt Sampson [EMAIL PROTECTED] writes:
On Mon, 17 Feb 2003, Tom Lane wrote:
Postgres has a bad habit of becoming very confused if the page header of
a page on disk has become corrupted.
What typically causes this corruption?
Well, I'd like to know that too. I have
Added to TODO:
* Allow WAL information to recover corrupted pg_controldata
---
Curt Sampson wrote:
On Fri, 14 Feb 2003, Bruce Momjian wrote:
Is there a TODO here, like Allow recovery from corrupt pg_control
52 matches
Mail list logo
