On Wed, 11 Oct 2000, Bruce Momjian wrote:
Considering no one has used it in 4 years that I remember, my guess is
that it is an abandonded Berkeley project.
It appeard to work the last time I tried it (2 years ago or so.)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |
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
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 a
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,
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 view
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
[ 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 Momjian
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
* 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 0x1dd210 in elog
| % 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
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 cleanup
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 our
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 of
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 started before
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 that
* 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 application
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
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
| 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 some
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
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
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
| 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
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 db
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
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
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
27 matches
Mail list logo
