Gregory Stark napsal(a):
"Simon Riggs" <[EMAIL PROTECTED]> writes:
I wonder how hard it would be to shove the clog into regular shared memory
pages and let the clock sweep take care of adjusting the percentage of shared
mem allocated to the clog versus data pages.
I tried to use memory mapp
Simon Riggs wrote:
On Fri, 2008-01-25 at 17:56 +0100, Zdenek Kotala wrote:
Regarding to Robert Mach's work during Google SOC on data integrity
check. I would like to improve storage module and implement some
Robert's code into the core.
I would like to make following modificatio
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I would like to make following modification:
1) Add ReadBuffer_noerror (recommend me better name) function which will
accept damaged page without Error. This page will be marked as corrupted
and when ReadBuffer will touch thi
Regarding to Robert Mach's work during Google SOC on data integrity
check. I would like to improve storage module and implement some
Robert's code into the core.
I would like to make following modification:
1) Add ReadBuffer_noerror (recommend me better name) function which will
accept damage
Peter Eisentraut wrote:
What about a feature to set a default tablespace just for indexes? I have
been told that this was originally proposed when tablespaces where designed,
but did not end up being implemented. Does anyone recall the details? I
have had people ask me about this feature.
Gevik Babakhani wrote:
After reading the thread of 2004 regarding user quotas, I understand
why the discussion moved towards having a tablespace quota as a
solution.
My reason to start this discussion was due the need of controlling
database size. Having tablespace quotas could allow one to crea
Tom Lane napsal(a):
Comments, opinions?
Is it time to remove old communication protocol support and cleanup code in 8.4?
Zdenek
---(end of broadcast)---
TIP 6: explain analyze is your friend
Tt seems that GCC makes decision do not inline this function and then it
will keep as a standard function. It is not problem and this warning is
generated by -Winline. I don't have this problem with GCC 3.4.3
Zdenek
Thomas Güttler wrote:
Hi,
I get the following compile warnings:
gc
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
Mark Mielke <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
My goodness that's a hardware-dependent proposal. Shall we discuss
how many CPUs there are where an integer division is *slower* than
a floating-point op?
Do you have one in m
Function AllocSetStats uses fprintf instead of standard logging method.
Is there any reason for it? If not I will rewrite it to use
elog(NOTICE,..) instead.
Zdenek
---(end of broadcast)---
TIP 9: In versions below 8.0, the plann
Martijn van Oosterhout napsal(a):
On Wed, Nov 14, 2007 at 09:33:17PM +0100, Zdenek Kotala wrote:
Sure, why not. To be honest I think that psql shouldn't be ignoring the
EISDIR error the kernel is returning.
But it works when you open directory in read-only mode. See posix
definition:
[E
Alvaro Herrera wrote:
Peter Eisentraut wrote:
Letting psql execute a script file that is really a directory doesn't complain
at all:
$ psql -f /tmp
Should we do some kind of stat() before opening the file and abort if it's a
directory?
Actually anything other than a plain file, right? (Do
Martijn van Oosterhout wrote:
On Wed, Nov 14, 2007 at 05:15:20PM -0300, Alvaro Herrera wrote:
Should we do some kind of stat() before opening the file and abort if it's a
directory?
Actually anything other than a plain file, right? (Do we really want to
be able to psql -f a_pipe?)
Sure, why
Magne Mæhre wrote:
I was playing with a Nevada server and noticed a rush on the FPU
(the Nevada has a single shared FPU for its 32 threads).
Probably you mean Niagara ;-).
Zdenek
---(end of broadcast)---
TIP 1: if posting/readi
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
I think the first step is to install the zic binary along the rest of
the stuff, so that a user without the source tree can compile the tzdata
package. Unless the compiled representation is portable, which I kinda
doubt?
Actually, it
Zdenek Kotala wrote:
Attached patch removes pg_dump dependency on postgres.h. The main reason
for that was discussed there:
http://archives.postgresql.org/pgsql-hackers/2007-10/msg01261.php
I found two problems there. One is that I forgot postgres.h include in
common.c. it is easy to fix
Heikki Linnakangas wrote:
David BOURIAUD wrote:
Le vendredi 9 novembre 2007, vous avez écrit :
David BOURIAUD wrote:
if the run-time option is chosen, any message issued by any command,
from
connexion to all sql commands launched in any way by a user should
go in
a separate log file, that co
Andrew Dunstan wrote:
Zdenek Kotala wrote:
Alvaro Herrera wrote:
I think the first step is to install the zic binary along the rest of
the stuff, so that a user without the source tree can compile the tzdata
package. Unless the compiled representation is portable, which I kinda
doubt
Magnus Hagander wrote:
On Fri, 2007-11-09 at 09:25 -0300, Alvaro Herrera wrote:
Magnus Hagander wrote:
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Zdenek Kotala wrote:
I think we need some different mechanism how to deliver timezone updated.
Even when the system TZ
Alvaro Herrera wrote:
I think the first step is to install the zic binary along the rest of
the stuff, so that a user without the source tree can compile the tzdata
package. Unless the compiled representation is portable, which I kinda
doubt?
Maybe wild idea, what's about use buildfarm to up
David BOURIAUD wrote:
if the run-time option is chosen, any message issued by any command, from
connexion to all sql commands launched in any way by a user should go in a
separate log file, that could be named log.username for example.
You can enable logging user name into postgres log and gr
Tom Lane wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
On Fri, 2007-11-09 at 02:26 -0500, Tom Lane wrote:
Plan B would be to take out contracts on all the banana-republic
politicians who think that changing DST laws with a month's notice
is a pleasant pastime. I fear we lack the resources
Devrim GÜNDÜZ napsal(a):
Hi,
ftp://elsie.nci.nih.gov/pub/tzdata2007i.tar.gz
Per announcement:
"...is now available; this reflects changes for Cuba and Syria
circulated earlier this week on the time zone mailing list.
There are no code changes, so there's no tzcode2007i; tzcood2007h
remains cu
Tom Lane wrote:
A better solution might be to move the declarations of
SEQ_MINVALUE/SEQ_MAXVALUE someplace else.
Hmm. It seems better, but it is also hard to find correct place. :( I'm
thinking put it into c.h.
Another question why sequence does not have separate flag which
determines if
I'm trying fix independence of pg_dump.c on postgres.h. And I found
following construct in dumpSequence function:
09391 snprintf(bufm, sizeof(bufm), INT64_FORMAT, SEQ_MINVALUE);
09392 snprintf(bufx, sizeof(bufx), INT64_FORMAT, SEQ_MAXVALUE);
09393
09394 appendPQExpBuffer(query,
093
Joshua D. Drake wrote:
x86_64 is x86_64, regardless of intel or amd.
Not exactly, ask kernel guys ;-). But for user space yes.
Zdenek
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
My idea is to put functions declaration int pg_xxx.h and structure
declaration in pg_xxx_def.h. I'm not sure if split DATA into separate
header is good idea, but if yes then pg_xxx_data.h should be good name
for it (it seems t
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
One solution should be put sugar words into separate header and include
them directly from catalog/*.h files.
Yeah, that would probably be a good idea. It's unlikely that we'll
get away anytime soon from frontend
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Why in the world is ecpg including either primnodes.h or postgres.h?
The problem is that ecpg shares parser.c source code and this code
includes postgres.h.
ecpg cannot do that. It would fail if parser.c ha
Zdenek Kotala wrote:
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
By my opinion Datum should be defined in separate file and all
headers which use this type should include it. (this is problem on
many places with another types). Another question is why ecpg needs it?
Da
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I fixed it for zic, but problem with ecpg is that it includes
nodes/primnodes.h and it requires Datum type definition which is defined
in postgres.h. :(
Why in the world is ecpg including either primnodes.h or postgres.h?
Peter Eisentraut wrote:
Am Donnerstag, 25. Oktober 2007 schrieb Zdenek Kotala:
I fixed it for zic, but problem with ecpg is that it includes
nodes/primnodes.h and it requires Datum type definition which is defined
in postgres.h. :(
I don't find an inclusion of primnodes.h in ecpg. Which
I'm trying to solve one TODO item mentioned in
src/backend/utils/mmgr/mcxt.c.
/*
* MemoryContextSwitchTo
* Returns the current context; installs the given context.
*
* This is inlined when using GCC.
*
* TODO: investigate supporting inlining for some non-GCC compilers.
*
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Is there any reason to have both these macros? By my opinion
MaxHeapTuplesPerPage is more accurate and it should replace all
MaxOffsetNumber occurrence.
We use MaxOffsetNumber with index pages as well.
I forgot to indexes, but there is
Is there any reason to have both these macros? By my opinion
MaxHeapTuplesPerPage is more accurate and it should replace all
MaxOffsetNumber occurrence.
Any comments?
Zdenek
http://doxygen.postgresql.org/htup_8h.html#c8829334a53a69e12b070bf09b7b7ab7
http://doxygen.post
Bruce Momjian wrote:
Zdenek Kotala wrote:
There are a lot of incoming DST or TZ changes (Venezuela, Brazil,
Indiana...). Most hot is Indiana which will happen at 4th Nov.
http://www.worldtimezone.com/dst_news/dst_news_usa02.html
Is there any schedule to release new minor versions? It seems
There are a lot of incoming DST or TZ changes (Venezuela, Brazil,
Indiana...). Most hot is Indiana which will happen at 4th Nov.
http://www.worldtimezone.com/dst_news/dst_news_usa02.html
Is there any schedule to release new minor versions? It seems that new
Olson database is in CVS repository
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
FWIW I tried this program here, and I get
C ... ANSI_X3.4-1968 - NO MATCH
POSIX ... ANSI_X3.4-1968 - NO MATCH
Note the funny name. Trying initdb with LC_ALL=C correctly uses
SQL_ASCII (I saw
Tom Lane wrote:
If this is what's happening I'd claim it is a kernel bug, but seeing
that I see it on FC6 and Miya sees it on Solaris 10, it would be a bug
widespread enough that we'd not be likely to get it killed off soon.
I think my colleague was solving similar issue in JavaDB. IIRC the
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
On Solaris I got following problematic locales:
C ... 646- NO MATCH
POSIX ... 646- NO MATCH
cs ... 646- NO MATCH
da .
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
Another possibility is to treat the case as a WARNING if you're
superuser and an ERROR if you're not. This would satisfy people
who are uncomfortable with the idea that CREAT
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
I'm Sorry for confusion, I overlooked it. You have right. Unfortunately
struct Port has been modified and by my opinion it means we must bump
major version. See
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/libpq-be.h.di
Stephen Frost wrote:
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
I'm for bumbing. Because if we use same number it also means that new
binary will able to use old library. But if there are two new functions
number must be increased. Standard practice how ELF loader works is
following:
Eac
Tom Lane wrote:
We're so close I can almost taste it ... Here are the open tasks
I can see, does anyone have others?
* Pending patches for pre-existing bugs in contrib/pgcrypto --- this
doesn't seem like a beta-stopper anyway.
I agree It is not show stooper for beta. In emergency ca
Tom Lane wrote:
Stephen Frost <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
* Do we bump the .so major version number for libpq? I think we should
because there are two new exported functions since 8.2, and on at least
some platforms there's nothing else than major number to disambigu
Mark Wong wrote:
On 9/25/07, Satoshi Nagayasu <[EMAIL PROTECTED]> wrote:
Mark,
Very interesting. I'm looking for such tool.
Unfortunately, I can't compile it on my Solaris right now,
but I hope it will be shipped with PostgreSQL distribution.
I haven't tried it on Solaris but I'm not surpris
Andrew Dunstan wrote:
Zdenek Kotala wrote:
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
We previously discussed compressing the numeric data type for small
values:
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php
We didn't do this for 8.3
Stefan Kaltenbrunner wrote:
Bruce Momjian wrote:
Just confirming, this should be applied to 8.3, right?
I think marko is working on an updated patch for this:
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00386.php
without that the backend will coredump if ones uses string ciphers
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
We previously discussed compressing the numeric data type for small values:
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php
We didn't do this for 8.3 but in any case Tom did suggest we ought to reverse
the weight and
Gregory Stark napsal(a):
"Zdenek Kotala" <[EMAIL PROTECTED]> writes:
Just for information. Venezuela is going to have new timezone change (30minutes
shift) on this weekend. This change is not yet integrated in the last version
in Olson database. (Original announcement sa
Just for information. Venezuela is going to have new timezone change
(30minutes shift) on this weekend. This change is not yet integrated in
the last version in Olson database. (Original announcement said it
happens on 1.1.2008)
More info:
http://www.reuters.com/article/oddlyEnoughNews/idUSN2
Marko Kreen wrote:
On 9/11/07, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
Marko Kreen wrote:
This is crashing because of the crippled OpenSSL on some version
of Solaris. Zdenek Kotala posted a workaround for that, I am
cleaning it but have not found the time to finalize it.
I'll
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I have a question about what does happen if search path is not defined
for SECURITY DEFINER function. My expectation is that SECURITY DEFINER
function should defined empty search patch in this case.
Your expectation is incorrec
rippled OpenSSL on some version
of Solaris. Zdenek Kotala posted a workaround for that, I am
cleaning it but have not found the time to finalize it.
I'll try to post v03 of Zdenek's patch ASAP.
However, I guess there still will be a problem with regression tests,
because pg_crypto wil
Tom Lane wrote:
I thought about ways to include GUC settings directly into CREATE
FUNCTION, but it seemed pretty ugly and inconsistent with the
existing syntax. So I'm thinking of supporting only the above
syntaxes, meaning it'll take at least two commands to create a secure
SECURITY DEFINER f
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zdenek Kotala wrote:
Peter Eisentraut wrote:
I'm having trouble with the hardcoded 60 second timeout in pg_ctl.
pg_ctl sometimes just times out and there is no way to make it wait a
little longer. I would like to a
Peter Eisentraut wrote:
Zdenek Kotala wrote:
Let me know if there something what should be adjusted on my patch. I
would like to do it tomorrow, because I will be offline for next two
weeks.
I can try to fit your patch into what's there now, if you'd rather just
start your
Peter Eisentraut wrote:
I'm having trouble with the hardcoded 60 second timeout in pg_ctl. pg_ctl
sometimes just times out and there is no way to make it wait a little longer.
I would like to add an option to be able to change that, say
pg_ctl -w --timeout=120. Comments?
+1
I played with
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
FWIW, hardwiring plus an environment variable would seem to address all
currently known und unknown requirements, and is not so totally
different from solutions to previous, related problems.
I think we are converging on the recogni
Alvaro Herrera wrote:
It would be even better to use --with-system-tzdata=/usr/share/zoneinfo
which enables lookup in the specified dir, hardwired at compile time in
the executable (I'm not aware if the patch already accepts a path
argument -- seems like the only sane choice). No symlink neede
Tom Lane wrote:
I think we've already found out that the opinions *aren't* equal.
So far the score seems to be:
Red Hat: will use relative symlink
Solaris: will use hardwired path in program
Finally, Because my original patch has not been accepted, Solaris also
use relative s
Tom Lane wrote:
[ catching up on today's email ]
Gregory Stark <[EMAIL PROTECTED]> writes:
Why would --with-zoneinfo want to use a symlink though? Shouldn't it just
compile the binary to use the path specified directly?
AFAICS that just moves the problem to a different place, one where an
a
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
Why would --with-zoneinfo want to use a symlink though? Shouldn't it just
compile the binary to use the path specified directly? Symlinks are fine for a
sysadmin or a packager but if it's going to be supported by Postgres code
direc
Andrew Dunstan wrote:
Zdenek Kotala wrote:
The problem what Dhanaraj tries to address is how to secure solve
problem with PAM and local user. Other servers (e.g. sshd) allow to
run master under root (with limited privileges) and forked process
under normal user. But postgresql
requires
Andrew Dunstan wrote:
Dhanaraj M wrote:
The non-root user does not have the permission to read other unix
local user password.
I found two solutions:
1. usermod -K defaultpriv=Basic,file_dac_read postgres
- Gives privilege to read all files. This solution works. Is it the
right way t
I'm comparing now different version of page layer, and I have two questions:
1) We now store only low 16bits TLI, but name in structure stays same.
Maybe pg_tli_lo could be better.
2) HASOID has been moved in infomask and original place is unused. Is
there some reason for that? This change li
Hans-Juergen Schoenig napsal(a):
the idea is basically to hide codes - many companies want that and ask
for it again and again.
i would suggest keys to reside in $PGDATA. we do this for SSL and so
already.
initdb could create such keys so that they are unique to every database
instance.
dec
Stefan Kaltenbrunner wrote:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lionfish&dt=2007-07-24%2005:30:13
any ideas ?
This test is very sensitive to floating point operations behavior. Any
gcc, libc update on this machine?
Zdenek
---(e
Marko Kreen wrote:
On 7/24/07, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
However, on default installation (which is commonly used) it is a
problem. Regression test cannot be fixed because it tests strong
ciphers, but there two very strange issue:
1) First issue is blowfish cipher. B
Stefan reported me that prcrypto regression test fails on solaris 10
with openssl support. I investigated this problem and the result is that
Solaris 10 delivers only support for short keys up to 128. Strong crypto
(SUNWcry and SUNWcryr packages) is available on web download pages. (It
is resul
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
E_FUNC_HAS_NO_RETURN_STMT is there because main is leaved by exit() instead
return. And In another case It should be regular warning.
That should be gone now; I changed the two places that triggered it.
I'd suggest no
Stefan Kaltenbrunner napsal(a):
Zdenek Kotala wrote:
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
For sun studio -erroff=E_STATEMENT_NOT_REACHED is useful there. If you
want to determine warning tags for each warning add -errtags.
Is
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
For sun studio -erroff=E_STATEMENT_NOT_REACHED is useful there. If you
want to determine warning tags for each warning add -errtags.
Is that supported on all versions of sun studio(Sun WorkShop
Stefan Kaltenbrunner wrote:
I just took a look at adding gssapi build support on solaris (solaris
10/x86_64, sun studio 10, 64bit build) which seemed easy enough by
educating configure to look for -lgss but while it compiles just fine
the resulting tree will not be able to complete a make check d
Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
Zdenek Kotala wrote:
I don't see any "const" keyword there.
Right after that:
where int conv(int num_msg, const struct pam_message **msg, struct pam_response **resp, void *appdata_ptr);
How confusing..
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
If I look there
http://www.opengroup.org/onlinepubs/008329799/chap5.htm#tagcjh_06
in "Call Back Information" section. The structure is defined as
struct pam_conv{ int (*conv) (int, struct pam_message **, struct
pam_respons
Kris Jurka wrote:
On Fri, 13 Jul 2007, Zdenek Kotala wrote:
Tom Lane wrote:
Kris Jurka <[EMAIL PROTECTED]> writes:
So pam_message ** isn't const.
Ah, thanks. I see luna_moth is giving the same warning, so it's still
not const in Solaris 11 either.
Is it worth working ar
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
For sun studio -erroff=E_STATEMENT_NOT_REACHED is useful there. If you
want to determine warning tags for each warning add -errtags.
Is that supported on all versions of sun studio(Sun WorkShop 6, Sun
Studio 8,11) we have on the farm ?
Yes
Tom Lane wrote:
Kris Jurka <[EMAIL PROTECTED]> writes:
So pam_message ** isn't const.
Ah, thanks. I see luna_moth is giving the same warning, so it's still
not const in Solaris 11 either.
Is it worth working around this? It's strictly cosmetic AFAICS.
The main issue in my mind would be how
Stefan Kaltenbrunner wrote:
Peter Eisentraut wrote:
Am Donnerstag, 12. Juli 2007 15:25 schrieb Stefan Kaltenbrunner:
a lot of those are simply noise (like the LOOP VECTORIZED stuff from the
icc boxes or the "statement not reached" spam from the sun compilers)
but others might indicate real issu
Kris Jurka wrote:
On Thu, 12 Jul 2007, Tom Lane wrote:
static int pam_passwd_conv_proc(int num_msg, const struct pam_message
** msg,
struct pam_response ** resp, void *appdata_ptr);
which exactly matches what my Fedora 6 pam header file says it should
be. What is it on
Martijn van Oosterhout wrote:
On Tue, Jul 03, 2007 at 09:51:59PM -0400, Tom Lane wrote:
Out-of-line datums aren't the only issue, either: consider inline
compressed datums. A data representation change, even one that is known
not to increase the ordinary uncompressed size of the datum, could
ea
Tom Lane wrote:
I do not expect that old code will work with new index structure. I want
to keep both implementation and old index will be processed by old code
and new one will be processed by new implementation. Each will have
different OID and pg_class.relam will point to correct implemen
Tom Lane wrote:
Again, you are setting yourself up for complete failure if you insist
on having every possible nicety in the first version. An incremental
approach is far more likely to succeed than a "big bang".
Yes, I know. I don't want to solve everything in one patch. I just
looking for
Martijn van Oosterhout wrote:
On Tue, Jul 03, 2007 at 07:13:29PM +0200, Zdenek Kotala wrote:
pg_migrator is separate tool which requires old postgres version and I
would like to have solution in postgres binary without old version
presence. Very often new postgres version is store in same
Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
My thinking is that when a page in the old format is read in, it's
converted to the new format before doing anything else with it.
Yeah, I'm with Heikki on this. What I see as a sane project definition
is:
* pg_migrator or equiva
Martijn van Oosterhout wrote:
On Tue, Jul 03, 2007 at 12:05:07PM +0100, Heikki Linnakangas wrote:
This is actually a bit of a problem. We would need to know when we
read in a page what the tupledescriptor for that relation looks like
to know which fields are varlena. I'm not sure how easy it wou
Heikki Linnakangas wrote:
Gregory Stark wrote:
Conceivably we could grab another infomask bit to indicate "uses
new-style
varlenas" and then have heaptuple.c understand how to convert them in
place.
But that leads to a ton of memory management or page locking problems.
My thinking is tha
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Project Goals
-
...
3) Do not require an old version of PostgreSQL to be installed.
Why not? Having two versions installed at the same time doesn't seem
like a problem to me. You can remove the old version as soon as the
upgrade is
I attach In-Place upgrade project concept. Any technical details about
implementation of each part will be sent later (after concept acceptance).
Please, let me know your comments.
thanks Zdenek
In-place Upgrade project
---
Overview
PostgreSQL com
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I would like to inform, that New Zealand changed DST rules and new
timezone files are available. See
http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Daylight-saving-to-be-extended
Patch for head attached
I would like to inform, that New Zealand changed DST rules and new
timezone files are available. See
http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Daylight-saving-to-be-extended
Patch for head attached. I kept zic.c untouched, but I think it would be
nice to update it
Heikki Linnakangas wrote:
Since we're discussing upgrades, let me summarize the discussions we had
over dinner in Ottawa for the benefit of all:
Thanks for summary.
As before, someone just needs to step up and do it.
I'm now working on proposal. I hope that it will ready soon.
Andrew Sullivan wrote:
On Wed, Jun 20, 2007 at 12:34:21PM -0400, Robert Treat wrote:
FWIW pg_migrator is a pretty good swing at an in-place upgrade tool for
8.1->8.2. Unfortunately until the PGDG decides that in-place upgrade is a
constraint their willing to place on development, I see them a
Simon Riggs wrote:
The objections to applying this patch originally were:
1. it changes on-disk format (we've done this, so argument is void)
I'm little bit confused when we introduce new page layout version? I
expect that new version become with changes with pageheader, tuple
header or dat
David Fetter wrote:
On Fri, Jun 08, 2007 at 08:12:22PM -0500, Jim C. Nasby wrote:
On Tue, Jun 05, 2007 at 05:52:39PM -, Andrew Hammond wrote:
On Jun 5, 9:19 am, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
Zdenek Kotala wrote:
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> write
Magnus Hagander wrote:
On Tue, Jun 12, 2007 at 12:23:50PM +0200, Zdenek Kotala wrote:
Alvaro Herrera wrote:
Zeugswetter Andreas ADI SD escribió:
The launcher is set up to wake up in autovacuum_naptime
seconds
at most.
Imho the fix is usually to have a sleep loop.
This is what we have. The
Alvaro Herrera wrote:
Zeugswetter Andreas ADI SD escribió:
The launcher is set up to wake up in autovacuum_naptime
seconds
at most.
Imho the fix is usually to have a sleep loop.
This is what we have. The sleep time depends on the schedule
of next vacuum for the closest database in time. If
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Is this a TODO?
I don't think so; there is no demand from anybody but Zdenek to remove
those programs. Has it ever even come up before?
Tom, Bruce
I started with postgres 6.5 as administrator and from this version names
of these u
Tom Lane napsal(a):
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Zdenek Kotala wrote:
And what about replace all "scripts" by one command e.g pg_cmd with
following interface:
Well, I don't think rolling up the miscellaneous commands into a single
binary with behaviour dep
501 - 600 of 703 matches
Mail list logo
