> Also, have we decided if multibyte should be the configure default now?
Not sure.
Anyway I have tested LIKE/REGEX query test using current. The query
executed is:
explain analyze select '000 5089 474e...( 16475
bytes long text containing only 0-9a-z chars) like 'aaa';
and
explain analyz
Hello,
Background:
I am pursuing a MS degree at Christopher Newport University. I'm currently
looking for a subject for my thesis plus I've also got to do a simulated
(scaled down) thesis proposal for class. Since my degree program is applied,
it doesn't necessarily have to be a pure resea
You are definitely inputting ISO 8859-1 characters, not UTF-8. That's
the source of your problem.
> Tatsuo Ishii wrote:
> >
> > > > Are you sure that you put the query in UTF-8 encoding?
> > >
> > > Yes :
> > >
> > > essai=> SHOW CLIENT_ENCODING;
> > > NOTICE: Current client encoding is UNICODE
> > The one thing I can't check is the anoncvs directory. Not sure if that
> > is the same as the CVS directory.
>
> It is the anoncvs server that's broken. The committers don't seem to be
> having any problem with accesses to the primary server. I suspect that
> there's a umask or group-membe
On Tue, 2 Oct 2001, Thomas Lockhart wrote:
> ...
> > Tom, what's missing or out of place? If I can I'll make sure it's there.
> > This morning I noticed a number of things that I thought were there really
> > weren't.
>
> What I was looking for was the place where development docs (built from
>
> Until the dust settles the only two people with write access to either
> the developer or regular website will be Marc and myself. I have enough
> to do trying to get mirroring straight, keep up with changes to the sites,
> etc. that I really don't need anyone messing around. So Bruce, your
>
> > Can someone give me TODO items for this discussion?
>
> What about:
>
> Improve Unicode combined character handling
Done. I can't update the web version because I don't have permission.
Also, have we decided if multibyte should be the configure default now?
--
Bruce Momjian
> Can someone give me TODO items for this discussion?
What about:
Improve Unicode combined character handling
--
Tatsuo Ishii
> > > So, this shows two problems :
> > >
> > > - length() on the server side doesn't handle correctly Unicode [I have
> > > the same result with char_length()], and
...
> Tom, what's missing or out of place? If I can I'll make sure it's there.
> This morning I noticed a number of things that I thought were there really
> weren't.
What I was looking for was the place where development docs (built from
daily snapshots) would go. They used to be underneath dev
> > Here is a stack trace using dbx.
>
> > semop(??, ??, ??) at 0xd02be73c
> > IpcSemaphoreLock(??, ??, ??), line 425 in "ipc.c"
> > LWLockAcquire(??, ??), line 270 in "lwlock.c"
> > LockAcquire(??, ??, ??, ??, ??), line 482 in "lock.c"
>
> This process is waiting to acquire the LockMgr lock. Y
On Mon, 1 Oct 2001, Thomas Lockhart wrote:
> > Vince, can I have write permision to /usr/local/www/www/html/docs on the
> > new web server machine so I can create symbolic links to the files in my
> > home directory?
>
> ??!!
>
> Bruce, what is actually happening here? If we are changing procedur
...
> Well, I'll take responsibility for fixing that, if you want to spread
> the blame ;-). It's my fault that those routines are marked cachable
> to begin with --- I hadn't dug into which datetime types had "current"
> and which didn't, just marked 'em all noncachable on sight.
I'm happy to d
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Hmm. Perhaps the definition for CURRENT_DATE should be recast as a call
> to now() (which happens to return timestamp)
Yes, something like date(now()) might be less subject to breakage as we
monkey around with the semantics of literals and implicit co
> I've been looking at the iscachable changes you committed recently,
> and I think a lot of them need to be adjusted still.
Sure. Me too ;)
I changed some for the areas within which I was working, and it did
occur to me that (as you mention below) anything affected as a side
effect of some othe
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> From postmaster startup, by default, could we try larger amounts of
> buffer memory until it fails then back off and allocate that? Seems
> like a nice default to me.
So performance would vary depending on the amount of shared memory
that could be all
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The one thing I can't check is the anoncvs directory. Not sure if that
> is the same as the CVS directory.
It is the anoncvs server that's broken. The committers don't seem to be
having any problem with accesses to the primary server. I suspect that
> > But what about BEFORE insert/update triggers which could
> > insert records too?
>
> Well, what about them? It's already possible for a later
> BEFORE trigger to cause the actual insertion to be suppressed,
> so I don't see any difference from what we have now.
> If a BEFORE trigger takes ac
>> ERROR: operator class "timestamp_ops" does not accept data type
>> timestamp with time zone
> Oh, ye olde change-of-opclass-name problem. I've stuck a hack into
> gram.y as we've done in the past, but I'm starting to think that we
> need a better answer going forward. Maybe pg_dump could be
>
> May be it's cosmetic, but:
>
> - "Migration to 7.1" right is "Migration to 7.2"
Fixed.
>
> Be missing:
>
> - information that some parts of interface are translated to
>Swedish, Russian, French, Germany nad Czech.
> (IMHO right place for information about Peter's NLS suppo
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
>> The effects don't stop propagating there, either. The decision
>> not to insert the tuple must be reported up still further, so
>> that the executor knows not to run any AFTER INSERT/UPDATE
>> triggers and knows not to count the tuple as inserted/upd
> The effects don't stop propagating there, either. The decision
> not to insert the tuple must be reported up still further, so
> that the executor knows not to run any AFTER INSERT/UPDATE
> triggers and knows not to count the tuple as inserted/updated
> for the command completion report.
But wh
>
> > Those are directories I just created. They have the same permission as
> > all the other files here. Maybe there is a problem with CVS server
> > creating stuff with the wrong permission.
>
> >From my experience, it is likely that you have a umask problem. Or there
> is some other read/w
On Monday 01 October 2001 05:07 pm, Bruce Momjian wrote:
> I think we are all just scrambing to get beta ready while the server
> reconfigures itself. :-) I don't see any fundamental changes being
> proposed. We are trying to plug leaks and are stepping on toes, or at
> least it looks that way
>
> > Those are directories I just created. They have the same permission as
> > all the other files here. Maybe there is a problem with CVS server
> > creating stuff with the wrong permission.
>
> >From my experience, it is likely that you have a umask problem. Or there
> is some other read/w
> > > I would propose that the reference machine be one that one of the
> > > "committers" owns, and be one whose owner is willing to *always* go
> > > through the effort to resolve regression test changes and differences.
> > Er ... wasn't that *you*?
>
> Yes. At the moment my toes are bright re
> Those are directories I just created. They have the same permission as
> all the other files here. Maybe there is a problem with CVS server
> creating stuff with the wrong permission.
>From my experience, it is likely that you have a umask problem. Or there
is some other read/write permissio
> > I would propose that the reference machine be one that one of the
> > "committers" owns, and be one whose owner is willing to *always* go
> > through the effort to resolve regression test changes and differences.
> Er ... wasn't that *you*?
Yes. At the moment my toes are bright red and sore f
> > Vince, can I have write permision to /usr/local/www/www/html/docs on the
> > new web server machine so I can create symbolic links to the files in my
> > home directory?
>
> ??!!
>
> Bruce, what is actually happening here? If we are changing procedures
> for building docs, please try to have
> -Original Message-
> From: Tom Lane
>
> I said:
> > "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> >> I thought that the problem was, that you cannot simply skip the
> >> insert, because at that time the tuple (pointer) might have already
> >> been successfully inserted into an
> Vince, can I have write permision to /usr/local/www/www/html/docs on the
> new web server machine so I can create symbolic links to the files in my
> home directory?
??!!
Bruce, what is actually happening here? If we are changing procedures
for building docs, please try to have a discussion ab
On Monday 01 October 2001 04:13 pm, Thomas Lockhart wrote:
> > the only changes to directory schemes is:
> > /var/spool/ftp/* for anon ftp
> > /usr/local/www/www for web stuff
> > directory structures under each should still be as they always were ...
> But they aren't (or didn't
...
> the only changes to directory schemes is:
> /var/spool/ftp/* for anon ftp
> /usr/local/www/www for web stuff
> directory structures under each should still be as they always were ...
But they aren't (or didn't seem to be). "find" couldn't find any
instance of the docs, unpac
> > >> Not everyone has sgml tools on their local machine, do they?
> > > But everyone committing changes to docs does, or should have, sgml tools
> > > on *their* machines. Right??
> > I think it's a bad idea to create such a policy; anything we do that
> > raises the bar for docs contributions w
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> > Marc,
> >
> > it worked, but now I'm again getting:
> >
> > cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
>(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
> > cvs
Vince, can I have write permision to /usr/local/www/www/html/docs on the
new web server machine so I can create symbolic links to the files in my
home directory?
> On Mon, 1 Oct 2001, Peter Eisentraut wrote:
>
> > Bruce Momjian writes:
> >
> > > Don't rush. I am setting up my system to check t
> Marc,
>
> it worked, but now I'm again getting:
>
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
>(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
> cvs server: failed to obtain dir lock in repository
>/p
I can't do `cvs update -d -P'. I get the following error:
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
`/
Marc,
it worked, but now I'm again getting:
cvs server: failed to create lock directory for
/projects/cvsroot/pgsql/contrib/pgcrypto/expected'
(/projects/cvsroot/pgsql/contrib/pgcrypto/expected/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
/projects/cvsroot
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> >> Not everyone has sgml tools on their local machine, do they?
>
> > But everyone committing changes to docs does, or should have, sgml tools
> > on *their* machines. Right??
>
> I think it's a bad idea to create such a policy; anything we do that
Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> Not everyone has sgml tools on their local machine, do they?
> But everyone committing changes to docs does, or should have, sgml tools
> on *their* machines. Right??
I think it's a bad idea to create such a policy; anything we do that
raises the ba
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> I would propose that the reference machine be one that one of the
> "committers" owns, and be one whose owner is willing to *always* go
> through the effort to resolve regression test changes and differences.
Er ... wasn't that *you*?
> > - First one is that the regression fails on "geometry" on what appears to be
> > a difference in the 13th decimal place of the output value. See the attached
> > regression diff.
> Looks like it was not you that changed, but Thomas' reference machine.
> What platform are you on, anyway?
fwiw,
On Mon, 1 Oct 2001, Thomas Lockhart wrote:
> > I agree --- for one thing, we definitely have some bugs in the datetime
> > pg_proc entries. Unless we want to go into beta with a known initdb
> > yet to do, we've got to wait for Thomas to deal with those.
>
> I had a chance to work on timestamp f
yes
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> >
> > web server and ftp server are now on the same machine, actually .
> > everything is now merged together once more ...
> >
>
> But are our accounts/CVS on the same machines as the web server now?
>
> --
> Bruce Momjian
> ...
> > Not everyone has sgml tools on their local machine, do they?
> ...
>
> But everyone committing changes to docs does, or should have, sgml tools
> on *their* machines. Right??
For a long time I didn't. I would make the edits and check them the
next day. I tried to make sure I had stuf
Bruce Momjian <[EMAIL PROTECTED]> writes:
> From postmaster startup, by default, could we try larger amounts of
> buffer memory until it fails then back off and allocate that? Seems
> like a nice default to me.
Chewing all available memory is the very opposite of a nice default,
I'd think.
The
> I haven't figured out *where* the docs are supposed to go in the new
> scheme; none of the disk areas known to me on the new machines seem to
> have a documentation directory at all! Where is this stuff supposed to
> go? If things are going in different places, perhaps someone will have
> time t
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
> Please apply attached patch to current CVS
>
> Changes:
>
> October 1, 2001
>
> 1. Implemented binary search in a
> This is still missing a bet since it fails to mention the option of
> adjusting -B and -N instead of changing kernel parameters, but that's
> easily fixed. I propose that we reword this message and the semget
> one to mention first the option of changing -B/-N and second the option
> of changin
...
> Not everyone has sgml tools on their local machine, do they?
...
But everyone committing changes to docs does, or should have, sgml tools
on *their* machines. Right??
- Thomas
---(end of broadcast)---
TIP 1: subscribe a
> I agree --- for one thing, we definitely have some bugs in the datetime
> pg_proc entries. Unless we want to go into beta with a known initdb
> yet to do, we've got to wait for Thomas to deal with those.
I had a chance to work on timestamp features this weekend, and would
like to apply patches
Can someone give me TODO items for this discussion?
> > So, this shows two problems :
> >
> > - length() on the server side doesn't handle correctly Unicode [I have
> > the same result with char_length()], and returns the number of chars
> > (as it is however advertised to do), rather the l
>
> web server and ftp server are now on the same machine, actually .
> everything is now merged together once more ...
>
But are our accounts/CVS on the same machines as the web server now?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Patch applied. Thanks.
> OS: FreeBSD4.3
>
> Diagnostic:
> gcc -g -Wall -Wmissing-prototypes -Wmissing-declarations
> -I../../../../src/include -c -o spin.o spin.c
> In file included from /usr/include/sys/sem.h:13,
> from spin.c:26:
> /usr/include/sys/ipc.h:54: syntax error
Replying to my own method.
In src/pl/plpython/plpython.c around line 1381, PLy_input_datum_func2
erroneously assigns PLyInt_FromString to handle int8 types.
Because PLyInt_FromString uses strtol at line 1461, it fails as
soon as you pass it a parameter exceed the bounds of an int4.
There are tw
> On Mon, 1 Oct 2001, Bruce Momjian wrote:
>
> > > > The pgsql CVS, not the www CVS:
> > > >
> > > > $ ls pgsql/doc/src/FAQ
> > > > CVS/FAQ_DEV.htmlFAQ_japanese.html
> > > > FAQ.htmlFAQ_german.html
> > > >
> > > > I copy them to the web direct
I said:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
>> I thought that the problem was, that you cannot simply skip the
>> insert, because at that time the tuple (pointer) might have already
>> been successfully inserted into an other index/heap, and thus this was
>> only sanely po
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>> AFAIK the only workaround at present is to use
>> EXECUTE for queries referencing the temp table.
> But EXECUTE does not support select into, does it?
You could probably get the result you want using
FOR rec IN EXECUTE text_expression LOOP ...
> -Original Message-
> From: Tatsuo Ishii [mailto:[EMAIL PROTECTED]]
> Sent: 24 September 2001 00:58
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [ODBC] [HACKERS] UTF-8 support
>
> Currently no. But it would be easy to implement such a
> function.
> Hi all,
>
> Reading through the script files again, there seems to be several
> different methods of doing the same thing :
>
> i.e. if [ -x "$self_path/postmaster" ] && [ -x "$self_path/psql" ];
> then
The above semicolon is useless. Actually, I have never see this. The
normal way is:
> > The pgsql CVS, not the www CVS:
> >
> > $ ls pgsql/doc/src/FAQ
> > CVS/FAQ_DEV.htmlFAQ_japanese.html
> > FAQ.htmlFAQ_german.html
> >
> > I copy them to the web directory like the platform-specific FAQ's.
>
> So you renamed it to faq-dev-en
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> > On Mon, 1 Oct 2001, Bruce Momjian wrote:
> >
> > > >
> > > > Is the developer's faq still a valid document? After last nite's website
> > > > changes I've been tracking down missing items and this one pops up. The
> > > > only place I see it tho is i
Please apply attached patch to current CVS
Changes:
October 1, 2001
1. Implemented binary search in array
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Inst
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>> Can you read the man page for cs(3), AIX 4 sais it is not recommended
>> suggests to use compare_and_swap, maybe AIX 5 has more to say ?
> Note: The cs subroutine is only provided to support binary
> compatibility with AIX Version 3 applications
... cs(3)
> > Seems same as AIX 4?
Yes, identical.
>
> Hmm, does anyone want to produce new s_lock code for AIX that uses
> compare_and_swap? But I'm not sure that's the problem here.
I did once, but performance was worse, so I discarded it.
Since AIX 5 still has it, I see no reason to change
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
> I think the default NBuffers (64) is too low to give meaningful
> performance numbers, too. I've been thinking that maybe we should
> raise it to 1000 or so by default.
>> Maybe something simple like pg_ctl shell script message, or s
> On Mon, 1 Oct 2001, Bruce Momjian wrote:
>
> > >
> > > Is the developer's faq still a valid document? After last nite's website
> > > changes I've been tracking down missing items and this one pops up. The
> > > only place I see it tho is in the cvs Attic. Isn't the attic where the
> > > jun
should be fixed now ...
On Mon, 1 Oct 2001, Oleg Bartunov wrote:
> Marc,
>
> what's happens with cvs ? I still can't update:
>
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgstattuple'
>(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission
> However my application code is assuming that duplicate rows will
> simply be ignored (this is the case in Ingres, and I believe Oracle's
> bulkloader too). I propose modifying _bt_check_unique() in
> /backend/access/nbtree/nbtinsert.c to emit a NOTICE (rather than
> ERROR) elog() and return NULL
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> what's happens with cvs ? I still can't update:
> cvs server: failed to create lock directory for
>/projects/cvsroot/pgsql/contrib/pgstattuple'
>(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission denied
> cvs server: failed to obtain
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> we arent' ready to go beta ... I'll let you know when ...
I agree --- for one thing, we definitely have some bugs in the datetime
pg_proc entries. Unless we want to go into beta with a known initdb
yet to do, we've got to wait for Thomas to deal w
> > - First one is that the regression fails on "geometry" on what appears
to be
> > a difference in the 13th decimal place of the output value. See the
attached
> > regression diff.
>
> Looks like it was not you that changed, but Thomas' reference machine.
> What platform are you on, anyway?
>
No
Lee Kindness writes:
> If I'm going to modify 'COPY INTO' to include 'ignore duplicates'
> functionality it looks like I'll have to add to the COPY syntax. The
> most obvious way is to add:
> WITH IGNORE DUPLICATES
Or does it make more sense to add a 'COPY_IGNORE_DUPLICATES' SET
parameter?
Sounds good. Keep us posted. This will probably not make it into 7.2
but can be added to 7.3. We can perhaps conditionally use your code in
place of what is there. I have also looked at reducing the write() size
for WAL secondary writes. That will have to wait for 7.3 too because we
are so n
> > Per Tom's request(1000 concurrent backends), I tried current on IBM
> > AIX 5L and found that make check hungs:
> >
> > parallel group (13 tests): float4 oid varchar
> >
> > pgbench hungs too if more than 4 or so concurrent backends are
> > involved.
>
> I once had hangs during make check o
> Tom Lane wrote:
> >
>
> > I think the default NBuffers (64) is too low to give meaningful
> > performance numbers, too. I've been thinking that maybe we should
> > raise it to 1000 or so by default. This would trigger startup failures
> > on platforms with small SHMMAX, but we could tell peo
On Mon, 1 Oct 2001, Bruce Momjian wrote:
> >
> > Is the developer's faq still a valid document? After last nite's website
> > changes I've been tracking down missing items and this one pops up. The
> > only place I see it tho is in the cvs Attic. Isn't the attic where the
> > junk goes that no
Okay,
If I'm going to modify 'COPY INTO' to include 'ignore duplicates'
functionality it looks like I'll have to add to the COPY syntax. The
most obvious way is to add:
WITH IGNORE DUPLICATES
to the syntax. I'm going to need my hand held a bit for this! The
grammar for COPY will need updating
>
> Is the developer's faq still a valid document? After last nite's website
> changes I've been tracking down missing items and this one pops up. The
> only place I see it tho is in the cvs Attic. Isn't the attic where the
> junk goes that noone wants anymore? Is that where the faq belongs?
> "Justin" == Justin Clift <[EMAIL PROTECTED]> writes:
Justin> if [ x"$foo" = x"" ]; then
Justin> or
Justin> if [ "$op" = "" ]; then
Justin> or
Justin> if [ "$foo" ]; then
I'm not the slightest bit a shell expert, but why not :-
if [ -z "$foo" ]; then
Is this POSIX/
On Fri, Sep 28, 2001 at 03:50:12PM -0400, Bruce Momjian wrote:
> > I'm using the current CVS (4.0.8-dev)- It's spectacular. Lower memory
> > usage, more descriptive debug, better control over it. Tons more options,
> > smaller code, much much faster.
> > Note: if you are not having the prob
Justin Clift wrote:
> if [ x"$foo" = x"" ]; then
This is the safest way. It prevents problems when $foo begins with with a
"-"
I don't know about your first question, though.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
we arent' ready to go beta ... I'll let you know when ...
On Sun, 30 Sep 2001, Bruce Momjian wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, I think we are on track for Monday beta.
> >
> > One thing that I think absolutely *must* happen before we can go beta
> > is to fix the do
Hi all,
Reading through the script files again, there seems to be several
different methods of doing the same thing :
i.e. if [ -x "$self_path/postmaster" ] && [ -x "$self_path/psql" ];
then
or
if [[ -x "$self_path/postmaster" && -x "$self_path/psql" ]]; then
if [ x"$foo" = x"" ]; then
o
Zeugswetter Andreas SB SD wrote:
[EMAIL PROTECTED]">
IMHO, you should copy into a temporary table and the do a select distinct from it into the table that you want.
Which would be way too slow for normal operation :-(We are talking about a "fast as possible" data load from a fla
> IMHO, you should copy into a temporary table and the do a select
> distinct from it into the table that you want.
Which would be way too slow for normal operation :-(
We are talking about a "fast as possible" data load from a flat file
that may have duplicates (or even data errors, but that
i
Marc,
what's happens with cvs ? I still can't update:
cvs server: failed to create lock directory for
/projects/cvsroot/pgsql/contrib/pgstattuple'
(/projects/cvsroot/pgsql/contrib/pgstattuple/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
/projects/cvsroot/p
> > Would this seem a reasonable thing to do? Does anyone rely on COPY
> > FROM causing an ERROR on duplicate input?
>
> Yes. This change will not be acceptable unless it's made an optional
> (and not default, IMHO, though perhaps that's negotiable) feature of
> COPY.
>
> The implementation mi
I can move it manually on the backend ... let me know when/if you want it
done ...
On Mon, 1 Oct 2001, Stefan Rindeskar wrote:
> When moving files in CVS I usually use the cvs add/cvs remove in the same
> commit with -m something like 'Changed location/name for file xxx to yyy'.
>
> That way
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> I thought that the problem was, that you cannot simply skip the
> insert, because at that time the tuple (pointer) might have already
> been successfully inserted into an other index/heap, and thus this was
> only sanely possible with sa
Lee Kindness <[EMAIL PROTECTED]> writes:
> I see where you're coming from, but seriously what's the use/point of
> COPY aborting and doing a rollback if one duplicate key is found?
Error detection. If I'm loading what I think is valid data, having the
system silently ignore certain types of erro
Tom Lane writes:
> Lee Kindness <[EMAIL PROTECTED]> writes:
> > Would this seem a reasonable thing to do? Does anyone rely on COPY
> > FROM causing an ERROR on duplicate input?
> Yes. This change will not be acceptable unless it's made an optional
> (and not default, IMHO, though perhaps tha
Tom Lane wrote:
>
> I think the default NBuffers (64) is too low to give meaningful
> performance numbers, too. I've been thinking that maybe we should
> raise it to 1000 or so by default. This would trigger startup failures
> on platforms with small SHMMAX, but we could tell people to use -B
Justin Clift writes:
> Lee Kindness wrote:
> > WITH ON_DUPLICATE = CONTINUE|TERMINATE (or similar)
> I would suggest :
> WITH ON_DUPLICATE = IGNORE|TERMINATE
> purely for easier understanding, given there is no present standard nor
> other databases' syntax to conform to.
Personally I don'
Lee Kindness <[EMAIL PROTECTED]> writes:
> Would this seem a reasonable thing to do? Does anyone rely on COPY
> FROM causing an ERROR on duplicate input?
Yes. This change will not be acceptable unless it's made an optional
(and not default, IMHO, though perhaps that's negotiable) feature of
COPY
its stale right now, but there have been no changes to ftp yet anyway ...
vince has a bit of work to do before we break all the mirrors and force
them to point to the new server ... almost done, so close, so close ...
On Mon, 1 Oct 2001, Oleg Bartunov
wrote:
> Marc,
>
> will hub.org::postgres
> Per Tom's request(1000 concurrent backends), I tried current on IBM
> AIX 5L and found that make check hungs:
>
> parallel group (13 tests): float4 oid varchar
>
> pgbench hungs too if more than 4 or so concurrent backends are
> involved.
I once had hangs during make check on AIX 4, but afte
> > The O_DIRECT flag has been added to open(2) and fcntl(2). Specifying
this
> > flag for open files will attempt to minimize the cache effects of
reading
> > and writing.
>
> I wonder if using this for WAL would be good.
Not before the code is not optimized to write more than the current 8k
t
Is the developer's faq still a valid document? After last nite's website
changes I've been tracking down missing items and this one pops up. The
only place I see it tho is in the cvs Attic. Isn't the attic where the
junk goes that noone wants anymore? Is that where the faq belongs?
Vince.
--
When moving files in CVS I usually use the cvs add/cvs remove in the same
commit with -m something like 'Changed location/name for file xxx to yyy'.
That way you have trace in the log about what happened to a file as both
old/new name/location.
Maybe not the nicest way but it usually works fine
1 - 100 of 109 matches
Mail list logo
