Hi all,
We have the following:
template1=# create tablespace blah location '/home/swm/tbl/tspc1/';
CREATE TABLESPACE
template1=# create table foo (i int) tablespace blah;
CREATE TABLE
template1=# create database foo tablespace blah;
ERROR: could not initialize database directory
DETAIL: Directo
There is a confusing bug in tablespaces. Here is examples:
OK, let's create a table with the 3 possible tablespaces of indexes:
test=# create table test(a int4) tablespace loc;
CREATE TABLE
test=# create unique index test_a_idx on test(a);
CREATE INDEX
test=# create unique index test_a_idx2 on tes
chinni <[EMAIL PROTECTED]> writes:
> Did you guys debate on merging it.
Yes.
If it were actually synced with our current CVS and potentially
mergeable, the debate might have been longer :-(. But in point of fact,
postgres-R has never been less than two releases behind in the past five
years, and
On 26 Jul, To: [EMAIL PROTECTED] wrote:
> Sorry I wasn't clearer. I think I have a better idea about what's going
> on now. With the archiving enabled, it looks like the database is able
> to complete 1 transaction per database connection, but doesn't complete
> any subsequent transactions. I'm n
Bruce Momjian <[EMAIL PROTECTED]> writes:
> If we get savepoints working inside functions, would they work if the
> function is not called from a multi-statement transaction?
We'll make sure they do ;-)
regards, tom lane
---(end of broadcast)--
Bruce Momjian <[EMAIL PROTECTED]> writes:
>>> If we get savepoints working inside functions, would they work if the
>>> function is not called from a multi-statement transaction?
>>
>> We'll make sure they do ;-)
> That will be a neat trick because it will become a multi-statement
> transaction w
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > If we get savepoints working inside functions, would they work if the
> > function is not called from a multi-statement transaction?
>
> We'll make sure they do ;-)
That will be a neat trick because it will become a multi-statement
t
On Wed, Jul 28, 2004 at 10:14:33AM +0800, Christopher Kings-Lynne wrote:
> I got no mail from any of the PostgreSQL lists this morning. That's not
> right. Did this mail get through?
Apparently everyone is at OSCON or something ... the rest of the people
was left out because the NNTP server was
all fixed ... had a kernel panic this morning, and fsck took a while to
run ...
On Wed, 28 Jul 2004, Christopher Kings-Lynne wrote:
I got no mail from any of the PostgreSQL lists this morning. That's not
right. Did this mail get through?
Chris
---(end of broadcast)
I got no mail from any of the PostgreSQL lists this morning. That's not
right. Did this mail get through?
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere
If we get savepoints working inside functions, would they work if the
function is not called from a multi-statement transaction?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Ro
On Mon, Jul 26, 2004 at 10:06:28PM -0400, [EMAIL PROTECTED] wrote:
> So what you are saying is that you should inconvenience 90% of your users
> to make sure they do something "right?"
I would say that was pretty solid reasoning. Exposing 10% of users to a
high data corruption risk just to get
Oliver Jowett wrote:
I suppose so. I'd point out that the NIO byteorder info is really just
an optimization hint -- the rest of the NIO API is byteorder agnostic,
regardless of what the native byteorder is.
The rest of the NIO API is not agnostic. A java.nio.ByteBuffer is big
endian by default
Thomas Hallgren wrote:
"Oliver Jowett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
NIO is not present before JDK 1.4. The JDBC driver, at least, needs to
support earlier JVMs.
Clients only capable of network order (such as a Java 1.3 based JDBC driver)
must of course be supported st
"Oliver Jowett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> NIO is not present before JDK 1.4. The JDBC driver, at least, needs to
> support earlier JVMs.
>
Clients only capable of network order (such as a Java 1.3 based JDBC driver)
must of course be supported still. No argument
See http://www.slony.org/
It's a master-multislave replication system that has a pretty robust
development cycle. It just reached a 1.0 release.
Whether any solution becomes a core part of the distribution remains, I
think, to be seen.
-tfo
On Jul 27, 2004, at 4:03 AM, chinni wrote:
Postg
Postgres-R is a multi server (write anywhere) replication tool
which is possibly important for any enterprise if they want to shift
to postgres.
Did you guys debate on merging it.
As of now They are working on postgres 7.2 and developing postgres-R.
They plan to do it for 7.4 as well, why n
Hello,
I've got some strange vacuum full behaviour. I've got a table:
flows=# explain select * from data;
QUERY PLAN
---
Seq Scan on data (cost=0.00..5045547.76 rows=236174576 width=55) (1 row)
That i
Thomas Hallgren wrote:
Oliver Jowett wrote:
> This is not true if you happen to be using Java on the client side,
> which has no idea (unless you grot around in the guts of the JVM) what
> the native byte order is.
>
The method java.nio.ByteOrder.nativeOrder() will tell you what the
native byt
19 matches
Mail list logo
