Andrew Dunstan píše v po 08. 02. 2010 v 20:07 -0500:
>
> Our Solaris *moth members seem to have stopped building. Have we lost them?
Hi Andrew,
The answer is not simple. Yes, we lost Solaris 8 and 9 machines which
was reinstalled and now they are used for different purpose. It was
planned befor
I revived codlin_month and it falls during PL/Python test:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=codlin_moth&dt=2010-02-16%2015:09:05
TRAP: BadArgument("!(((context) != 0 && (Node*)((context)))->type)
== T_AllocSetContext", File: "mcxt.c", Line: 641)
feaf5005 _lwp_kill
Dne 17.02.10 18:39, Peter Eisentraut napsal(a):
On ons, 2010-02-17 at 11:26 -0500, Tom Lane wrote:
But the behavior gcc appears to exhibit is that it won't warn about
variables that are only assigned once before the PG_TRY is entered,
and that seems reasonable to me since such a variable ought t
Hi all,
I got following stack:
fd7ffed14b70 strlen () + 40
fd7ffed71665 snprintf () + e5
fd7fff36d088 pg_GSS_startup () + 88
fd7fff36d43a pg_fe_sendauth () + 15a
fd7fff36e557 PQconnectPoll () + 3b7
fd7fff36e152 connectDBComplete () + a2
fd7fff36dc32 PQsetdbLogi
Magnus Hagander píše v čt 25. 02. 2010 v 15:17 +0100:
> On Thu, Feb 25, 2010 at 15:04, Zdenek Kotala wrote:
> > Hi all,
> >
> > I got following stack:
> >
> > fd7ffed14b70 strlen () + 40
> > fd7ffed71665 snprintf () + e5
> > fd7fff36d088
Magnus Hagander píše v po 01. 03. 2010 v 16:55 +0100:
> 2010/3/1 Zdenek Kotala :
> > Magnus Hagander píše v čt 25. 02. 2010 v 15:17 +0100:
> >> On Thu, Feb 25, 2010 at 15:04, Zdenek Kotala wrote:
> >> > Hi all,
> >> >
> >> > I got following
Hi Tom,
I'm sorry that I did not look on it early. I played with it and there
are some facts. gothic(sparc) and codlin(x86) uses Sun Studio 12 nad I
setup them to use very high optimization.
Gothic:
---
-xalias_level=basic -xarch=native -xdepend -xmemalign=8s -xO5
-xprefetch=auto,explici
Dne 11.03.10 16:24, Greg Stark napsal(a):
On Wed, Mar 10, 2010 at 11:37 PM, Tom Lane wrote:
My conclusion is that this is probably a compiler bug. Both buildfarm
animals appear to be using Sun Studio, although on different
architectures which weakens the compiler-bug theory a bit. Even though
Dne 11.03.10 17:37, Tom Lane napsal(a):
Zdenek Kotala writes:
"-xO4 -xalias_level=basic" generates problem.
"-xO3 -xalias_level=basic" works fine
"-xO5" works fine
As documentation say:
Cite from Sun studio compiler guide:
http://docs.sun.com/app/
Tom Lane píše v čt 11. 03. 2010 v 11:37 -0500:
> Zdenek Kotala writes:
> > "-xO4 -xalias_level=basic" generates problem.
> > "-xO3 -xalias_level=basic" works fine
> > "-xO5" works fine
>
> > As documentation say:
>
> > Cite
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=comet_moth&dt=2010-05-13%2021:06:01
msgfmt -o po/ja.mo po/ja.po
WARNING: the string after closing " is ignored at line number 11.
Error, No space after directive at line number 2008.
ERROR: Exiting...
gmake[2]: *** [po/ja.mo] Error 2
The problem
Takahiro Itagaki píše v pá 14. 05. 2010 v 19:38 +0900:
> Zdenek Kotala wrote:
>
> > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=comet_moth&dt=2010-05-13%2021:06:01
> > The problem is that it contains mix of DOS/Unix end of lines.
>
> I removed two CRs in ja
Zoltan Boszormenyi wrote:
Hi,
we have found that psql in PostgreSQL 8.2.3
has problems connecting to the server
running on Solaris 10/Sun SPARC.
$ uname -a
SunOS dev-machine 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V440
It seems that somehow the system provided
GCC 3.4.3 miscompiles ti
Zoltan Boszormenyi wrote:
We compiled GCC-4.1.2 on this machine, recompiled PostgreSQL
with the new GCC without --enable-integer-datetimes and it fixed
the problem we experienced. It seems that my suspicion was right:
GCC-3.4.3 on Solaris 10/Sparc is buggy.
I tried original S10 gcc (3.4.3) o
I'm looking on pid file creation code (src/backend/utils/init/miscinit.c
- CreateLockFile) and I have couple of questions:
1) Is there still some reason have negative value in postmaster.pid? It
happens only if backend runs in single mode. But I think now is not
necessary to use it. And there
Alvaro Herrera wrote:
Can I declare a struct in a function's declaration section? Something
like this:
static void
foobar(void)
{
struct foo {
Oid foo;
int bar;
};
struct foo baz;
baz.foo = InvalidOid;
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
1) Is there still some reason have negative value in postmaster.pid?
Just to distinguish postmasters from standalone backends in the error
messages. I think that's still useful.
I'm not sure what you mean. It
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Just to distinguish postmasters from standalone backends in the error
messages. I think that's still useful.
I'm not sure what you mean. It is used only in CreatePidFile function
and I think that
Tom Lane wrote:
[ redirecting to -hackers for wider comment ]
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
LET_OS_MANAGE_FILESIZE is good way. I think one problem of this option I
fixed. It is size of offset. I went thru the code and did not see any
other problem there. H
Tom Lane wrote:
Jim Nasby <[EMAIL PROTECTED]> writes:
If we expose LET_OS_MANAGE_FILESIZE, should we add a flag to the
control file so that you can't start a backend that has that defined
against a cluster that was initialized without it?
I imagine we'd flag that as relsegsize = 0 or some s
Heikki Linnakangas wrote:
That's a clever trick, but I can't help thinking we really should have
an explicit field in the page header to indicate what kind of a page it
is. It would make life simpler for any external tools that want to peek
into pages, including migration utilities after a r
Dave Page wrote:
In my original message I described my thinking:
- Developer submits patch, with additional info through a web interface.
- The web interface formats an email containing the patch description,
patch and any other info entered, assigns it a patch number, and
forwards it to the
Dave Page wrote:
Stefan Kaltenbrunner wrote:
This means that there is a huge rush of new code in pgAdmin's
development cycle, right at the time when we should be testing - making
the release process more and more rushed as each release of PostgreSQL
gets more efficient and adds more and more new
Tom Lane wrote:
[ redirecting to -hackers for wider comment ]
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
LET_OS_MANAGE_FILESIZE is good way. I think one problem of this option I
fixed. It is size of offset. I went thru the code and did not see any
other problem there. H
See http://www.postgresql.org/docs/8.2/interactive/storage.html
in code it is for example in
src/backend/storage/...
src/backend/utils/adt/...
src/backend/access/...
and very good also is
src/include/stroage/bufpage.h
I hope it helps
Zdenek
jorge alberto wrote:
Hello!
I w
Heikki Linnakangas wrote:
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Heikki Linnakangas wrote:
Any suggestions? pgdiagnostics?
Yes, I like "diagnostics", or "internals". I just think forensics isn't
going to be understood by the average native English speaker, let alone
non-
Heikki Linnakangas wrote:
I'm going to go with pgdiagnostics. We could short it to just "pgdiag",
but that feels too short :). We could make it "pgdiagfuncs", but that's
not much shorter than pgdiagnostics.
pgdiagfn? It is only 8 chars length ;).
Zdenek
---(
Tom Lane wrote:
We can fix this for gcc by putting __attribute__((noreturn)) on the
declaration of pg_re_throw(), but what about other compilers?
Sun studio also complains about it :(.
Zdenek
---(end of broadcast)---
TIP 5: don
Zdenek Kotala wrote:
Tom Lane wrote:
We can fix this for gcc by putting __attribute__((noreturn)) on the
declaration of pg_re_throw(), but what about other compilers?
Sun studio also complains about it :(.
I'm sorry it was to late for me, I recheck it again and Sun studio is
I would like to add one point:
Bruce Momjian wrote:
Patch committers check several things before applying a patch:
1) Follows the SQL standard or community agreed-upon behavior
2) Style merges seamlessly into the surrounding code
3) Written as simply and efficiently as possible
4) Uses th
Neil Conway wrote:
So, are there any corresponding benefits to providing both FP and
integer datetimes? AFAIK the following differences in user-visible
behavior exist:
There should be also problem with floating point implementation on
client and server side. For example if somebody use float
Bruce Momjian wrote:
Neil Conway wrote:
On Sat, 2007-05-05 at 20:52 -0400, Bruce Momjian wrote:
What? We don't pass float as a binary to clients.
Sure we do, if the client is sending or receiving data in binary format.
But in those cases, we assume the client and server have the same
config
Jim Nasby wrote:
People have suggested different trackers that have varying amounts of
email capability, but I don't think any of them have had the full
capability that we'd need. At best they might accept comments on a
bug/issue via email, but to work for the community they'd need to go
bey
I'm looking into PG/PLSql code and following code in
plpgsql_call_handler looks strange:
/* Find or compile the function */
func = plpgsql_compile(fcinfo, false);
/* Mark the function as busy, so it can't be deleted from under
us */
func->use_count++;
I don't
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I'm looking into PG/PLSql code and following code in
plpgsql_call_handler looks strange:
/* Find or compile the function */
func = plpgsql_compile(fcinfo, false);
/* Mark the function as busy,
Heikki Linnakangas napsal(a):
Jim C. Nasby wrote:
There is two counters for checkpoints in pgstats, the number of timed
(triggered by checkpoint_timeout) and requested (triggered by
checkpoint_segments) checkpoints.
Maybe we should improve the stats system so that we can collect events
w
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Zdenek
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
Yes ... Never mind
What's about
- full page writes improvement
but I will have time
Ron Mayer wrote:
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, "Oh, yea, I need to do that".
Would it inspire more people to learn enough to become patch
reviewers if patch authors scheduled walkthroughs of their
pa
Robert Mach wrote:
I see different ways of delivering this functionality to Postgresql. The
best of course would be to become part of Postgresql release either as a
PostgreSQL command (like UPDATE) or as an postgresql server application
like vacuumdb.
Other possibility is to create a freesta
Richard Huxton wrote:
Zdenek Kotala wrote:
3) My personal favorite is create management console - which allows to
perform check without physically access to local machine. Management
console should be use for another purpose - for example disable/enable
databases from cluster, perform upgrade
Richard Huxton wrote:
Zdenek Kotala wrote:
Richard Huxton wrote:
For the rest, that's what ssh is for imho.
And what you will do when you don't have ssh access on this machine
and 5432 is only one way how to administrate a server? (Windows is
another story.)
If I've not
Sahoo, Ranjan Rashmi wrote:
Hi All,
I am new to this postgres and now struggling with creation of a user
specific to a database, so the user can login to that specific database
and can do the activities as per the given credentials and can not touch
or see any information from other da
Grant Finnemore napsal(a):
CrashReporter trace:
Date/Time: 2007-05-31 10:21:39.285 +0200
OS Version: 10.4.9 (Build 8P2137)
Report Version: 4
Command: postmaster
Path:./bin/postmaster
Parent: postmaster [23091]
Version: ??? (???)
PID:23096
Thread: 0
Exception: EXC_BAD_ACCES
Peter Eisentraut wrote:
The messages output by the "scripts" always seemed unnecessary to me, e.g.,
$ createdb foo
CREATE DATABASE
A Unix program (hi Magnus) shouldn't need to say anything if the requested
action succeeded.
I believe the history of this output is actually that these scripts
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Zdenek Kotala wrote:
And what about replace all "scripts" by one command e.g pg_cmd with
following interface:
pg_cmd create database <...>
And we'll break a million applications that rely on the command
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
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
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
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
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
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
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
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.
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
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 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
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
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
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
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 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:
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
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
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
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
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
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
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
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..
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
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
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 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
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 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
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 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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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:
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
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
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
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
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
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
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
1 - 100 of 703 matches
Mail list logo
