> > Personally I'd rather take out the =NULL conversion anyway...
>
> I'd second that.
Ok, from my yesterday's mistake, and mails that M$ doesn't support it
eighter you convinced me. If this was a vote, I would also now vote
for removing it.
Andreas
---(end of broadc
I have seen problems with extremely many concurrent users.
I run pgbench:
pgbench -c 1000 -t 1 test
And I get stuck spin lock errors. This is 100% reproducable (i.e. I
have nerver succeeded in pgbench -c 1000).
This is Linux kernel 2.2.18. Followings are some resource settings
that seem crytica
> > What about a KDE or Gnome piece of software? In
> > fact, I believe that such a
> > project may already be in its infancy...
>
> Yes, I could be, but no all systems have one of them
> installed or even installable (think not only about
> Linux, but all the platforms in wich Postgres run,
>
Michael Meskes wrote:
On Wed, Jun 20, 2001 at 09:13:13AM +0200, Pedro Abelleira Seco wrote:
- Phppgadmin is a web based tool. You need a PHPenabled web server. Most end users/admins don't wantto have to configure a web server, PHP ("what isPHP?") and to have a poor interface (I'm talking about
On Wed, Jun 20, 2001 at 09:13:13AM +0200, Pedro Abelleira Seco wrote:
> To say it briefly if an average IT manager asks you to
> "show him PostgreSQL" and you open pgsql or pgaccess
> you are done. Sad but true.
>
Well, then open Access. What do you do when the same manager wants to
see your web
Hmm, your using ColdFusion, so that goes through the ODBC driver, which
picks up the 'primary key' by looking for an index named 'foo_pkey',
I think. Ah, here it is:
in interfaces/odbc/info.c:
sprintf(tables_query, "select ta.attname, ia.attnum"
" from pg_attribute ta, pg_attribute ia,
> Problem can be demonstrated by following example
>
> create table a (a numeric primary key);
> insert into a values (1);
> insert into a values (2);
> insert into a values (3);
> insert into a values (4);
> update a set a=a+1 where a>2;
> ERROR: Cannot insert a duplicate key into unique index
> I think that application people would probably prefer the delete trigger,
> insert trigger. It makes more sense, because I would interpret replace
> as "get rid of the old if it exists" and "put in a new item". If people
> wanted
> to make sure code is run on delete, and they have to put it in
> > update a set a=a+1 where a>2;
> > ERROR: Cannot insert a duplicate key into unique index a_pkey
>
> This is a known problem with unique contraints, but it's not
> easy to fix it.
Yes, it requires dirty reads.
Vadim
---(end of broadcast)---
T
Okay, what I'm thinking is to have a pair of commands added to PL/pgSQL. For
the sake of example we'll call them:
ENABLE PRIVLEDGE --> Sets user ID to that of the function's owner
DISABLE PRIVLEDGE --> Restores the original UID
I saw something like this being used in the referential integrity c
> > > update a set a=a+1 where a>2;
> > > ERROR: Cannot insert a duplicate key into unique index a_pkey
> >
> > We use uniq index for UK/PK but shouldn't. Jan?
>
> What else can you use than an index? A "deferred until
> statement end" trigger checking for duplicates? Think it'
At 13:41 20/06/01 -0700, Naomi Walker wrote:
>
>Well, so now there is at least TWO of us
>
>We should start the thread again.
>
WAL based backup & recovery is something I have been trying to do in
background, but unfortunately I have no time at the moment. I do plan to
get back to it as soon
On Thu, Jun 21, 2001 at 09:44:43AM +0800, Christopher Kings-Lynne wrote:
> > Okay, what I'm thinking is to have a pair of commands added to
> > PL/pgSQL. For
> > the sake of example we'll call them:
> >
> > ENABLE PRIVLEDGE --> Sets user ID to that of the function's owner
> > DISABLE PRIVLEDGE
"Olivier Haies" <[EMAIL PROTECTED]> writes:
> I'm using version 6.5.2 of PostgreSQL
Time to update... 7.1.2 is current...
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PRO
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I think there will be a race condition around the time of a database
> shutdown. After a new child process is created, the system may go into
> shutdown mode. However, there is a window where the child won't know
> this, because the signal is blocke
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> How far off is 7.2? Ages?
Hopefully not. I'd like to see us get back on a reasonably short
release cycle, like every six months or less --- the last couple
major release cycles have been painfully long.
So, maybe beta around Aug-Sep?
Not
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Thomas Lockhart writes:
>> SQL9x "timestamp" has no notion of time zones. PostgreSQL "timestamp"
>> does.
> AFAICT, it does not. The value is stored in UTC (more or less) and is
> converted to the local time zone for display. But a data type is def
On Thu, 21 Jun 2001, Tom Lane wrote:
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > How far off is 7.2? Ages?
>
> Hopefully not. I'd like to see us get back on a reasonably short
> release cycle, like every six months or less --- the last couple
> major release cycles have been pai
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I have seen problems with extremely many concurrent users.
> I run pgbench:
> pgbench -c 1000 -t 1 test
> And I get stuck spin lock errors. This is 100% reproducable (i.e. I
> have nerver succeeded in pgbench -c 1000).
Is it actually stuck, or just tim
19 matches
Mail list logo
