On Sunday 29 August 2004 18:29, Greg Sabino Mullane wrote:
>
> > On the ordering issues, I'd go for straight alphabetical schema/name
> > sort in all cases; I thought that's where we were already, but if you
> > see some missing cases let's fix it. I'm not enamored of discriminating
> > against sy
This has just been fixed by Tom and will be in beta2.
---
Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > As for extending the length of xl_len, what happens if someone now has
> > 2^30 subtransaction IDs (as
ok, will look at it in the morning.
-- Original Message ---
From: Tom Lane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: "pgsql-hackers" <[EMAIL PROTECTED]>
Sent: Sun, 29 Aug 2004 21:42:57 -0400
Subject: Re: [HACKERS] beta 1 failed on linux mipsel
> "Jim Buttafuoco" <[EMAIL PR
"Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> Shouldn't this also work on mipsel CPU's?
It should work on a real MIPS CPU. The PlayStation 2 has a dumbed-down
MIPS chip without the TAS instruction :-(, but now that we've eliminated
that point I think you've found a problem. We made several
reor
The system is a cobalt raq, I am also going to test on some decstations (also mipsel)
and SGI (mips) systems.
I didn't use the disable-spinlock option. will try tomorrow. i did see some mips
spinlock code in s_lock.c.
Shouldn't this also work on mipsel CPU's?
Jim
-- Original Mess
Mike Rylander <[EMAIL PROTECTED]> writes:
> Will we be looking at a re-initdb with beta2?
At this point, no initdb, but you will need to be prepared to reset the
xlog if you don't want to initdb. In short:
1. clean shutdown of old postmaster.
2. install new executables.
3
Tom Lane wrote:
> Just so you know --- core has agreed that it's about time for beta2.
> If you've got any "must fix" issues, please get 'em in over the weekend.
Will we be looking at a re-initdb with beta2? I didn't notice any changes
that would force it, but just to be clear...
>
> regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I find this quite ugly, and don't think it's a good change. Anyone
> who's fool enough to use trailing spaces in column names deserves the
> pain it will cost them --- and there is no other case in which the
> unquoted display is ambiguous.
I
Richard van den Berg <[EMAIL PROTECTED]> writes:
> My problem is this: we have ODBC users working from home, so they cannot use
> SSL unless we buy the commercial drivers. We decided that encrypting the data
> is not required, but we do need to strictly protect access to our database.
You could a
"Jim Buttafuoco" <[EMAIL PROTECTED]> writes:
> trying to test beta 1 on Debian linux mipsel (sarge).
What is that, a playstation 2? Last we heard, that chip had no spinlock
support. Did you use configure --disable-spinlocks?
regards, tom lane
---
Hi all,
today I tried this tool:
http://www-106.ibm.com/developerworks/linux/library/l-ccache.html
and the second full compilation, after a make clean
took: 47 seconds. Amazing.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9'
Mohawksoft,
> Actually that are not involved with transactions in any way.
>
> There classes of problems in which proper ACID implementation is not
> nessisary. In fact, there are subclasses within a larger system that need
> not have the overhead imposed by transactions.
Hmmm, wait, are you impl
trying to test beta 1 on Debian linux mipsel (sarge). I am getting the following
error "PANIC: stuck spinlock
(0x2b052030) detected at lwlock.c:246" during initdb. here is the complete initdb run.
[EMAIL PROTECTED]:~$ initdb
The files belonging to this database system will be owned by user "p
On Sun, Aug 29, 2004 at 09:24:59AM -0400, [EMAIL PROTECTED] wrote:
> Think about a website shopping cart. The session and the things in the
> cart don't matter after 10 or 15 minutes. Most of the time, it will just
> be abandoned. The only time it is important is at checkout. At which point
> it i
Tom Lane wrote:
"Maurizio Merli" <[EMAIL PROTECTED]> writes:
I'm using PostgreSQL 8.0.0 beta1
On what?
md5.o(.text+0x1ee):md5.c: undefined reference to `bcopy'
I've fixed these by changing to the more-standard memmove() routine.
crypt-des.o(.text+0x520):crypt-des.c: undefined reference to [EMAI
>> md5.o(.text+0x1ee):md5.c: undefined reference to `bcopy'
>
>I've fixed these by changing to the more-standard memmove() routine.
>
>> crypt-des.o(.text+0x520):crypt-des.c: undefined reference to
>[EMAIL PROTECTED]'
>> crypt-des.o(.text+0xbbe):crypt-des.c: undefined reference to
>[EMAIL PROTECT
"Maurizio Merli" <[EMAIL PROTECTED]> writes:
> I'm using PostgreSQL 8.0.0 beta1
On what?
> md5.o(.text+0x1ee):md5.c: undefined reference to `bcopy'
I've fixed these by changing to the more-standard memmove() routine.
> crypt-des.o(.text+0x520):crypt-des.c: undefined reference to [EMAIL PROTECTE
Greg Stark wrote:
I expect to see substantial resistance to incorporating such a feature. One
argument will be that he should simply use a separate system for such data.
For example, memcached would be much faster and more scalable than
communicating via postgres.
Postgres should do what postgr
After a long battle with technology, [EMAIL PROTECTED] (Andrew Dunstan), an earthling,
wrote:
> Bruce Momjian wrote:
>
>>I have shortened your paragraph to:
>>
>>Because Win32 is significantly different from the Unix platforms
>>supported in previous releases, this port might have
I'm sorry to bring this up again. From the archives I found that the
current md5 authentication scheme of postgres was designed in 2001. I
found a debate about it's security from 2002.
http://archives.postgresql.org/pgsql-hackers/2001-06/msg00511.php
http://archives.postgresql.org/pgsql-hackers/2
I'm using PostgreSQL 8.0.0 beta1
I can compile all contrib modules but pgcrypton
i have this error when I execute make
md5.o(.text+0x1ee):md5.c: undefined reference to `bcopy'
md5.o(.text+0x25c):md5.c: undefined reference to `bcopy'
md5.o(.text+0x2ae):md5.c: undefined reference to `bcopy'
md5.o
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Wed, Aug 25, 2004 at 11:21:49AM +1000, Gavin Sherry wrote:
>> On Tue, 24 Aug 2004, Tom Lane wrote:
>>> Or we could assign an rmgr value to represent an "extension" record that
>>> is to be merged with a following "normal" record. This is kinda klugy
Josh Berkus <[EMAIL PROTECTED]> writes:
> Question: How will these "system variables" behave regarding transactions?
> If I update a system variable and roll back the transaction, does it change
> back? Do changes in a running transaction remain invisible until COMMIT?
> Excuse me if you
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> This should be:
> Table "public.Upper Division"
> Column | Type | Modifiers
> --+-+---
> abc | integer |
> " spaced out " | text|
> " real ""Name""" | text|
> "MixedCase"
> On Sat, 28 Aug 2004 [EMAIL PROTECTED] wrote:
>
>>
>>> I don't see how this is different from "CREATE TABLE shared_variables
>>> (name
>>> VARCHAR PRIMARY KEY, value VARCHAR)" and
>>> inserting/updating/deleting/selecting from that. Perhaps these are
>>> per-session shared variables? IN which case
>> I think the shared variable module is another one of those things. The
>> cost overhead of a single variable implemented as a row is too high,
>> especially if you want to update it many times a second.
>
> Question: How will these "system variables" behave regarding
> transactions?
> If I upd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message
>> 1. Do we want to use quote_ident on object names? Ideally, column
>> names with a space in them, for example, should be surrounded by
>> double quotes.
> Example of it failing? You mean li
27 matches
Mail list logo
