On Wed, Jun 11, 2008 at 6:56 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
>> On Mon, Jun 2, 2008 at 5:46 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>>
>> > pg_ctl -D data check?
>> >
>> > I would +1 that.
>>
>&
On Tue, Jun 10, 2008 at 4:51 PM, Alvaro Herrera
<[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
>> Right, but shouldn't we always output something we know we can read
>> back in (unambiguously), assuming a server with no user defined
>> abbreviations?
>
> Tha
On Tue, Jun 10, 2008 at 4:37 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
>> It seems like a bug that we happily output PKST as a timezone (in a
>> 'timestamp with time zone'), but won't accept it ba
tput PKST as a timezone (in a
'timestamp with time zone'), but won't accept it back in. Perhaps we
should only output names that we can read back, and revert to a
numeric offset in other cases?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hacke
es are valid, as
>> someone
>> else mentioned elsewhere in this thread.
>
> pg_ctl -D data check?
>
> I would +1 that.
I would also really like to see that - though I'd also like to see an
SQL interface so we can check a config before saving when editing via
pgAdmin or simi
On Thu, May 29, 2008 at 4:52 PM, Dave Page <[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 4:45 PM, Justin <[EMAIL PROTECTED]> wrote:
>>
>> Then what is the purpose of shared buffers if nothing is being reused is it
>> only used to keep track locks, change
ink the idea is that WAL records would be shipped (possibly via
> socket) and applied as they're generated, rather than on a
> file-by-file basis. At least that's what "real-time" implies to me...
Yes, we're talking real-time streaming (synchronous) log shipping.
--
Da
a structures), not query results.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
erned about the back
> branches where testing isn't as complete.
We'll find out in a few hours.
My guess is that anyone happy to be running such an old version of
gettext is probably running old versions of everything, including PG.
Your case is obviously a little different.
--
having it always on.
Sounds reasonable to me.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tried it, and
> then wouldn't be surprised if it behaved either way :-)
It pre-allocates the space as copy does. And yes, I did test :-p
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
he required space for the file it's
copying, thus checking the file size to verify that the copy has
completed is not a valid test.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
not enough space.
As I read it, each node takes the value of the largest child, not the
sum of the children.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
g00131.php
Patch queue -> Wiki]
To link to another wiki page, put the target page title in double
square brackets
[[Developer and Contributor Resources]]
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
gets 5
threads that's not a huge chore).
I see no reason to go manually copying all 2k emails to the wiki.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
emails should not rely on
> external domains. That way the project is in control, not the other way
> around.
The company domain is from the message id by the looks of it - it
should not be changed under any circumstances.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
Pos
On Tue, Mar 18, 2008 at 11:48 AM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Dienstag, 18. März 2008 schrieb Dave Page:
>
> > I was actually thinking of the OS X buildfarm member I setup to
> > exercise this. From your description it sounded like we need to
>
o explain the details to someone who does.
I was actually thinking of the OS X buildfarm member I setup to
exercise this. From your description it sounded like we need to
generate the probe header manually if we enable dtrace.
I'm sure Magnus would love to hear the details for the MSVC perl sc
in the buildfarm to create the header file?
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
onical name = distrib-coffee.ipsl.jussieu.fr.
Name: distrib-coffee.ipsl.jussieu.fr
Address: 134.157.176.20
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
't see any reason why what Greg & Josh are suggesting couldn't
work - it's roughly what I had in mind anyway, except that we'd have
to use a URL rewrite on developer to get it to redirect requests to
wiki, as that hostname is used for other things so hijacking DNS
doesn'
per wiki
into a dedicated area on it.
Any thoughts on whether thats a good or bad idea? Any objections?
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
x27;t account for problems discovered post-release.
>
> It is a best effort with our limited resources.
Should we outsource it? It is user-facing :-p
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-ha
ak at a
specific point, I sometimes add a loop to the code along the lines of:
int x=0;
while (!x)
Sleep(100);
When the backend hits that point, attach the debugger, break
execution, and set x to a value in the locals window. Then you can
step through the code from that point.
--
Dave
es ;)
We are - but the idea doesn't need to be on the list for us to
consider it. Just write up a good project outline and plan ready to
submit when the doors open.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
-
help to many people's
>
> Comments from others? Objections?
If it's well documented which versions of MSVC++ work with it, and
which versions of ossp-uuid, I don't see it as a major problem to
include it. It's annoying for sure, but it's not the end of the worl
On Mon, Feb 25, 2008 at 11:48 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
> > Yes, because newer builds may be linked against updated runtime
> > versions. We need to be sure the installer will upgrade the file so it
> > definitely mat
On Mon, Feb 25, 2008 at 10:03 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
> > It's used on Windows to ensure that installers can do the right thing
> > when replacing a copy of libpq.dll. The daily build number was the
> > most maintena
of libpq.dll. The daily build number was the
most maintenance-free way of getting a fourth value for the version
resource.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---(end of broadcast)---
TIP 6: explain analyze is your friend
usly just for testing. Should we just turn it on by
> default and see if anyone complains?
I say go for it. We'll soon know if it kills the buildfarm.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---
-
namely that too many brain dead hosting providers won't add a contrib
module or anything else in a customer's database because they don't
understand that just because it's not there by default doesn't mean
it's in any way second rate. Including pl/pgsql in template1 wil
seems like an excessively ugly solution :) But what about the others?
> What would people prefer?
I like option 1 the best. Minimally invasive, and probably easier to
handle on the client than 2. 3 is just ugly as you say. You should be
ashamed of yourself :-p
--
Dave Page
EnterpriseDB
hs. If
someone with PHP skillz wants to pick it up please let me know.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by dona
Not judging by Hiroshi's screenshot. I don't speak Japanese either,
but it certainly didn't say 'tuesday' after he adjusted LC_MESSAGES.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---(end of bro
urce on Slackware Linux? It took about an hour the
first time I did it, with no previous SVN experience.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---(end of broadcast)---
TIP 5: don't forget
On Feb 6, 2008 11:12 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> I've sometimes wondered whether the SUBSYS.o files really offer any
> advantage compared to just linking all the individual .o files. They
> certainly eat disk space, but perhaps they save some time ... or perhaps
> not, especially in
On Feb 6, 2008 4:24 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
>
> I would rather set a target and modify it if necessary based on
> experience than have none at all.
>
> The danger of not doing so is that we'll be in almost constant 'commit
> fest' mode.
Yes, that is something we discussed
On Feb 6, 2008 3:57 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
> I would like to see this tied down some more. The time for the commit
> fests is too open ended. I think we should say something like "All
> commit fests will run no more than two weeks, except for the final
> commit fest which c
On Feb 6, 2008 2:44 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> Good start. /me thinks it should be on the website. We've usually announced
> our feature freeze dates there... (in less details, sure, but something
> there)
Feel free - you've been hacking that recently!
/D
On Feb 6, 2008 1:49 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 06, 2008 at 08:56:51AM +0000, Dave Page wrote:
> > Hackers,
>
> Looks great and well-thought through. Let's hope it works out!
>
> I assume you'll be committing this info to t
final commit fest to take a good
deal of time, we'll reserve the right to reject patches that are too
large to be reviewed in a timely fashion. We want to encourage people
to do development of large features in an incremental fashion, with a
new increment landing during each commit fest.
Regards
On Feb 5, 2008 5:56 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> Dave Page wrote:
> > On Feb 5, 2008 3:24 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> >> On Mon, Jan 28, 2008 at 06:27:05PM +, Pavel Golub wrote:
> >> I think a better solution
On Feb 5, 2008 8:57 PM, Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> Can I ask when the Feature Freeze for next release will be?
I shall be posting on this topic in the next day or so.
/D
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Feb 5, 2008 6:11 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > Please go ahead and remove the -i - it's not like users cannot cannot
> > specify which set of pg utilities to use if they need a specific
> > version.
>
> Ok, done!
Thanks.
/D
---(end of broadcast)--
On Feb 5, 2008 3:24 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 28, 2008 at 06:27:05PM +, Pavel Golub wrote:
> >
> I think a better solution is to add a parameter to clean.bat to make it
> work like "make clean" does. So you'd to "clean" when you mean "make
> clean", and "clean
On Feb 5, 2008 3:27 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 31, 2008 at 11:02:03AM -0500, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > I would be satisfied with that if I thought people would actually read
> > > the message. My complaint is really directed at certain admin p
On Feb 5, 2008 11:50 AM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
> This probably wasn't on the core team's horizon - IIRC Dave is the only
> member of core who runs a buildfarm member.
To be honest the zoo beside me didn't even cross my mind when that
thread happened. I didn't pay much attenti
On Feb 5, 2008 9:00 AM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> I assume this vote was taken out on -core? I don't mind -core deciding on
> this, not at all, but I would appreciate it if you would post the result of
> the vote on -hackers.
It wasn't a 'vote' in the formal sense. It was just
On Jan 31, 2008 1:33 AM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> > Re-reading the thread ... could that last point be significant? Are
> > all four of these boxen set to auto-accept updates from Redmond?
>
> No. red_bat does not auto-accept anything.
For future reference, my BF members do au
On Jan 30, 2008 9:21 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> I won't have access to my MSVC box until tomorrow, but unless beaten to
> it I can dig into it a bit more. I don't see anything obvious int he
> latest patches thoughy (but again, that could be the beer :-P).
>
> Any chance you
On Jan 30, 2008 9:13 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
> > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mastodon&dt=2008-01-30%2020:00:00
>
> Maybe I shouldn't have had those beers after work today, but that looks
> like it'
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mastodon&dt=2008-01-30%2020:00:00
/D
---(end of broadcast)---
TIP 6: explain analyze is your friend
On 18/01/2008, Gregory Stark <[EMAIL PROTECTED]> wrote:
> Are you picturing adding ALTER TABLE commands to set autovacuum parameters? Or
> do you mean for tools like pgadmin to control this? Because the latter could
> happen even during the 8.3 cycle (though I perhaps not with pgadmin itself
> whic
On 17/01/2008, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> Cc: "[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
> PROTECTED]@postgresql.org.pgsql-chat"@post
>
> Hey, this is exactly the sort of weird "Cc:" line I saw in the recent
> spam surge. Since I suspect you are using the new
On 12/01/2008, Mark Mielke <[EMAIL PROTECTED]> wrote:
> Jean-Michel Pouré wrote:
> > In my past development projects, I always used the concept of
> > Materialized VIEW to speed-up SELECTs over INSERTs
>
> Unless you are going to *pay* for it - you do realize that the best way
> to get it implement
On 11/01/2008, Kris Jurka <[EMAIL PROTECTED]> wrote:
> Turns out it's not just 83RC1, but all of the security releases, which
> will require different pljava packages for the patch versions before/after
> the security changes. I've committed a fix to CVS for this, and I guess
> I'll try to respin
Andrew Dunstan wrote:
> Writing and calling a temp .bat file might be yucky - having to keep two
> environment files is a lot more yucky, IMNSHO, and we shouldn't make
> people do it.
+1
/D
---(end of broadcast)---
TIP 1: if posting/reading through
Bruce Momjian wrote:
> Dave Page wrote:
>> David != Dave
>
> Yea, but that is so subtle that is seems too error-prone.
I think you missed the smiley. It doesn't bother me if I'm named in full
or not, just that the introduction is accurate - which
Bruce Momjian wrote:
> Heikki Linnakangas wrote:
>> Dave Page wrote:
>>>> First-name-only
>>>>entries represent established developers, while full names represent
>>>>newer contributors.
>>> That's inaccurate - I've been l
Dave Page wrote:
> Tom Lane wrote:
>> Dave Page <[EMAIL PROTECTED]> writes:
>>> Gregory Stark wrote:
>>>> An alternative is leaving it in the project file but putting
>>>> something like
>>>> this in c.h:
>>
>> Put it in
> --- Original Message ---
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: Bruce Momjian <[EMAIL PROTECTED]>
> Sent: 09/12/07, 23:39:55
> Subject: Re: [HACKERS] Release Note Changes
>
> First-name-only
> entries represent established developers, while full names represent
>
Tom Lane wrote:
Dave Page <[EMAIL PROTECTED]> writes:
Gregory Stark wrote:
An alternative is leaving it in the project file but putting something like
this in c.h:
Put it in win32.h, please. c.h shouldn't get cluttered with
platform-specific kluges when there's no need for
Mark Cave-Ayland wrote:
H. So even though PGPASSWORD is set (and the command works if the
database exists within the cluster), if I specify a non-existent
database then I still get prompted for a password.
Just to add a note to that - when running it in the same shell from
which I started
Gregory Stark wrote:
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
I guess my advice would be to see if we can define _USE_32BIT_TIME_T
in port/win32.h and make it go away that way. It'd definitely be nice
if MSVC and Mingw builds weren't binary-incompatible.
The attached patch defines it in
Dave Page wrote:
but the CRC is still different for some as-yet unknown reason...
Unknown because I wasn't fully grokking what it was a CRC of. Everything
looks good now :-)
/D
---(end of broadcast)---
TIP 1: if posting/reading through U
Tom Lane wrote:
> AFAIK, time_t is a Unix-ism, so it's pretty unlikely to be used in the
> APIs of anything on Windows.
Oh, it is.
> I guess my advice would be to see if we can define _USE_32BIT_TIME_T
> in port/win32.h and make it go away that way. It'd definitely be nice
> if MSVC and Mingw bu
Gregory Stark wrote:
> This is because of (at least) two changes in the ABI between the runtimes used
> by mingw and VC++. 1) Enums are apparently 8 bytes on VC++ but 4 bytes on
> mingw and 2) time_t is 8 bytes on VC++ but 4 bytes on mingw.
For the record:
Mingw
=
WARNING: sizeof(ControlFil
Magnus Hagander wrote:
> Hi!
>
> When you redid the msvc build stuff you seem to have missed the
> documentatino.. Specifically, I notice that buildenv.pl isn't documented -
> docs still say buildenv.bat is the way to go.
>
> Also, do we now have both buildenv.bat and buildenv.pl? (I have them bo
Joshua D. Drake wrote:
> On Wed, 28 Nov 2007 16:27:42 +
> Dave Page <[EMAIL PROTECTED]> wrote:
>
>> Why not Hackers? Noone is a 'member' of anything except core or mayber
>> the web/infrastructure team.
>
> Define Hacker. And I could argue that s
Joshua D. Drake wrote:
> Not to mention there don't seem to be any defined rules. I asked Berkus
> and his reply was, "It has always been a little fuzzy". I asked Devrim
> and he gave me 5 bullet points that don't quite make sense.
Not sure what Devrim is referring to, but most often in the past R
Stefan Kaltenbrunner wrote:
> yeah well - the release notes do not make that good a reference on the
> "who submitted patches" question anyway because the do not contain stuff
> that are mere compile failures or add support for additional
> platforms/cleanups) of new features (ie my patches to add
Josh Berkus wrote:
> All,
>
> Time for the annual update of this list:
> http://www.postgresql.org/developer/bios
>
> Here's the list of people I gleaned from the release notes (btw, if people
> have countries for the folks who aren't attributed, I'd appreciate them).
> Of course, there are ma
Tom Lane wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
>>> From: Tom Lane <[EMAIL PROTECTED]>
>>> I see that there are two or three minor bug fixes in the REL7_3_STABLE
>>> branch since 7.3.20. Rather than just leaving those to rot, maybe t
> --- Original Message ---
> From: Tom Lane <[EMAIL PROTECTED]>
> To: pgsql-hackers@postgresql.org
> Sent: 27/11/07, 19:02:24
> Subject: [HACKERS] PG 7.3 is five years old today
>
> I see that there are two or three minor bug fixes in the REL7_3_STABLE
> branch since 7.3.20. Rather than
> --- Original Message ---
> From: Tom Lane <[EMAIL PROTECTED]>
> To: "Dave Page" <[EMAIL PROTECTED]>
> Sent: 26/11/07, 22:30:17
> Subject: Re: [HACKERS] Locating sharedir in PostgreSQL on Windows
>
> "Dave Page" <[EMAIL PROTEC
> --- Original Message ---
> From: Tom Lane <[EMAIL PROTECTED]>
> To: "Dave Page" <[EMAIL PROTECTED]>
> Sent: 26/11/07, 22:02:09
> Subject: Re: [HACKERS] Locating sharedir in PostgreSQL on Windows
>
>
> I believe that that is talking spe
> --- Original Message ---
> From: Peter Eisentraut <[EMAIL PROTECTED]>
> To: Dave Page <[EMAIL PROTECTED]>
> Sent: 26/11/07, 20:14:25
> Subject: Re: [HACKERS] Locating sharedir in PostgreSQL on Windows
>
> Dave Page wrote:
> > How does
Peter Eisentraut wrote:
> Am Montag, 26. November 2007 schrieb Mark Cave-Ayland:
>> I'm working on a piece of code for PostGIS to allow the loading of
>> projection configuration files from the share/postgresql directory, but
>
> The share directory is the wrong place for configuration files anywa
postgresql01.managed.contegix.com and therefore developer.pgadmin.org
and nagios.pgadmin.org will be going down for maintenance sometime
shortly after 9AM GMT today. Downtime is expected to be around 15 minutes.
Apologies for the short notice.
Regards, Dave
---(end of bro
Andrew Dunstan wrote:
(And I share Tom's concern about version compatibility - the autoconf
team don't have a great record on that IIRC.)
Thats why I think it might be useful to keep an eye on what does and
doesn't work.
I agree it's not a major issue though, so if it's non-trivial to
imple
Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Friday, November 16, 2007 18:00:26 + Dave Page <[EMAIL PROTECTED]>
wrote:
Marc G. Fournier wrote:
Maybe the BF members could just run their default autoconf as part of the
build if they have one.
yo
Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Friday, November 16, 2007 11:10:09 -0500 Tom Lane <[EMAIL PROTECTED]>
wrote:
I'm really not
too sure what the functional incompatibilities between versions are,
but given the extent of line-by-line diffs I've see
Marc G. Fournier wrote:
Maybe the BF members could just run their default autoconf as part of the
build if they have one.
you lost me on that one ... Tom is hestitant about moving to 6.1 because we
don't know what the fall out will be ... since I imagine the fallout would be
in the configure/
hold the presses...
Narwhal just broke :-(
Original Message
Subject: PGBuildfarm member narwhal Branch HEAD Status changed from OK
to Make failure
Date: Thu, 15 Nov 2007 13:23:06 -0800 (PST)
From: PG Build Farm <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
[EMAIL PROTECTED]
The P
Magnus Hagander wrote:
> I'm certainly not convinved about that either, but we should make a test on
> a VM at some point.
>
> Sophos AV has plugins into for example the explorer (I assume - most AV
> does, haven't used Sophos specifically myself), which may be done with
> extra DLLs loading along
Magnus Hagander wrote:
>> As for desktop heap, only 65KB of the service heap was allocated, or
>> about 80 bytes per connection. No danger of hitting limits in the
>> kernel memory pools either.
>
> As Dave said, it could be that the server version uses a lot less heap per
> process, which would
> --- Original Message ---
> From: "Trevor Talbot" <[EMAIL PROTECTED]>
> To: "Magnus Hagander" <[EMAIL PROTECTED]>
> Sent: 10/11/07, 23:17:13
> Subject: Re: [HACKERS] 8.2.3: Server crashes on Windows using Eclipse/Junit
>
> As for desktop heap, only 65KB of the service heap was allocated
Pavel Stehule wrote:
> Hello
>
>
> C:\Program Files\PostgreSQL\8.3-beta2\bin>pgAdmin3.exe
> The system cannot execute the specified program.
>
>
> When I run pgAdmin from menu I got
>
> This applications has failed to start because the application
> configuration is incorrect. Reinstalling the
Pavel Stehule wrote:
> Hello
>
>> Why aren't you asking in the pgadmin forums?
>>
>
> It's true, I am sorry, I havn't access to pgadmin phorum from win :(.
Huh? Your windows based mua can post to pgsql-hackers@postgresql.org but
not [EMAIL PROTECTED] That's even more borked than OE
Regards,
> --- Original Message ---
> From: Peter Eisentraut <[EMAIL PROTECTED]>
> To: pgsql-hackers@postgresql.org
> Sent: 29/10/07, 17:54:00
> Subject: Re: [HACKERS] pg_ctl configurable timeout
>
> Am Freitag, 17. August 2007 schrieb Peter Eisentraut:
> > I'm having trouble with the hardcoded 6
Magnus Hagander wrote:
> I'm leaning towards applying the patch now, and hoping for 2b to happen.
I think we should live with the mingw BF breakage for a day or two. The
patch is clearly an important improvement, but it should be as widely
tested as possible.
/D
---(end o
Magnus Hagander wrote:
> Right. You need to look at VM size in *process explorer*. VM size in
> task manager has nothing to do with VM size, it's the private bytes :-S
> And there is no way to see that info from task manager, I think. PE is
> your friend.
>
>
> Anyway. Other than a refresher on t
Magnus Hagander wrote:
> VM size in taskmgr should show that I think, and should show a much
> smaller footprint now..
With patch -4,492K
Without patch: 28,224K
Thats with 3 x 100 pgbench connections.
/D
---(end of broadcast)---
TIP 3: Have
Magnus Hagander wrote:
> Taking this one to -hackers once and for all now...
>
> Can you try the attached patch? See how many backends you can get up to.
Regression tests run just fine, and I've run multiple pgbench runs with
3 and 4 sessions of 100 connections each*, with pgAdmin monitoring
thin
Roberto Icardi wrote:
Also, please set pgAdmin to 'Debug' log level (under File->Options),
create a new log of you recreating the crash (using direct debugging,
not a global breakpoint) and then send me the logfile.
Done
Doesn't shed any light though unfortunately. Do you have a firewall on
Roberto Icardi wrote:
>> When you attempt to debug it, do you see the parameter dialogue before
>> it crashes, or does it go immediately?
>>
>
> if I try debug->debug it goes immediately
> if I try debug->set breakpoint I can see debugger window but is
> completely empty and inactive
>
>
>
>> A
Roberto Icardi wrote:
> CREATE OR REPLACE FUNCTION public.prova(provain character varying)
> RETURNS character varying AS
> $BODY$
> begin
> if (provain = 'A') then
>return 'INVALIDO';
> else
>return 'VALIDO';
> end if;
> end;
> $BODY$
> LANGUAGE 'plpgsql' VOLATILE
> COST 100;
> ALTER
Roberto Icardi wrote:
> Yes, they are all there
> I've also tried on a newly created database instead of testing on a
> restored from 8.2. backup but with
> the same behaviour :-(
Please post the definition of an affected function, along with the
output from the following queries:
select * fr
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> On Mon, Oct 22, 2007 at 08:59:07AM +0100, Dave Page wrote:
>>> From chatting with Magnus, I believe he'd support losing the .1252 or
>>> leaving it as is, where I'd rather rewrite
Roberto Icardi wrote:
> Dave,
>
> the problem isn't with a particular function. Debug does not work with
> every function I try, even with the simplest one, always with the same
> behaviour I've previously explained.
> I repeat, my postgresql server is an 8.3 beta 1 installed on the same
> machin
701 - 800 of 1719 matches
Mail list logo
