Jan Wieck <[EMAIL PROTECTED]> writes:
> I guess nobody ever relied that heavily on data to be persistent at the
> microsecond the NOTIFY arrives ...
Sure they have.
In theory you cannot see a NOTIFY before the sending transaction
commits, because the sender is holding a lock on pg_notify and you
I said:
> Oh, fooey.
> exec_simple_query calls EndCommand before it calls finish_xact_command,
Fooey again --- that theory is all wrong. Back to the drawing board.
I have managed to reproduce the bug on CVS tip, btw. But it's very
painful to make it happen. Have you got any tips for making it
On 9/24/2004 10:24 PM, Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
Now the scary thing is that not only did this crash rollback a committed
transaction. Another session had enough time in between to receive a
NOTIFY and select the data that got rolled back later.
Different session, or s
Jan Wieck <[EMAIL PROTECTED]> writes:
> Now the scary thing is that not only did this crash rollback a committed
> transaction. Another session had enough time in between to receive a
> NOTIFY and select the data that got rolled back later.
Different session, or same session? NOTIFY is one of t
It would appear that region_id = parent_id is not internally converted
to region_id = 1129, despite parent_id being enforced to 1129 at the top
level.
In this case, it makes a difference in performance of about 4 (2 minutes
vs 30 second).
The reason I didn't do this myself upfront, is that parent
Hi all,
Martijn, a user of Npgsql, sent me a query which is giving problems with
postgresql using extended query mode.
The problem I'm having is in the Parse message. The parse message I'm
sending is as follow:
select * from table where $1 in (select some_field from table)
Postgresql returns t
On 9/24/2004 6:37 PM, Tom Lane wrote:
Can you still reproduce the problem if you take out the ereport call
in quickdie()?
Will check ...
BTW, what led you to develop this test setup ... had you already seen
something that made you suspect a data loss problem?
Good guess ... what actually happenend
>> This means either that the server sent a commit message before it had
>> xlog'd the commit, or that Pgtcl mistakenly reported the command as
>> successful when it was not. Any thoughts?
Oh, fooey.
exec_simple_query calls EndCommand before it calls finish_xact_command,
and of course the latter
The new thread on 7.4.5 losing committed transactions popped up just as
I discovered something that was at least unexpected to me.
In doing the cleanup from my pg_resetxlogs from today's earlier fun, I
found some missing rows and some duplicate row versions showing up in my
restore. All of this w
Jan Wieck <[EMAIL PROTECTED]> writes:
> Is it somehow possible that the commit record was still sitting in the
> shared WAL buffers (unwritten) when the response got sent to the client?
I don't think so. What I see in the two cases I have now are:
(1) The backend that was doing the "lost" tran
On 9/24/2004 5:12 PM, Tom Lane wrote:
This means either that the server sent a commit message before it had
xlog'd the commit, or that Pgtcl mistakenly reported the command as
successful when it was not. Any thoughts?
Is it somehow possible that the commit record was still sitting in the
shared W
Jan Wieck <[EMAIL PROTECTED]> writes:
> But occasionally there will appear a gap in the data. With the given
> logic only to increment the counter on a dupkey or after a positive
> COMMIT response by the backend, IMHO there can only be one if we lose
> transactions after commit on a crash restar
Shown below is a HOWTO for PostgreSQL build farm clients for the system
I'm working on. The HOWTO is also available at
http://pgfoundry.org/docman/view.php/140/4/PGBuildFarm-HOWTO.txt
The code is running successfully on several machines, and uploading
results to my test server.
A producti
Cott Lang wrote:
I wish I knew - this is what appeared to start it:
Sep 24 10:19:41 snafu postgres[18176]: [464-1] ERROR: could not open
segment 1 of relation "idx_ordl_id" (target block 1719234412): No such
file or
Sep 24 10:19:41 snafu postgres[18176]: [464-2] directory
I can't figure out what
On Fri, Sep 24, 2004 at 10:03:33AM -0400, Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Or are you talking about non-scalar OUT params?
>
> Exactly. I agree that a procedure has no "return value" per se,
> but we need to be able to support OUT params that are rowsets.
FWIW, Sybas
The attached archive contains a script that I used to reproduce the
error multiple times.
Setup:
* create database crashtest
* start 6 instances of testload.tcl as
./testload.tcl tN dbname=crashtest
where N = 1..6
* frequently kill a backend to cause a postmaster restart.
The te
Does pgfsck work on 7.4.x?
>
> Otherwise, maybe something here will help:
> http://svana.org/kleptog/pgsql/pgfsck.html
>
> ---(end of broadcast)---
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining colum
On Fri, 2004-09-24 at 11:43, Tom Lane wrote:
>
> I think your only chance is pg_resetxlog. Be aware that you won't
> necessarily have a consistent database afterwards --- in particular,
> whichever index that failure is about is certainly broken. I'd
> recommend a dump and reload, plus as much m
Cott Lang <[EMAIL PROTECTED]> writes:
> Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG: database system was
> interrupted while in recovery at 2004-09-24 10:21:41 MST
> Sep 24 10:22:37 snafu postgres[18306]: [2-2] HINT: This probably means
> that some data is corrupted and you will have to use
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Cott Lang
> Sent: Friday, September 24, 2004 10:21 AM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] CRITICAL HELP NEEDED! DEAD DB!
>
>
> Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG: database
> s
Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG: database system was
interrupted while in recovery at 2004-09-24 10:21:41 MST
Sep 24 10:22:37 snafu postgres[18306]: [2-2] HINT: This probably means
that some data is corrupted and you will have to use the last backup for
recovery.
Sep 24 10:22:37
pg_autovacuum just writes to standard out unless you specify a log file
on the command line. See pg_autovacuum -h for details.
Matthew
On Wed, 2004-09-22 at 03:29, Iulia Pacurar wrote:
Hi!
I run pg_autovacuum:
./pg_autovacuum -D
but then I cannot find pg_autovacuum.log file.
Where shoud I look f
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Magnus Hagander
> Sent: 24 September 2004 16:27
> To: Marc G. Fournier; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] PostgreSQL 8.0 beta3 on Monday
>
>
> I would like to get the SSL stuff in, but
I hope to get PL/Python builds on win32 in.
I would like to get the SSL stuff in, but I haven't had the time to look
at it lately, so unless someone else steps up to that one (I know at
least Dave is also working on it) I don't think it'll make it.
//Magnus
> -Original Message-
> From:
I believe you are correct for Oracle at least.
But for people porting over from MSSQL it is a *huge* deal, and given
the native windows port of Postgres with 8.0.0, I predict *many*
requests for this in upcoming months.
Speaking from a commercial perspective. I have had, in the last 60 days
ov
Andrew Dunstan wrote:
Thomas Hallgren wrote:
Problem:
PL/Java use a JVM. On some platforms and with some JVM's (Sun's in
particular) a libzip.so is bundled that contains a 1.1.3 version of
functions also provided in zlib (why they do this is beyond me, but
they do so I'll have to live with it).
Neil Conway wrote:
On Fri, 2004-09-24 at 01:56, Joe Conway wrote:
As other's have pointed out, this is very common in the MS SQL Server
world (and I believe Sysbase also supports it).
From looking at the docs, it appears this isn't supported by Oracle or
DB2 (correct me if I'm wrong). I can see h
"Hicham G. Elmongui" <[EMAIL PROTECTED]> writes:
> In other words, in the following tree, a variable in B that shows in Op1's
> target list, does it have its relation as INNER (which is B) or OUTER (which
> is Op2)
> Op1
> / \
> / \
>/ \
> Op2 Op3
>
Its been almost a month now, since Beta2, and commit activity has quite
busy, so we're aiming for Monday, September 28th, for Beta3.
Starting with Beta3, Bruce is also going to change the format for the
OpenItems list a little bit, but including a list of 'Changes since last
Beta' at the bottom
Neil Conway <[EMAIL PROTECTED]> writes:
> On Fri, 2004-09-24 at 04:12, Josh Berkus wrote:
>> Well, see my thoughts above on differentiating SPs from Functions.I
>> certainly don't think we should be using the same table.
> Using a different system catalog strikes me as total overkill, and a
>
Thomas Hallgren wrote:
Problem:
PL/Java use a JVM. On some platforms and with some JVM's (Sun's in
particular) a libzip.so is bundled that contains a 1.1.3 version of
functions also provided in zlib (why they do this is beyond me, but
they do so I'll have to live with it). PostgreSQL is linked
Neil Conway <[EMAIL PROTECTED]> writes:
> Or are you talking about non-scalar OUT params?
Exactly. I agree that a procedure has no "return value" per se,
but we need to be able to support OUT params that are rowsets.
regards, tom lane
---(end of b
Hi,
I am confused about an internal point of the planner.
Consider a select query and the output target list at the root of the tree.
This target lists points to some Vars. Each of which has as relation either
INNER/OUTER.
Does this INNER/OUTER refer to the inner/outer relations of the top-most
no
Peter Mount <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>
> >One interesting point is whether it's possible for one procedure to call
> >another, and if so what that means for the semantics. Is the inner
> >procedure allowed to commit a transaction started by the outer one?
>
> Usually yes a
Neil Conway wrote:
On Fri, 2004-09-24 at 01:56, Joe Conway wrote:
As other's have pointed out, this is very common in the MS SQL Server
world (and I believe Sysbase also supports it).
From looking at the docs, it appears this isn't supported by Oracle or
DB2 (correct me if I'm wrong). I can see
On Fri, 2004-09-24 at 02:40, Tom Lane wrote:
> I concur with Grant Finnemore's objection as well: people expect
> procedures to be able to return resultsets, ie SETOF something,
> not only scalar values.
IMHO most products (and the standard) define stored procedures as not
returning _anything_, wh
On Fri, 2004-09-24 at 05:52, Alvaro Herrera wrote:
> I don't think we can do that in a standard function, at least not
> without a lot of work.
Can you elaborate on why this would be so difficult?
-Neil
---(end of broadcast)---
TIP 8: explain ana
On Fri, 2004-09-24 at 01:56, Joe Conway wrote:
> As other's have pointed out, this is very common in the MS SQL Server
> world (and I believe Sysbase also supports it).
>From looking at the docs, it appears this isn't supported by Oracle or
DB2 (correct me if I'm wrong). I can see how it would be
On Fri, 2004-09-24 at 04:12, Josh Berkus wrote:
> My comments are based on having professionally written several hundred
> thousand lines of procedural code for PostgreSQL, SQL Server, and Oracle.
I haven't used stored procedures as implemented elsewhere, so I
appreciate your comments.
> > If we
Maarten Boekhold wrote:
Joe Conway wrote:
Gavin Sherry wrote:
Do you have any idea about databases returning result sets from SQL
procedures (ie, not functions).
As other's have pointed out, this is very common in the MS SQL Server
world (and I believe Sysbase also supports it). It works like:
An
Tom Lane wrote:
One interesting point is whether it's possible for one procedure to call
another, and if so what that means for the semantics. Is the inner
procedure allowed to commit a transaction started by the outer one?
Usually yes a procedure can call another, and it's extremely useful to
Joe Conway wrote:
Gavin Sherry wrote:
Do you have any idea about databases returning result sets from SQL
procedures (ie, not functions).
As other's have pointed out, this is very common in the MS SQL Server
world (and I believe Sysbase also supports it). It works like:
And these databases also r
42 matches
Mail list logo
