Hi all,
I'm compiling the last postgres CVS version and I get:
vacuum.c: In function `repair_frag':
vacuum.c:1528: warning: unused variable `myXID'
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EM
Hi all,
I'm doing some experiments with NT, I din't expect this behaviuor:
create table test ( a integer );
insert into test values (3);
insert into test values (4);
insert into test values (5);
insert into test values (6);
SESSION 1;SESSION 2;
begin;
Hi all,
still experimenting NT:
kalman=# begin;
BEGIN
kalman=# select * from a;
ERROR: relation "a" does not exist
kalman=# begin;
BEGIN
kalman=# select * from test;
ERROR: current transaction is aborted, commands ignored until end of transaction block
I think the second begin shall fail instead
Hi all,
why after compiling and install postgresql CVS tip
there is no information on how to run it ? Also
the file INSTALL is not there anymore.
Do I miss something in these days ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9: the planner
This is presumably a standard feature of any PITR design - if the
failure event destroys the current transaction log, then you can only
recover transactions that committed in the last *archived* log.
regards
Mark
Simon Riggs wrote:
The test works, but gives what looks like strange results: the t
FYI - I can confirm that the patch fixes main issue.
Simon Riggs wrote:
This was a very confusing test...Here's what I think happened:
.
The included patch doesn't attempt to address those issues, yet.
Best regards, Simon Riggs
---(end of broadcast)--
Gaetano Mendola wrote:
> Bruce Momjian wrote:
>
> > Scott Marlowe wrote:
> >
> I use a checkpoint_segments = 16 but in my pg_xlog I have
> 35 files. Why 35 files ?
> >
> >
> > You have 35 because the max files in pg_xlog is 2*checkpoint_segments +1
> > or something like that. This is do
Bruce Momjian wrote:
Scott Marlowe wrote:
I use a checkpoint_segments = 16 but in my pg_xlog I have
35 files. Why 35 files ?
You have 35 because the max files in pg_xlog is 2*checkpoint_segments +1
or something like that. This is documented in the SGML.
Ok, that explain why. And they will remain t
Scott Marlowe wrote:
> > > I use a checkpoint_segments = 16 but in my pg_xlog I have
> > > 35 files. Why 35 files ?
You have 35 because the max files in pg_xlog is 2*checkpoint_segments +1
or something like that. This is documented in the SGML.
--
Bruce Momjian| http:/
Joshua D. Drake wrote:
> Hello,
>
> Perhaps you have an open transaction that isn't closing and thus the
> pg_xlog continues to grow?
>
> Sincerely,
>
> Joshua D. Drake
I was thinking about it but unfortunately there is no transaction open.
On my development database, were I simulate the same opera
Bruce said the other day open transactions can't cause this problem.
I wonder what all can?
On Tue, 2004-07-20 at 16:32, Joshua D. Drake wrote:
> Hello,
>
> Perhaps you have an open transaction that isn't closing and thus the
> pg_xlog continues to grow?
>
> Sincerely,
>
> Joshua D. Drake
>
OK, it turns out myXID is only used by Assert tests, and most developers
compile with Asserts. I have fixed this by defining the variable only
when asserts are enabled.
Patch attached and applied.
---
Gaetano Mendola wrote
Hello,
Perhaps you have an open transaction that isn't closing and thus the
pg_xlog continues to grow?
Sincerely,
Joshua D. Drake
Gaetano Mendola wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
today I add 4 new columns to a table with 4E+06 rows,
I also update to an initial value th
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Added to TODO:
> >
> > * Allow psql to display permission information using \df+ and \l+
>
> What about, develop a consistent way to display privilege information
> for all objects in psql?
OK, item wording updated.
--
Bruce Momjian
(cc: -hackers as I think this has been raised there before)
It's going to be fun using anything more than very basic cursors via the
V3 protocol in the JDBC driver. DECLARE does not work with parameters
passed via a Parse/Bind combination -- which is how we currently always
pass parameters when
On Tue, Jul 20, 2004 at 11:41:14PM +0200, Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Added to TODO:
> >
> > * Allow psql to display permission information using \df+ and
> > \l+
>
> What about, develop a consistent way to display privilege
> information for all objects in psql?
Ex
Bruce Momjian wrote:
> Added to TODO:
>
> * Allow psql to display permission information using \df+ and \l+
What about, develop a consistent way to display privilege information
for all objects in psql?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
Simon Riggs wrote:
> On Sat, 2004-07-17 at 00:57, Bruce Momjian wrote:
> > OK, I think I have some solid ideas and reasons for them.
> >
>
> Sorry for taking so long to reply...
>
> > First, I think we need server-side functions to call when we start/stop
> > the backup. The advantage of these
Added to TODO:
* Allow psql to display permission information using \df+ and \l+
---
Christopher Kings-Lynne wrote:
> > Maybe other people want to comment on this issue.
> >
> > So far, \z and \dp have shown privi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
today I add 4 new columns to a table with 4E+06 rows,
I also update to an initial value these new columns.
The new columns are 3 INTEGER one of type DOUBLE.
The table have also 5 indexes.
Immediately after the operation my partition "data" had
a
Seems it might be time to address this and get it fixed. Win32 doesn't
clean up the directory structure under /data and leave /data unchanged,
and there is no way to do this with a system() command on Win32.
I resisted adding a C version of rmtree during Win32 development because
I was concerned
On Tue, 2004-07-20 at 00:58, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > where the default is and if you specify a target, the default
> > target_in_timeline is .
>
> I think actually the default target has to be the timeline ID found in
> pg_control -- otherwise you get weird
Tom Lane <[EMAIL PROTECTED]> writes:
> Anybody see any holes in this design?
God help the DBA who deletes a history file with needed information. Or edits
it inappropriately.
Why can't every log file contain a header that says which timeline it's part
of and which timeline the preceding log fil
KL,
> CREATE DATABASE phppgadmin WITH TEMPLATE = template0 OWNER = chriskl
> ENCODING = 'LATIN1';
> CREATE DATABASE usa WITH TEMPLATE = template0 OWNER = usadmin ENCODING =
> 'LATIN1';
Ok, so that would come under the heading of "already fixed". Great.
--
Josh Berkus
Aglio Database Solutions
S
Andrew Dunstan wrote:
> To that extent is it not broken by relocated installations that we
> have now made some provision for?
Well, then it should be fixed to take relocated installations into
account.
Relocatable installations are by nature a pretty broken feature. When
you use pg_config to
On Tue, Jul 20, 2004 at 08:32:00AM -0400, Tom Lane wrote:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> >> I think you should first trace down what the problem really is --- is
> >> your system just misconfigured or is there some fundamental issue that
> >> we really ought to answer t
Yeah, I was talking about it on freenode yesterday. If the stats
collector doesn't start, the internal variable is set to off.
Gavin
Gaetano Mendola wrote:
Gavin M. Roy wrote:
I have no problem resolving localhost anywhere else on the box, do
you have any suggestions on finding out if it's a mi
> If localhost isn't being resolved correctly are you seeing error
> messages like this on the server log (from pqcomm.c)?
>
>"could not translate host name \"%s\", service \"%s\" to
> address: %s"
After poking around, I found the following:
The Windows pdc (==name server :-( ) does reall
Andrew Dunstan wrote:
> Peter Eisentraut said:
> > Tom Lane wrote:
> >> I doubt it. People can always just read the file to see what
> >> settings are in it, and it's not like nonexperts are going to have a
> >> variety of different configurations that we're gonna have to ask them
> >> about. (Eve
On Tue, 2004-07-20 at 14:11, Simon Riggs wrote:
> On Tue, 2004-07-20 at 13:51, Tom Lane wrote:
> > Simon Riggs <[EMAIL PROTECTED]> writes:
> > >> The quick and dirty solution would be to dike out the safety check at
> > >> 4268ff.
> >
> > > If you take out that check, we still fail because the w
On Tue, 2004-07-20 at 15:00, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2004-07-20 at 13:51, Tom Lane wrote:
> >> Ugh. I'm beginning to think we ought to revert the patch that added the
> >> don't-split-across-files logic to XLogInsert; that seems to have broken
> >> mor
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2004-07-20 at 13:51, Tom Lane wrote:
>> Ugh. I'm beginning to think we ought to revert the patch that added the
>> don't-split-across-files logic to XLogInsert; that seems to have broken
>> more assumptions than I realized.
> The problem was that
Tom Lane wrote:
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
I think you should first trace down what the problem really is --- is
your system just misconfigured or is there some fundamental issue that
we really ought to answer to?
The trouble on AIX is, that getaddrinfo on
On Tue, 2004-07-20 at 13:51, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> >> The quick and dirty solution would be to dike out the safety check at
> >> 4268ff.
>
> > If you take out that check, we still fail because the wasted space at
> > the end is causing a "record with zero le
Simon Riggs <[EMAIL PROTECTED]> writes:
>> The quick and dirty solution would be to dike out the safety check at
>> 4268ff.
> If you take out that check, we still fail because the wasted space at
> the end is causing a "record with zero length" error.
Ugh. I'm beginning to think we ought to re
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
>> I think you should first trace down what the problem really is --- is
>> your system just misconfigured or is there some fundamental issue that
>> we really ought to answer to?
> The trouble on AIX is, that getaddrinfo only does a nameserv
On Tue, 2004-07-20 at 05:14, Tom Lane wrote:
> Mark Kirkwood <[EMAIL PROTECTED]> writes:
> > I have been doing some re-testing with CVS HEAD from about 1 hour ago
> > using the simplified example posted previously.
>
> > It is quite interesting:
>
> The problem seems to be that the computation o
Peter Eisentraut said:
> Tom Lane wrote:
>> I doubt it. People can always just read the file to see what
>> settings are in it, and it's not like nonexperts are going to have a
>> variety of different configurations that we're gonna have to ask them
>> about. (Even in the Unix world, pg_config is
In article <[EMAIL PROTECTED]>,
Rod Taylor <[EMAIL PROTECTED]> writes:
> On Mon, 2004-07-19 at 12:36, Josh Berkus wrote:
>> Rod,
>>
>> > I think what we want is a clean template without all of the extras that
>> > template1 has.
>>
>> We have this, it's called Template0.
> Doesn't work for me.
Gavin M. Roy wrote:
I have no problem resolving localhost anywhere else on the box, do you
have any suggestions on finding out if it's a misconfiguration?
Gavin
Are you the users on IRC yesterday night ? He had the same problem, however
he/she had the GUC variable stats_start_collector equal to "o
Great that it's not fundamental - and hopefully with this discovery, the
probability you mentioned is being squashed towards zero a bit more :-)
Don't let this early bug detract from what is really a superb piece of work!
regards
Mark
Tom Lane wrote:
In any case this isn't a fundamental bug, jus
On Tue, 2004-07-20 at 05:14, Tom Lane wrote:
> Mark Kirkwood <[EMAIL PROTECTED]> writes:
> > I have been doing some re-testing with CVS HEAD from about 1 hour ago
> > using the simplified example posted previously.
>
> > It is quite interesting:
> The problem seems to be that the computation of
> > Hang on, are you supposed to MOVE or COPY away WAL segments?
>
> Copy. pg will delete them once they are archived.
Copy. pg will recycle them once they are archived.
Andreas
---(end of broadcast)---
TIP 9: the planner will ignore your desire
> > I don't know if the problem is isolated to just me, but I wanted to
> > suggest that we use a parameter for that, which can be configured in the
> > postgresql.conf, with a default value if it's not set, set to
> > localhost.
>
> I think you should first trace down what the problem really
44 matches
Mail list logo
