Bruce,
Attached patch replaces the original, applied today against CVS HEAD.
Fixes the surrogates, and limits to 4 byte utf8 as per spec.
Also extends UtfToLocal to 4 byte characters (tho, it does not add any,
just enables the code to handle them. If my interpretation of this code
is wrong, pleas
Bruce Momjian writes:
> I suppose no one would like adding an option to turn off locking during
> COPY, so the non-WAL logging would become the default?
When and if we add LOCK or some equivalent option to COPY, I'm sure
we'll change pg_dump to specify that option in its output. But trying
to ge
What would be absolutely ideal is a reset connection command, plus some
way of knowing via the protocol if it's needed or not.
Chris
Bruce Momjian wrote:
What did we decide on RESET CONNECTION. Do we want an SQL command or
something only the protocol can do?
-
Now that I look, it doesn't look like these operators are documented
at all in the SGML docs, so it sure seems that removing them should be
pretty painless.
I'd agree with that
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmas
Well, that's clear evidence that the only way we are going to be able to
SIGTERM a backend is it does a query cancel first, then terminates. I
don't think anything else is going to work cleanly.
---
Rod Taylor wrote:
> > >
Yes, I assume that the patch to group the writes isn't something we want
right now, and the one for O_DIRECT is going to need an additional
fsync, and I have asked for testing on that.
I have posted a patch that I think fixes the memory leak reported and am
waiting for feedback on that.
> > Exactly. In theory it probably works fine to allow one backend to exit
> > via kill -TERM, but it cannot be claimed that that behavior has been
> > tested to any significant extent --- "fast" shutdown is not stressing it
> > in the same way.
> >
> > I think this is largely a question of someon
Later version of this patch added to the patch queue.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
-
What did we decide on RESET CONNECTION. Do we want an SQL command or
something only the protocol can do?
---
Oliver Jowett wrote:
> (cc'ing -hackers)
>
> Karel Zak wrote:
>
> > I think command status is common and nice fe
It would be nice to add the current sequence value to \ds, but the
existing psql query would have to be overhauled to do that. Right now
the same query does all the work for most \d commands.
---
Gevik Babakhani wrote:
> De
I have added this thread as a link on the TODO list under TODO.detail.
I know folks are working on this for 8.1 but now they can get the
discussions all in one place.
---
Heikki Linnakangas wrote:
> I've been very slowly co
I do like this idea. Can you make a general patch? Do others like the
idea of system tables showing error codes and keywords?
---
David Fetter wrote:
> On Mon, Nov 01, 2004 at 12:49:47AM +0100, Gaetano Mendola wrote:
> > J
Neil Conway wrote:
> Bruce Momjian wrote:
> > Well, it isn't going to help us for 8.1 because 8.0 will not have it,
> > and if we add the clause we make loading the data into previous releases
> > harder.
>
> pg_dump output in general is not compatible with prior releases. It
> would be a nice fe
This thread has been added as a link on the TODO list under TODO.detail.
---
Dennis Bjorklund wrote:
> I've made a partial implementation of a datatype "timestamp with time
> zone" as described in the sql standard. The curre
On Sat, 4 Jun 2005, Bruce Momjian wrote:
> Date: Sat, 4 Jun 2005 19:33:40 -0400 (EDT)
>
> I have added a link to this thread on the TODO list under TODO.detail.
Thanks Bruce (and Josh Berkus) for reminding me about this. I should be
able to follow this up in early July.
-s
> Serguei A. Mokhov w
I have added a link to this thread on the TODO list under TODO.detail.
---
Serguei A. Mokhov wrote:
> Hello dear all,
>
> [Please CC your replies to me as I am on the digest mode]
>
> Here's finally a very high-level desig
This has already been implemented in CVS as a psql \set variable:
ON_ERROR_ROLLBACK = 'interactive'
and will appear in 8.1.
---
Michael Paesold wrote:
> Tom Lane wrote:
>
> > "Michael Paesold" <[EMAIL PROTECTED]>
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Ri
Dear all,
The PostgreSQL Developer Network’s Source Browser (beta1)
is ready.
If you got the time to check it for a moment, please do not
hesitate to send your opinion.
Regards,
Gevik
PGDN can be found at http://www.truesoftware.net/pgdn/
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> On Jun 5, 2005, at 12:55 AM, Tom Lane wrote:
>> Now that I look, it doesn't look like these operators are documented
>> at all in the SGML docs, so it sure seems that removing them should be
>> pretty painless.
> I wonder what else is lurking around
Qingqing Zhou <[EMAIL PROTECTED]> writes:
> How do we force the dependency according to pg_dependency records? Seems
> pg_dependency just records them and we follow the records by hand on
> create or delete ...
Deletion scans the entries and either deletes the dependent objects or
raises error. I
On Jun 5, 2005, at 12:55 AM, Tom Lane wrote:
Now that I look, it doesn't look like these operators are documented
at all in the SGML docs, so it sure seems that removing them should be
pretty painless.
I wonder what else is lurking around undocumented and unused? Might
be some other nuggets
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> I don't even grasp what unary modulo actually means???
At some point in the dim mists of prehistory, somebody thought it would
be cute to define prefix % as trunc() and postfix % as round(). I'm not
aware of any precedent for that; it was prob
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes:
>> A run-length compressor would be reasonably quick but I think that the
>> omit-the-middle-hole approach gets most of the possible win with even
>> less work.
> I can't think that a RLE scheme would be much more expensive than a 'count
> the hole' a
round() and trunc() also have the virtue that they already have versions
for type numeric. If we keep the operators then we'll be right back
with the complaint that was lodged the other day about exponentiation,
namely unexpected precision loss for numeric inputs:
regression=# select 12345678901
Tom Lane wrote:
> We could possibly fix this by fooling with the precedence of the
> productions for postfix '%', but I'm worried that that would have
> unintended side-effects. What I'd like to propose instead is that
> we remove prefix and postfix '%' entirely --- and also '^', which
> is the on
I wrote:
> Bruce Momjian writes:
>> Does anyone understand why the precedence of % is strange:
>> test=> select -25 % -10;
> It's treating it as ((-25) %) - (10), which is probably not so
> surprising given the relative precedence of % and - ... though
> I have to admit I'm not totally clear why
How do we force the dependency according to pg_dependency records? Seems
pg_dependency just records them and we follow the records by hand on
create or delete ...
Regards,
Qingqing
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Try the PL/sh project on www.pgfoundry.org.
Chris
Gevik babakhani wrote:
Dear people,
Does anyone know how to execute an OS command from pgsql. I would like
to create a trigger that op on firing would run/execute an external
program.
Does such functionality exist or do I have to writ
Gevik babakhani wrote:
Dear people,
Does anyone know how to execute an OS command from pgsql. I would like
to create a trigger that op on firing would run/execute an external program.
Does such functionality exist or do I have to write my own trigger
function in C.
Reagrds,
Gevik.
30 matches
Mail list logo
