Luke Lonergan wrote:
Tom,
... and instead, define some new behavior that will soon be considered
broken legacy code itself?
I'll not argue further about whether to have a separate LOAD command.
That's not as important as fixing the performance issues in the data load
path in
Patch applied. Thanks for the COPY \x patch.
---
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Here is a new version of the three \x hex support patches. I have added
\x for
Bruce,
Yep, you have to double backslahses coming in as data so we can use
backslash for marking null, delimiters, etc. I see no way around that,
and no one since Berkeley has come up with one either. If you have an
idea, we would _love_ to hear it.
Apropos to the previous thread on escape
Yep, we would _love_ those improvements.
Coming soon, probably from the guy you've never heard of :-)
I am confused why you are confused. :-)
Uh, how do you do the escapes if you don't double the escape character
on input so you can distinguish a literal escape from one use to mark
Magnus Hagander [EMAIL PROTECTED]
Why not just use the pid in teh name, and have one segment
per backend?
Being used only for signals you mean? That might work.
That was my idea. We'll end up using three global namespace objects
(mutex+event+shared memory) instead of one (named
Luke Lonergan wrote:
I propose an extended syntax to COPY with a change in semantics to remove
the default of WITH ESCAPE '\'.
Er, doesn't this break existing database dumps?
-O
---(end of broadcast)---
TIP 3: if posting/reading through
Luke Lonergan wrote:
Yep, we would _love_ those improvements.
Coming soon, probably from the guy you've never heard of :-)
LOL
I am confused why you are confused. :-)
Uh, how do you do the escapes if you don't double the escape character
on input so you can distinguish
Oliver Jowett wrote:
Luke Lonergan wrote:
I propose an extended syntax to COPY with a change in semantics to remove
the default of WITH ESCAPE '\'.
Er, doesn't this break existing database dumps?
Right, we will not change the default.
--
Bruce Momjian|
Oliver,
On 6/1/05 7:13 PM, Oliver Jowett [EMAIL PROTECTED] wrote:
Luke Lonergan wrote:
I propose an extended syntax to COPY with a change in semantics to remove
the default of WITH ESCAPE '\'.
Er, doesn't this break existing database dumps?
Yes, one of the previously stated reasons to
How do you distinguis an escape-delimiter used to escape a delimiter in
the data from a literal escape-delimiter in the data being loaded --- it
seems impossible to do.
The usual approach is fine - a pair of escapes is equivalent to a literal
escape.
Or are you saying there would be no
On Wed, Jun 01, 2005 at 07:35:33PM -0700, Luke Lonergan wrote:
I propose an extended syntax to COPY with a change in semantics to remove
the default of WITH ESCAPE '\'.
Er, doesn't this break existing database dumps?
Yes, one of the previously stated reasons to create another command
Is there any reason we can't have SELECT FOR UPDATE on union ALL queries?
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Wed, Jun 01, 2005 at 10:35:30AM -0700, Alon Goldshuv wrote:
2) A modified command syntax for introducing a direct single row error
handling. By direct I mean - a row that if rejected from within the COPY
command context does not throw an error and rollsback the whole transaction.
Instead
Steve,
I've been following this thread, and I'm a little confused. Could you
possibly clarify what you mean, by providing a couple of lines of
input as it would be formatted with escape processing turned off -
containing a text field with an embedded newline and tab and a null field.
Using
yeah, this is all a bit confusing, but I *hope* I can clarify things here as I
think I got a better understanding now.
before that, let me just clarify that the performance improvements in the patch
have nothing to do with the escaping mechanizm. Escapes could change. The
performance gain in
I've been following this thread, and I'm a little confused. Could you
possibly clarify what you mean, by providing a couple of lines of
input as it would be formatted with escape processing turned off -
containing a text field with an embedded newline and tab and a null field.
yeah, this is all
Steve,
Oops. Example below should have read differently:
Sample with 2 identical rows (with binary representations depicted between
):
Blahblah0xaablahblah0x09blahblah0x00blahblah0xaaBlahblah0xaablahbl
ah0x09blahblah0x00blahblah0xaa
On Thu, Jun 02, 2005 at 12:30:01AM -0400, Alon Goldshuv wrote:
before that, let me just clarify that the performance improvements in
the patch have nothing to do with the escaping mechanizm. Escapes
could change. The performance gain in due to a buffered processing
with minimal line/attribute
101 - 118 of 118 matches
Mail list logo
