On Oct 28, 2007, at 2:54 PM, Josh Berkus wrote:
I'd actually be curious what incremental changes you could see
making to
PostgreSQL for better in-memory operation. Ideas?
It would be difficult to make PostgreSQL really competitive for in-
memory operation, primarily because a contrary
I created one function which updates a table using updatable cursor. I wrote
one trigger also on the same table. When i execute the function it gives
expected results. But after that all DMLs fail.
CREATE TABLE test(i int, j int);
Drop trigger test_trig;
INSERT INTO test VALUES(1, 100);
INSERT
Hi,
I went through the mailing list and couldn't get answer to the question.
a) Is there a proposal in place for going back in time within a transaction?
--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Groups.
(www.alliedgroups.com)
This is the complete question.
Hi,
I went through the mailing list and couldn't get answer to the question.
a) Is there a proposal in place for going back in time within a transaction?
I am thinking of some functionality like this.
BEGIN
select ... (command id 1)
update ... (command id 10)
Tom Lane [EMAIL PROTECTED] writes:
Tatsuo Ishii [EMAIL PROTECTED] writes:
Is it possible to use UTF-8 for SGML docs?
No :-(. We've been through this already, see discussions awhile back
about spelling non-English names correctly. Unless there's a recognized
HTML entity for the character,
Gregory Stark [EMAIL PROTECTED] writes:
No :-(. We've been through this already, see discussions awhile back
about spelling non-English names correctly. Unless there's a recognized
HTML entity for the character, you can't use it.
Are entities like #x3041; ok?
No. See prior thread.
On 10/31/07, Gokulakannan Somasundaram [EMAIL PROTECTED] wrote:
a) Is there a proposal in place for going back in time within a transaction?
Yes, it's called a savepoint :)
b) I know time travel doesn't allow to change the details of the past. But
is it possible to provide an alternative to
Following test case is crashing the postgresql-8.3-beta
create schema st;
CREATE TABLE ST.STUDENT(
STUDENT_ID VARCHAR2(10),
NAME VARCHAR(50) NOT NULL,
NIC CHAR(11),
DOB DATE NOT NULL,
GENDER CHAR(1) NOT NULL,
MAR_STAT CHAR(1) NOT
No i am referring to time travel within a transaction, not outside.
On 10/31/07, Hans-Juergen Schoenig [EMAIL PROTECTED] wrote:
hello ...
i guess there is no formal proposal yet but there are some ideas around
and some major challenges have been discussed already.
i think simon riggs was
Ühel kenal päeval, T, 2007-10-30 kell 09:35, kirjutas David Fetter:
On Tue, Oct 30, 2007 at 02:31:52PM +0100, Gevik Babakhani wrote:
Hi all,
I am working a lot with custom procedures/functions which are
implemented in language sql. At the moment function parameter refs
cannot work
There is only one condition under which this would be useful.
Current Scenario:
BEGIN
Select x into var from inventory where y=const;
update inventory..
some more DMLs.
some select into var2;
if (condition based on var2)
use the var;
END;
here i have to fire the first select query all
Gokulakannan Somasundaram wrote:
a) Is there a proposal in place for going back in time within a transaction?
Within a transaction? No, can't remember one. Doesn't sound very useful.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---(end of
hello ...
i guess there is no formal proposal yet but there are some ideas
around and some major challenges have been discussed already.
i think simon riggs was planning to work on it in the future.
the basic idea here is to have the option to create a snapshot
which then stays in the
Sheikh Amjad wrote:
Following test case is crashing the postgresql-8.3-beta
create schema st;
CREATE TABLE ST.STUDENT(
STUDENT_ID VARCHAR2(10),
NAME VARCHAR(50) NOT NULL,
NIC CHAR(11),
DOB DATE NOT NULL,
GENDER CHAR(1) NOT NULL,
MAR_STAT
I want to unsubscrib me please,
Mensaje citado por Hans-Juergen Schoenig [EMAIL PROTECTED]:
hello ...
i guess there is no formal proposal yet but there are some ideas
around and some major challenges have been discussed already.
i think simon riggs was planning to work on it in the
I wrote:
I was able to reproduce this after replacing those VARCHAR2's with
VARCHAR. I added some debugging elog's (attached), and it looks like
libxml2 is trying xml_pfree a pointer we never gave it in any of the
alloc functions. Log attached, last xml_pfree crashes and it's the first
time
On Oct 31, 2007, at 11:10 , [EMAIL PROTECTED] wrote:
I want to unsubscrib me please,
From the headers of every list message:
List-Archive: http://archives.postgresql.org/pgsql-hackers
List-Help: mailto:[EMAIL PROTECTED]
List-ID: pgsql-hackers.postgresql.org
List-Owner: mailto:[EMAIL
with autovacuum enabled with default settings, cramd.sql is 154M:
[EMAIL PROTECTED]:/pub/back$ time pg_restore -Fc -C -d postgres cramd.sql
real3m43.687s
user0m11.689s
sys 0m0.868s
[EMAIL PROTECTED]:/pub/back$
during restore we see scary things like:
[EMAIL PROTECTED]:~# ps
I know its way too late in the game, sorry, but it's a very small patch...
I was wondering if this could be added to 8.3: it adds the dbsize to \l
in psql.
It looks like this:
List of databases
Name| Owner | Encoding | Dbsize
---+--+--+-
Alvaro Herrera wrote:
Bruce Momjian wrote:
Is this item closed?
No, it isn't. Please add a TODO item about it:
* Prevent long-lived temp tables from causing frozen-Xid advancement
starvation
Thanks. Added to TODO.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
look at the headers on email from the list and it tells you how to
unsubscribe.
[EMAIL PROTECTED] wrote:
I want to unsubscrib me please,
Mensaje citado por Hans-Juergen Schoenig [EMAIL PROTECTED]:
hello ...
i guess there is no formal proposal yet but there are some ideas
around and
andy wrote:
I know its way too late in the game, sorry, but it's a very small patch...
I was wondering if this could be added to 8.3: it adds the dbsize to \l
in psql.
8.3 is many months beyond feature-freeze, so no, that's not likely to
happen.
It looks like this:
List of
I have not forgotten this suggestion. Do have any ideas what such a
list would look like? Examples?
I think we have avoided more details in fear of scaring off coders.
People usually follow our style as they gain experience. Having a hard
list seems like it would be a lot of do's and
Thank you Tom.
After running a create function statement (language sql), the final check
for a column is done in
parse_expr.c:transformColumnRef in case 1. Would this be the correct place
to implement
functionality for a final match?
Regards,
Gevik.
- Original Message -
From: Tom
Dharmendra Goyal [EMAIL PROTECTED] writes:
I created one function which updates a table using updatable cursor. I wrote
one trigger also on the same table. When i execute the function it gives
expected results. But after that all DMLs fail.
The problem is that your trigger function
Andrew Dunstan [EMAIL PROTECTED] writes:
Perhaps both these considerations dictate providing another command or a
special flavor of \l instead of just modifying it?
I've seen no argument made why \l should print this info at all.
regards, tom lane
Heikki Linnakangas [EMAIL PROTECTED] writes:
So my current theory is:
In xmlelement(), we use ExecEvalExpr(), which in turn calls xml_parse.
xml_parse calls xmlCleanupParser(). But when we call ExecEvalExpr(),
we're in the middle of constructing an xml buffer, so calling
andy [EMAIL PROTECTED] writes:
I know its way too late in the game, sorry, but it's a very small patch...
(1) What's the performance impact? I should think that this makes \l orders
of magnitude slower.
(2) Doesn't this render \l entirely nonfunctional for users who don't
have CONNECT
On 11/1/07, Bruce Momjian [EMAIL PROTECTED] wrote:
I have not forgotten this suggestion. Do have any ideas what such a
list would look like? Examples?
Thanks for the reply Bruce.
Code examples, perhaps with good style and bad style versions to
illustrate each point.
In the case of Tom's
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
I know its way too late in the game, sorry, but it's a very small patch...
(1) What's the performance impact? I should think that this makes \l orders
of magnitude slower.
(2) Doesn't this render \l entirely nonfunctional for users who don't
Sorry for top-posting -- challenged reader.
Perhaps a future addition as \L ?
This command doesn't seem to be used and could be documented as being subject
to permissions and slower.
I actually would find this useful, but there are other ways of getting it. But
having the option would be nice
[EMAIL PROTECTED] (Tom Lane) writes:
Andrew Dunstan [EMAIL PROTECTED] writes:
Perhaps both these considerations dictate providing another command or a
special flavor of \l instead of just modifying it?
I've seen no argument made why \l should print this info at all.
Its interesting
Chris Browne wrote:
[EMAIL PROTECTED] (Tom Lane) writes:
Andrew Dunstan [EMAIL PROTECTED] writes:
Perhaps both these considerations dictate providing another command or a
special flavor of \l instead of just modifying it?
I've seen no argument made why \l should print this info at all.
Its
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
I know its way too late in the game, sorry, but it's a very small patch...
(1) What's the performance impact? I should think that this makes \l orders
of magnitude slower.
(2) Doesn't this render \l entirely nonfunctional for users
On 11/1/07, Chris Browne [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Tom Lane) writes:
Andrew Dunstan [EMAIL PROTECTED] writes:
Perhaps both these considerations dictate providing another command or a
special flavor of \l instead of just modifying it?
I've seen no argument made why \l
Brendan Jurd [EMAIL PROTECTED] writes:
I'd find this convenient too. Although \l+ would be more consistent
with the \d series of commands.
Putting it into \l+ would address my gripe about increased execution
time. The permissions angle still bothers me though. AFAIR there are
no psql
36 matches
Mail list logo
