I notced that COPY FROM does not invoke the length coercion function
before calling heap_insert(). This leads sometimes bad things such as
incorrectly truncated mutibyte strings. My idea is finding an
appropreate function like currently
coerce_type_typmod(parser/parse_coerce.c) does, and calling i
Hello,
just my $0.02...
If I do
insert into x
select * from y limit 10;
I will get all of rows in x inserted, not just 10...
I already wrote about this... But did not get any useful reply.
> This is an interesting idea. We don't allow ORDER BY in INSERT INTO ...
> SELECT because it doesn't m
This time in the client library...
(gdb) bt
#0 0xff215dd0 in _poll ()
#1 0xff1ce79c in select ()
#2 0xff08b164 in select ()
#3 0xff338ec0 in PQgetResult (conn=0xa89c8) at fe-exec.c:1126
#4 0xff339168 in PQexec (conn=0xa89c8,
query=0xfe107b98 "UPDATE url SET
total_os='4963.98|135037.315
> > Could this be added? I am willing to help with the coding.
>
> This is what Version 7.1 WAL is all about.
> There might be some help wanted in one of the possible backup methods:
> 1. a pg_dumpall restore, and a subsequent restore of logs
> 2. a restore of a "physical backup of d
> > > How far are we from seeing the version 7.1 out?
> >
> > beta starts ~Nov 1st, release in January ...
>
> Just wondering, WAL is going to be integrated when, and that gives how
Hopefully, next week.
> much time to test it before releasing the beta?
Vadim
| I said:
| > BlockSig includes SIGUSR1.
|
| Oh, wait, I take that back. It's initialized that way, but then
| postmaster.c removes SIGUSR1 from the set.
|
| regards, tom lane
So, back to my initial question, why not make each postmaster SIG_IGN
SIGUSR1 after it receive
On Thu, 12 Oct 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > On Thu, 12 Oct 2000, Tom Lane wrote:
> >> Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> My conclusion would be that we need both:
> 1. a fast system table only solution with physical/logical
I said:
> BlockSig includes SIGUSR1.
Oh, wait, I take that back. It's initialized that way, but then
postmaster.c removes SIGUSR1 from the set.
regards, tom lane
Dan Moschuk <[EMAIL PROTECTED]> writes:
> | We should probably tweak the postmaster to be less enthusiastic about
> | signaling its children repeatedly.
> Perhaps have postgres ignore SIGUSR1 after it has already received one?
Now that you mention it, it tries to do exactly that:
void
quickdie(
| Still, it's a mighty peculiar backtrace.
Indeed.
| After looking at postmaster.c, I see that the postmaster will issue
| SIGUSR1 to all remaining backends *each* time it sees a child exit
| with nonzero status. And it just so happens that quickdie() chooses
| to exit with exit(1) not exit(0)
Dan Moschuk <[EMAIL PROTECTED]> writes:
> It would appear from that very rough test program that solaris doesn't mind
> system calls from within a signal handler.
Still, it's a mighty peculiar backtrace.
After looking at postmaster.c, I see that the postmaster will issue
SIGUSR1 to all remaining
On Thu, Oct 12, 2000 at 04:18:05PM -0400, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane writes:
> >> Even though I think '|' is clearly given a bogus precedence, I doubt
> >> it's a good idea to change it.
>
> > The only builtin '|' operator, besides the not-there-ye
| > Sparc solaris 2.7 with postgres 7.0.2
| > It seems to be reproducable, the server crashes on us at a rate of about
| > every few hours.
|
| That's a very bizarre backtrace. Why the multiple levels of recursive
| entry to the quickdie() signal handler? I wonder if you aren't looking
| at so
>
> On Thu, 12 Oct 2000, Bruce Momjian wrote:
>
> > Is this addressed in 7.1?
>
> Not as far as I know.
> It would require one or more of:
> ALTER FUNCTION
> ALTER TABLE ... DROP CONSTRAINT
> a reference system that automatically drops/
> restricts based on objects referencing the
> thi
On Thu, Oct 12, 2000 at 09:34:05PM +0200, Peter Eisentraut wrote:
> Well, what are we going to do with this? I think we should take it.
> Since I encouraged him to write it, I'd volunteer to take care of it.
Nice :)
> We might want to change the bitxor operator to # (or at least something
> d
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Even though I think '|' is clearly given a bogus precedence, I doubt
>> it's a good idea to change it.
> The only builtin '|' operator, besides the not-there-yet bitor, is some
> arcane prefix operator for the "tinterval" type, wh
Peter Mount wrote:
>
> On Wed, 11 Oct 2000, Joseph Shraibman wrote:
>
> [snip]
>
> > It isn't. I wish there were online mail archives. But anyway the
> > reason it isn't is that if two statements use the same connection, when
> > one of them calls enters a transaction the other one does too.
Dan Moschuk <[EMAIL PROTECTED]> writes:
> Sparc solaris 2.7 with postgres 7.0.2
> It seems to be reproducable, the server crashes on us at a rate of about
> every few hours.
That's a very bizarre backtrace. Why the multiple levels of recursive
entry to the quickdie() signal handler? I wonder if
On Thu, 12 Oct 2000, Bruce Momjian wrote:
> Is this addressed in 7.1?
Not as far as I know.
It would require one or more of:
ALTER FUNCTION
ALTER TABLE ... DROP CONSTRAINT
a reference system that automatically drops/
restricts based on objects referencing the
thing you drop (and this wo
Tom Lane writes:
> Even though I think '|' is clearly given a bogus precedence, I doubt
> it's a good idea to change it.
The only builtin '|' operator, besides the not-there-yet bitor, is some
arcane prefix operator for the "tinterval" type, which returns the start
of the interval. This is all
* Tom Lane <[EMAIL PROTECTED]> [001012 12:14] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I'm pretty sure I know what to do now, it's pretty simple actually,
> > I can examine the state of the connection, if it's in PGASYNC_COPY_IN
> > then I don't grow the buffer, I inform the appli
Well, what are we going to do with this? I think we should take it.
Since I encouraged him to write it, I'd volunteer to take care of it.
We might want to change the bitxor operator to # (or at least something
distinct from ^) as well, for consistency.
Marko Kreen writes:
>
> Well, I was in
Is this addressed in 7.1?
>
> This is particular to postgres, although the
> SQL behavior would have either dropped
> the constraint or prevented the drop in the
> first place.
>
> There's been some talk of an ALTER FUNCTION
> that would let you change the code behind
> a function without a d
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I'm pretty sure I know what to do now, it's pretty simple actually,
> I can examine the state of the connection, if it's in PGASYNC_COPY_IN
> then I don't grow the buffer, I inform the application that the
> data will block, if it's no PGASYNC_COPY_I
> Here's two ideas I had for optimizing vacuum, I apologize in advance
> if the ideas presented here are niave and don't take into account
> the actual code that makes up postgresql.
>
>
>
> #1
>
> Reducing the time vacuum must hold an exlusive lock on a table:
>
> The idea is
> #2
>
> Reducing the amount of scanning a vaccum must do:
>
> It would make sense that if a value of the earliest deleted chunk
> was kept in a table then vacuum would not have to scan the entire
> table in order to work, it would only need to start at the 'earliest'
> invalidated row.
>
> The
> Alfred Perlstein wrote:
> > #1
> >
> > Reducing the time vacuum must hold an exlusive lock on a table:
> >
> > The idea is that since rows are marked deleted it's ok for the
> > vacuum to fill them with data from the tail of the table as
> > long as no transaction is in progress that has start
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Thu, 12 Oct 2000, Tom Lane wrote:
>> Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
My conclusion would be that we need both:
1. a fast system table only solution with physical/logical column id
2. a tool that does the cleanup (
This is a very nice summary of OpenVMS work for PostgreSQL. That IPC
stuff can be very difficult, so I imagine it would take an experienced
VMS person to get that done.
> Hi Postgresql Developers!
>
> A few weeks ago I posted a message on the pgsql-general list asking about a
> possible port o
* Bruce Momjian <[EMAIL PROTECTED]> [000929 19:32] wrote:
> Can someone remind me of where we left this?
[snip]
Sorry for the really long follow-up, but this was posted a long time
ago and I wanted to refresh everyone's memory as to the problem.
The problem is that when doing a COPY from stdin
I'm just committing the first changes to ECPGs parser so variables are
allowed wherever possible instead of constants. I'm pretty sure this breaks
stuff at one point or the other. Also I have not yet fixed all problems I
know about. So please bear with me.
I'd like everyone who has embedded SQL s
> I have created the following patch with applies to the current source
> tree. However, there have been significant changes since 7.0, and even
> my patch does not incorporate all the other changes.
>
> I am not sure what to recommend. It would be optimal if you could take
> your patch, grab o
On Thu, 12 Oct 2000, Tom Lane wrote:
> Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> > My conclusion would be that we need both:
> > 1. a fast system table only solution with physical/logical column id
> > 2. a tool that does the cleanup (e.g. vacuum)
>
> But the peak space usage during
| % uname -sr
| SunOS 5.7
|
| from sys/signal.h:
|
| #define SIGUSR1 16 /* user defined signal 1 */
|
| Are you sure you don't have any application running amok sending
| signals to processes it shouldn't? Getting a superfolous signal
| seems out of place, this doesn't look like a crash
>
> Well, If I'm reading the spec correctly,
> INSERT INTO references a query expression
> which doesn't include ORDER BY as an option, so this
> is even less SQL since we're actually not just changing
> it to allow our non-standard bit, but we're changing
> a piece that is explicitly not allowe
* Dan Moschuk <[EMAIL PROTECTED]> [001012 09:47] wrote:
>
> Sparc solaris 2.7 with postgres 7.0.2
>
> It seems to be reproducable, the server crashes on us at a rate of about
> every few hours.
>
> Any ideas?
>
> GNU gdb 4.17
> Copyright 1998 Free Software Foundation, Inc.
[snip]
> #78 0x1dd
I think that was the agreement on the best way to do it (although the
operator is even easier looking, just replace = with whatever the operator
is.). This would mean moving the array code from contrib into the real
source tree probably though, or having the foreign key stuff figure out if
you h
Sparc solaris 2.7 with postgres 7.0.2
It seems to be reproducable, the server crashes on us at a rate of about
every few hours.
Any ideas?
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change i
> Peter Mount <[EMAIL PROTECTED]> writes:
> > It lists it under "Generic EPS (*.eps, *.AI, ...)" so its similar to eps
> > anyhow.
>
> Yes, I found that I just had to comment out some stuff at the end
> (%%PageTrailer and showpage) to get the file to work as plain EPS.
> Now I've got a pretty sha
Peter Mount <[EMAIL PROTECTED]> writes:
> It lists it under "Generic EPS (*.eps, *.AI, ...)" so its similar to eps
> anyhow.
Yes, I found that I just had to comment out some stuff at the end
(%%PageTrailer and showpage) to get the file to work as plain EPS.
Now I've got a pretty sharp-looking tit
I looked for that myself. It is on the web site in slices so it can be
rendered faster in a browser.
> I just spent a fruitless half hour rooting around the website for
> our elephant-in-crystal logo. I need a moderately large, clean copy
> for the title slide of a presentation. Where's the or
[ Charset ISO-8859-1 unsupported, converting... ]
>
> > TODO updated:
> >
> > * Prevent truncate on table with a referential integrity
> > trigger (RESTRICT)
>
> I think this was solved in current with a better approach
> (checks if referenced table is empty).
Removed from TODO.
--
Bruce
On Thu, 12 Oct 2000, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > We never really had a large one.
>
> Drat. Guess I'll have to use the cartoon elephant instead.
>
> Does anyone know how to convert a ".ai" file into EPS? I think that's
> some kind of vector-art format, an
Tom Lane wrote:
>
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > We never really had a large one.
>
> Drat. Guess I'll have to use the cartoon elephant instead.
>
> Does anyone know how to convert a ".ai" file into EPS? I think that's
> some kind of vector-art format, and it'd be nice to p
Bruce Momjian writes:
> My assumption is that we never came up with any solution to this, right?
It stopped when we noticed that proper support for non-finite values will
break indexing, because the relational trichotomy doesn't hold.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> P.S. I have used bsearch() to search code spaces. Is bsearch() is
> portable enough?
According to my references, bsearch() was originally a SysV localism
but is a required library function in ANSI C. So in theory it should
be portable enough ... but I n
The Hermit Hacker writes:
> > How far are we from seeing the version 7.1 out?
>
> beta starts ~Nov 1st, release in January ...
Just wondering, WAL is going to be integrated when, and that gives how
much time to test it before releasing the beta?
--
Peter Eisentraut [EMAIL PROTECTED]
Travis Bauer writes:
> Which version of Solaris was he using? I'm using Solaris 2.7, and 7.0.2
> compiled, installed and works without a hitch.
He was using the Solaris compiler rather than GCC, and that couldn't
possibly have worked, as it turned out.
--
Peter Eisentraut [EMAIL PROTECTE
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> We never really had a large one.
Drat. Guess I'll have to use the cartoon elephant instead.
Does anyone know how to convert a ".ai" file into EPS? I think that's
some kind of vector-art format, and it'd be nice to preserve scalability.
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> My conclusion would be that we need both:
> 1. a fast system table only solution with physical/logical column id
> 2. a tool that does the cleanup (e.g. vacuum)
But the peak space usage during cleanup must still be 2X.
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> I don't know, but imho one field for all permissions would have been
> better, like we discussed for the permissions system table, since
> there are more rights in SQL than read/write (e.g. write is separated
> into insert, update and delete)
N
At 16:21 12/10/00 +0200, Zeugswetter Andreas SB wrote:
>>
>> Could this be added? I am willing to help with the coding.
>
>This is what Version 7.1 WAL is all about.
>There might be some help wanted in one of the possible backup methods:
> 1. a pg_dumpall restore, and a subsequent restore
> TODO updated:
>
> * Prevent truncate on table with a referential integrity
> trigger (RESTRICT)
I think this was solved in current with a better approach
(checks if referenced table is empty).
Andreas
> WAL would provide the framework to do something like that, but I still
> say it'd be a bad idea. What you're describing is
> irrevocable-once-it-starts DROP COLUMN; there is no way to
> roll it back.
> We're trying to get rid of statements that act that way, not add more.
Yes.
> I am not con
> I am a long time ordbms proponent (illustra, informix and
> now postgresql). And I have heard mixed information
> regarding Oracle's extensibility. Do they use a unified
> type system? Are cartriges separate processes? Do the
> separate processes (if they are) share memory with the
> serv
> Well, that would only be part og what I'm looking for. The thing I like about
> informix is that I can make a Level 0 backup of all the data (equal to the
> pg_dumpall), and then leave the logical logs downloading continuosly, so that
> if in one moment the system breaks, I restore the Level
Sorry for the late reply, but I was on vacation (my 2. daughter was born).
> After looking at the rule rewriter some more, I realized that the only
> way to push all permissions checks to execution time is not
> only to keep
> skipAcl, but to generalize it. The problem is with checks on the vie
There is some stuff which last time I looked is in contrib that allows
queries to test if something is in an array. Something vaguely like
SELECT * from part, box where IN(part.num, box.array).
Having this integrated in the foreign key stuff would certainly be
important for object databases, whic
> > being deleted, then if the system crashes part way through,
> it should be
> > possible to continue after the system is brought up, no?
>
> If it crashes in the middle, some rows have the column
> removed, and some
> do not.
We would need to know where this separation is, but we cannot do
On Thu, 12 Oct 2000, Tom Lane wrote:
> I just spent a fruitless half hour rooting around the website for
> our elephant-in-crystal logo. I need a moderately large, clean copy
> for the title slide of a presentation. Where's the original hiding?
We never really had a large one. There was a gol
It seems that I'm now getting some delayed emails from around the 27th of
September. It's probably at my end, but if you sent me anything important,
like patches etc, please can you resend it to me.
Thanks, Peter
--
Peter T Mount [EMAIL PROTECTED] http://www.retep.org.uk
PostgreSQL JDBC Driver
Hi,
I have committed the first implementation of an automatic code
conversion between UNICODE and other encodings. Currently
ISO8859-[1-5] and EUC_JP are supported. Supports for other encodings
coming soon. Testings of ISO8859 are welcome, since I have almost no
knowledge about European languages
62 matches
Mail list logo
