It seems postmaster won't restart under WAL. What I have done so far
was creating some tables and inserting fairly large amount of tuples
(10 tuples) using pgbench.
Here is the test sequence:
pg_ctl -w stop
rm -fr /usr/local/pgsql/data
initdb
pg_ctl -w start
createdb test
./pgbench -i test
p
On Tue, 31 Oct 2000, Alfred Perlstein wrote:
> * Steve Wolfe <[EMAIL PROTECTED]> [001031 13:47] wrote:
> >
> > > >(Incidentally, we've toyed around with developping a
> > query-caching
> > > > system that would sit betwen PostgreSQL and our DB libraries.
> > >
> > > Sounds amazing, but
* Karel Zak <[EMAIL PROTECTED]> [001031 16:18] wrote:
>
> On Tue, 31 Oct 2000, Alfred Perlstein wrote:
>
> > I never saw much traffic regarding Karel's work on making stored
> > proceedures:
> >
> > http://people.freebsd.org/~alfred/karel-pgsql.txt
> >
> > What happened with this? It looked pr
> My query cache is in usable state and it's efficient for all things
> those motivate me to work on this.
Well, you know, us application developers are lazy egoists, we want all of
that without efforts on our side :) In fact, customers do that. They don't
want to pay for both implementin
On Tue, 31 Oct 2000, Alfred Perlstein wrote:
> I never saw much traffic regarding Karel's work on making stored
> proceedures:
>
> http://people.freebsd.org/~alfred/karel-pgsql.txt
>
> What happened with this? It looked pretty interesting. :(
It's probably a little about me :-) ... well,
> > The first test did not go very well. I did a fresh compile, initdb,
> > started the postmaster, ran 'make installcheck' (sequential
> > regression tests), and sent a kill -QUIT to the postmaster during the
> > numeric test.
> > Then I restarted the postmaster and got a load of lines like
>
Thanks for the info.
> The first test did not go very well. I did a fresh compile, initdb,
> started the postmaster, ran 'make installcheck' (sequential regression
> tests), and sent a kill -QUIT to the postmaster during the
> numeric test.
> Then I restarted the postmaster and got a load of lines like
>
> REDO @ 0
I never saw much traffic regarding Karel's work on making stored
proceedures:
http://people.freebsd.org/~alfred/karel-pgsql.txt
What happened with this? It looked pretty interesting. :(
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a j
* Peter Eisentraut <[EMAIL PROTECTED]> [001031 12:57] wrote:
> I'd like to add an option or two to restrict the set of users that can
> connect to the Unix domain socket of the postmaster, as an extra security
> option.
>
> I imagine something like this:
>
> unix_socket_perm = 0660
> unix_socket
* Steve Wolfe <[EMAIL PROTECTED]> [001031 13:47] wrote:
>
> > >(Incidentally, we've toyed around with developping a
> query-caching
> > > system that would sit betwen PostgreSQL and our DB libraries.
> >
> > Sounds amazing, but requires some research, I guess. However, in
> many
> >
Title: RE: [HACKERS] Restricting permissions on Unix socket
Please take me off this list! I have received over 50 emails in the last 24 hours and I have no idea why I am getting them. Please look for email address [EMAIL PROTECTED] or [EMAIL PROTECTED] and take it out! Thanks!
-Origi
> I'd like to add an option or two to restrict the set of users that can
> connect to the Unix domain socket of the postmaster, as an extra security
> option.
>
> I imagine something like this:
>
> unix_socket_perm = 0660
> unix_socket_group = pgusers
>
> Obviously, permissions that don't have
> I believe that its just resting on Vadim again to give us the go ahead
> ... which I believe its always been on his shoulders, no? :)
>
> Vadim?
I think that at least 1 & 2 from WAL todo (checkpoints and port to
machines without TAS) is required before beta. As well as more testing...
Did an
I'm about to launch into an experiment that will do some new things
inside the PG server. I'm sure to have a lot of problems, and one
of them I can already tell is going to be difficult is the business
of contexts: memory contexts, scan contexts and the like.
Before I go around shooting myself i
I'd like to add an option or two to restrict the set of users that can
connect to the Unix domain socket of the postmaster, as an extra security
option.
I imagine something like this:
unix_socket_perm = 0660
unix_socket_group = pgusers
Obviously, permissions that don't have 6's in there don't m
* Michael J Schout <[EMAIL PROTECTED]> [001031 11:22] wrote:
> Hi.
>
> Ive had a crash in postgresql 7.0.2. Looking at what happened, I actually
> suspect that this is a filesystem bug, and not a postgresql bug necessarily,
> but I wanted to report it here and see if anyone else had any opinions
Hi.
Ive had a crash in postgresql 7.0.2. Looking at what happened, I actually
suspect that this is a filesystem bug, and not a postgresql bug necessarily,
but I wanted to report it here and see if anyone else had any opinions.
The platform this happened on was linux (redhat 6.2), kernel 2.2.16
After much too long a time, I have updated the RedHat RPMset on
ftp.postgresql.org.
The version is 7.0.2, release is 21.
Please see the changelog for more information (rpm -q --changelog
postgresql for installed packages, rpm -qp --changelog
postgresql-7.0.2-21.i386.rpm for packages before insta
Hi:
I'm wrinting a graphical interface that would manage users, groups and permissions on
a postgresql database, that was the reason for me to ask for this datatype since it
is in the pg_class table. If it is going to
dissapear soon then what should I do ?, is there any other form to handle
Thanks Peter. I will download tomorrow when the new snapshot is
available. So how do we find out whether hex needs to be supported? I
see what you mean with ('1001' as bit), but shouldn't that be (B'1001'
as bit)? Certainly if hex values are allowed the first version is
ambiguous. I would have to
Hello,
there's really wierd trouble.
When I run 2 vacuum's in parallel they hangs. Both.
I use PostgreSQL from 7.0.x CVS (almost 7.0.3).
Any ideas? Tom?
--
Sincerely Yours,
Denis Perchine
--
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
FidoNe
Adriaan Joubert writes:
> Peter, I think it is a problem if the B or X are dropped from the input,
> as that is the only way to determine whether it is a binary or hex
> string.
Well, you just assume it's a binary string, because it's unclear as of yet
whether you're going to get to handle hex s
At 14:14 31/10/00 +0100, Zeugswetter Andreas SB wrote:
>>
>> Which is why I like the client being able to ask the
>> optimizer for certain kinds of solutions *explicitly*.
>
>Yes, something like:
> set optimization to [first_rows|all_rows]
>
That's one way that is usefull for affecting al
> >So I think if you want to make optimization decisions based on cursors
> >being used versus a "normal" select, then the only thing you can safely
> >take into account is the network roundtrip and client processing per
> >fetch, but that might be as random as anything.
>
> Which is why I like
Peter Eisentraut wrote:
>
> Adriaan Joubert writes:
>
> > > 2. We don't handle and literals correctly;
> > > the scanner converts them into integers which seems quite at variance
> > > with the spec's semantics.
> >
> > This is still a problem that needs to be fixed.
>
> I have gotten the B'1
At 10:51 31/10/00 +0100, Peter Eisentraut wrote:
>Tom Lane writes:
>
>> 1. If DECLARE CURSOR does not contain a LIMIT, continue to plan on the
>> basis of 10%-or-so fetch
>
>I'd say that normally you're not using cursors because you intend to throw
>away 80% or 90% of the result set, but instead y
Adriaan Joubert writes:
> > 2. We don't handle and literals correctly;
> > the scanner converts them into integers which seems quite at variance
> > with the spec's semantics.
>
> This is still a problem that needs to be fixed.
I have gotten the B'1001'-style syntax to work, but the zpbit_in
Luis Magaña writes:
> What is the data definition for the aclitem datatype, I'm not able to found it
>in the sources, I know is there but I was not able to find it. Thank you.
src/backend/utils/adt/acl.c
Don't use it though, it's slated to disappear soon.
--
Peter Eisentraut [EMA
Peter Mount writes:
> Did that, and it still doesn't substitute @abs_top_srcdir@
Hmm, if you have "configure" revision 1.74 then you should certainly get
something for @abs_top_srcdir@. Try to remove config.cache and re-run
configure by hand. Most odd...
--
Peter Eisentraut [EMAIL PROTE
Tom Lane writes:
> 1. If DECLARE CURSOR does not contain a LIMIT, continue to plan on the
> basis of 10%-or-so fetch
I'd say that normally you're not using cursors because you intend to throw
away 80% or 90% of the result set, but instead you're using it because
it's convenient in your programmi
Lamar Owen writes:
> In the environment of the general purpose OS upgrade, the RPM's
> installation scripts cannot fire up a backend, nor can it assume one
> is running or is not running, nor can the RPM installation scripts
> fathom from the run-time environment whether they are being run from a
32 matches
Mail list logo
