Hi,
in Czech database conference we talk about windows PostgreSQL port and
windows encodings now. The current code expect use win1250 as FE
encoding only. That's right for non-windows systems, but native windows
knows work with this encoding. The encodings separation (FE|BE) is
On Thu, 2004-07-08 at 07:57, [EMAIL PROTECTED] wrote:
On Thu, 8 Jul 2004, Simon Riggs wrote:
We don't need to mention timelines in the docs, nor do we need to alter
pg_controldata to display it...just a comment in the code to explain why
we add a large number to the LogId after each
On Wed, Jul 07, 2004 at 12:39:34PM +0200, Yannick Lecaillez wrote:
Thanks a lot for all people which answer.
I have this clustering on SAN problem today and i think it could be
less harder to implement this today than it was for Oracle in 1993
You want to do clustering for
I've discovered that CREATE DATABASE doesn't redo correctly in an
archive recovery test.
This isn't a bug --in the current code--, because when crash recovery
occurs, the database directories are already there, so this only doesn't
work when using the PITR patches. During archive recovery,
On Thu, Jul 08, 2004 at 02:58:01PM +0100, Simon Riggs wrote:
I've discovered that CREATE DATABASE doesn't redo correctly in an
archive recovery test.
This isn't a bug --in the current code--, because when crash recovery
occurs, the database directories are already there, so this only
On Thursday 01 July 2004 09:26 pm, Scott Marlowe wrote:
On Thu, 2004-07-01 at 18:54, Gavin Sherry wrote:
On Thu, 1 Jul 2004, Mike Rylander wrote:
On Thursday 01 July 2004 06:43 pm, Gavin Sherry wrote:
Hi Mike,
In this release, unfortunately not.
That't too bad, but it's not
After reproducing these crashes and running tests long enough, we found
that these Postgres Crashes happen on linux 2.4.18 and not on linux
2.4.25. In all likelihood, this is a kernel (or driver) issue.
Could you kindly ensure this gets on my mail thread with subject Postgres
Crashes.
Thanks
As a result of the constraint output functions being shared between
pg_dump and psql, some of the output is mis-quoted in the display area
for columns including quotes. Notice it's correct in the table Column
list, but the constraint has the escaped versions.
Thoughts?
rt=# create table c
On Thursday 01 July 2004 08:54 pm, Gavin Sherry wrote:
On Thu, 1 Jul 2004, Mike Rylander wrote:
On Thursday 01 July 2004 06:43 pm, Gavin Sherry wrote:
Hi Mike,
In this release, unfortunately not.
That't too bad, but it's not that urgent I suppose.
I had some idea early on of
Hi
i have an orderedtable of dates let's
say:
1/1/2004
8/1/2004
15/1/2004
29/1/2004
5/2/2004
12/2/2004
I am searching for a way to have the minimum date
and maximum date for dates seperated byone week whitout gaps between them
in a string.
which will give the
followingoutput:
On Thu, 2004-07-08 at 16:19, Alvaro Herrera wrote:
On Thu, Jul 08, 2004 at 02:58:01PM +0100, Simon Riggs wrote:
I've discovered that CREATE DATABASE doesn't redo correctly in an
archive recovery test.
This isn't a bug --in the current code--, because when crash recovery
occurs, the
Alvaro, Hackers:
I've been giving this some thought. Here's what I came up with:
We should NOT use the savepoint syntax. Alvaro's Nested Transactions are not
savepoints, they don't meet the spec, and they don't behave the same. Using
standard syntax for a non-standard feature will, in my
On Thu, Jul 08, 2004 at 06:33:56PM +0100, Simon Riggs wrote:
On Thu, 2004-07-08 at 16:19, Alvaro Herrera wrote:
On Thu, Jul 08, 2004 at 02:58:01PM +0100, Simon Riggs wrote:
The correct solution would be to emit a XLog record for CREATE
DATABASE ...
I'd prefer a formal approach, hence
On Thu, Jul 08, 2004 at 03:28:12PM -0400, Andrew Dunstan wrote:
I will be away from the 9th to the 16th or 17th of July, and will
have no net access during that time. I'm hoping that in the meantime
other interested people will pick up the remaining tasks (docs,
I've got some preliminary
[Note: my ISP is having problems with email, so probably a duplicate
of this will be published as soon as their SMTP starts working again]
There's a point that hasn't been raised in discussion of subtransactions
here and it's what to do when a function aborts.
If I have a plpgsql function that
Alvaro,
My proposal would be:
1. Begin main transaction: BEGIN { TRANSACTION | WORK }
2. Commit main (all) transaction: COMMIT { TRANSACTION | WORK }
3. Rollback main (all) transaction: ROLLBACK { TRANSACTION }
4. Begin inner transaction: BEGIN NESTED { TRANSACTION | WORK }
5. Commit inner
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Magnus Hagander
Sent: 06 July 2004 21:46
Cc: [EMAIL PROTECTED]
Subject: [HACKERS] Initdb error
Hi!
I'm getting this error whenever I try to change the superuser of my
database to anything
create function crashme2() returns int strict language plpgsql as '
begin
subbegin;
select foo; -- aborts the transaction
-- did not close the subxact
end;';
I'm not sure I follow. Are you saying that the following code or
something similar will
On Thu, Jul 08, 2004 at 04:52:04PM -0400, Rod Taylor wrote:
create function crashme2() returns int strict language plpgsql as '
begin
subbegin;
select foo; -- aborts the transaction
-- did not close the subxact
end;';
I'm not sure I follow.
All,
Out of necessity, I've implemented user quotas in 7.4.3. What would the
process be for having this reviewed and combined? I have a patch for
7.4.3 ready, but wanted to know if you suggest that I patch the latest
cvs instead. Below if some information on the implementation.
Some sort of modification will be needed to the error processing
mechanism, but this is beyond me at this point ... I don't have any
idea how could this be.
So.. If you cannot rollback a subtransaction within a plpgsql function
(all function types or just that one?) then there is no point is
Alvaro Herrera wrote:
On Thu, Jul 08, 2004 at 10:40:36AM -0700, Josh Berkus wrote:
This means that we CANNOT maintain compatibility with other databases without
supporting SAVEPOINT syntax, which we are not yet ready to do. As a result,
I would propose the following syntax:
Begin
Hi. I want to begin helping develop postgresql.
I have an up-to-date computer, a dell dimension 4600, built with lots of extras. I have an MS in CS, and have worked with postgres in industry.
Can someone tell me what software I need? I guess I need a compiler. What compiler do I need? What else
Title: Message
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of robert kernellSent: Thursday, July 08, 2004
4:23 PMTo: [EMAIL PROTECTED]Subject:
[HACKERS] Want to Contribute
Hi. I want to begin helping develop postgresql.
I have
docs?
--- Trend GateLock [EMAIL PROTECTED] (higp7.gatelock.com.tw)
** friend_incest.pif
Trend GateLock [EMAIL PROTECTED] (higp7.gatelock.com.tw)
** friend_incest.pif WORM_NETSKY.C
As a result of the constraint output functions being shared between
pg_dump and psql, some of the output is mis-quoted in the display area
for columns including quotes. Notice it's correct in the table Column
list, but the constraint has the escaped versions.
It's misquoted because psql DOES NOT
How come I default to Antartica in CVS?
test=# show time zone;
TimeZone
--
Antarctica/Casey
(1 row)
test=#
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
27 matches
Mail list logo
