The following bug has been logged online:
Bug reference: 4909
Logged by: Richard Neill
Email address: rn...@cam.ac.uk
PostgreSQL version: 8.4
Operating system: Linux
Description:wish: easier way to configure RAM allocation
Details:
I've been using Postgres for ages
"Kevin Grittner" writes:
> Tom Lane wrote:
>> Or you could turn on standard_conforming_strings if you'd prefer not
>> to deal with escapes.
> That doesn't help with this, because of the separate pgpgsql parser:
Ah, sorry, it does work in 8.4 but not before.
regards, t
Tom Lane wrote:
> Or you could turn on standard_conforming_strings if you'd prefer not
> to deal with escapes.
That doesn't help with this, because of the separate pgpgsql parser:
ccdev=> select version();
version
--
"Jack Douglas" writes:
> Am I missing something obvious here - I understand from the documentation no
> escapes are counted in dollar quoted strings?
Yes, and yes.
> postgres=> create or replace function temp() returns text language plpgsql
> AS $$
> postgres$> begin
> postgres$> return '\';
>
The following bug has been logged online:
Bug reference: 4908
Logged by: Jack Douglas
Email address: jackpdoug...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Debian Lenny
Description:escaping and dollar quotes: "ERROR: unterminated
string"
Details:
Am I m
The bug was solved!
Change the configuration of your Windows XP(appearence/Scheme) to
"Windows Classic".
best regards
Silvano de Souza escreveu: > Failed to get System metrics for terminal
services:87 > 8.1 is *not* supported on Windows platform anymore.
Consider using the latest stabl
On Jul 8, 2009, at 3:42 PM, Tom Lane wrote:
Joe Uhl writes:
On Jul 8, 2009, at 3:00 PM, Tom Lane wrote:
Hmm. In any case that shouldn't have led to a lock left hanging.
Assuming that it was a regular and not autovacuum, do you know what
the exact command would have been? (In particular, FU
Joe Uhl writes:
> On Jul 8, 2009, at 3:00 PM, Tom Lane wrote:
>> Hmm. In any case that shouldn't have led to a lock left hanging.
>> Assuming that it was a regular and not autovacuum, do you know what
>> the exact command would have been? (In particular, FULL, ANALYZE,
>> etc options)
> They we
Michael Tenenbaum wrote:
> If I have a stored procedure that returns a set of records of a table, I get
> an error message that the procedure's record is the wrong type after I
> change some columns in the table.
>
> Deleting the procedure then rewriting the procedure does not help. The only
> t
On Jul 8, 2009, at 3:00 PM, Tom Lane wrote:
Joe Uhl writes:
On Jul 8, 2009, at 2:41 PM, Tom Lane wrote:
What exactly did you do to "kill" those processes? Do you remember
whether any of them happened to have PID 10453?
I used "kill pid1 pid2 pid3 ..." (no -9) as root. Unfortunately I do
Joe Uhl writes:
> On Jul 8, 2009, at 2:41 PM, Tom Lane wrote:
>> What exactly did you do to "kill" those processes? Do you remember
>> whether any of them happened to have PID 10453?
> I used "kill pid1 pid2 pid3 ..." (no -9) as root. Unfortunately I do
> not recall if that pid was one of the
On Jul 8, 2009, at 2:41 PM, Tom Lane wrote:
Joe Uhl writes:
I had to bounce an OpenMQ broker this morning (this database is the
DB
for an OpenMQ HA setup) and couldn't get it to reconnect to postgres.
On inspecting the database I found dozens of vacuum processes waiting
(I have a cron job th
Joe Uhl writes:
> I had to bounce an OpenMQ broker this morning (this database is the DB
> for an OpenMQ HA setup) and couldn't get it to reconnect to postgres.
> On inspecting the database I found dozens of vacuum processes waiting
> (I have a cron job that vacuums each night) and chewing
Hi all,
I entered a bug report yesterday through the PostgreSQL web site that
was assigned bug ID 4906. However, looking through the pgsql-bugs
list, I don't see the posting I entered -- is it possible this bug
report disappeared into the void? Should I resubmit it?
Thanks,
Mathieu Fen
Robert Schnabel writes:
> From a fresh server restart I have one process that will run one
> processor 100% essentially forever. (I've let it go for about a week
> just to see if it would ever stop and it didn't). Attached is a text
> dump from ProcessExplorer. I have highlighted the releva
On Wed, Jul 8, 2009 at 2:03 PM, Tsutomu Yamada wrote:
> In the past, there was the thread about this problem,
> and it suggested using VirtualAllocEx().
> (But no patch was posted, right?)
> http://archives.postgresql.org/pgsql-general/2007-08/msg01592.php
>
> So I tries using VirtualAllocEx().
>
I've been having an issue for about 5 months now and after upgrading to
8.4 did not fix it I figured I'd try this list. I tried the perform
list a while back but no bites.
My system: Windows XP64 SP2, dual Opteron 2218, 12G ram, PostgreSQL
8.4. I am the only person using the postgres server
When the server starts, it should also spew out the initial shmem
segment ID and address - did you get them? They may go to stderr
rather than the log, because they're output so early in the startup. I
assume they're the same because one of the attaches seems to work
fine.
2009/7/8 Wojciech Strza
I have a 8.3.6 postgres database running on Arch Linux (2.6.28 kernel)
with the following entry in pg_locks:
locktype | database | relation | page | tuple | virtualxid |
transactionid | classid | objid | objsubid | virtualtransaction |
pid | mode | granted
relation
Dave Page wrote:
> 2009/7/7 Wojciech Strzałka :
> >
> > Here ( http://www.codelabs.pl/_varia/pg.zip ) is detailed info from
> > my machine (PostgreSQL 8.3.6, compiled by Visual C++ build 1400):
> >
> > - detailed log file with several memory attach problems
> > - process activity log fi
And the result is:
2009-07-08 14:26:00 CEST PID:9612 DEBUG: 0: forked new backend, pid=8120
socket=948
2009-07-08 14:26:00 CEST PID:9612 LOCATION: BackendStartup,
.\src\backend\postmaster\postmaster.c:3029
*** Finished restoring shared memory vars in restore_backend_variables
(key=256, ad
Witam!
W liście datowanym 8 lipca 2009 (13:55:00) napisano:
> 2009/7/8 Wojciech Strzałka :
>> I was wondering why I can not see the DEBUG2 info you were talking
>> about (tripple star), and probably that's another bug.
>> Whichever debug1 - debug5 level I set in config file the pg_settings
>>
2009/7/8 Wojciech Strzałka :
> I was wondering why I can not see the DEBUG2 info you were talking
> about (tripple star), and probably that's another bug.
> Whichever debug1 - debug5 level I set in config file the pg_settings
> tells me that it's set to 'debug' (without a number) - and there i
Witam!
W liście datowanym 7 lipca 2009 (18:02:30) napisano:
> 2009/7/7 Wojciech Strzałka :
>>
>> I think both 8.3 & 8.4 are from EnterpriseDB (the integer_datetime
>> is 'off' at least in 8.3 which is active at the time).
> OK, I put a zip of a server build at
> http://uploads.enterprisedb.com
Hi all,
I have this problem today: one thread of our application hung, and
we found the thread waiting for the result of poll() function. poll()
was called by pgSocketCheck(). So is it a bug of pg? I found the bug
report from
website(http://archives.postgresql.org/pgsql-bugs/2008-02/msg00260.
25 matches
Mail list logo
