Tom,
> > Aha! Yes, the problem is that I dropped the last VARCHAR column, not in
> > that table but in one that came after it. Any workaround to fix?
>
> Easiest is to add back a useless varchar column ...
Can't do it, the column needed to be dropped in order to fix a problem with
the data tr
Josh Berkus <[EMAIL PROTECTED]> writes:
>> Easiest is to add back a useless varchar column ...
> Can't do it, the column needed to be dropped in order to fix a problem with
> the data transfer.Maybe re-create the table?
Yeah, I think you're stuck with doing that.
reg
Tom,
> Yeah, I think you're stuck with doing that.
BTW, this is a pretty nasty error, although apparently infrequent give the
lack of list e-mails. Can we fix it for 7.4 series?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)--
> BTW, this is a pretty nasty error, although apparently infrequent give the
> lack of list e-mails. Can we fix it for 7.4 series?
Possibly, but I'm not very excited about it --- it's certainly a corner
case. I'm not sure it's worth the risk of breaking something.
rega
Zane <[EMAIL PROTECTED]> writes:
> Different memory usage 7.4.3 vs 8.0.0beta1
> client does:
> begin
> bulk inserts into single table via PQexecParams (1.2 million records)
> commit
> under 7.4.3 memory usage is static
> under 8.0.0beta1 server used increasing memory untill depletion of vm/swap
The following bug has been logged online:
Bug reference: 1231
Logged by: Piotr Figiel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: Linux Suse
Description:Probelm with transactions in stored code.
Details:
Hello
I have a problem w
The following bug has been logged online:
Bug reference: 1232
Logged by: John R Pierce
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Linux 2.4.9
Description:Singapore Timezone missing
Details:
The timezone designation SGT is not r
The following bug has been logged online:
...
The timezone designation SGT is not recognized on inserts to "timestamp
with
time zone" fields.
...
fyi, I am on this list, if anyone wants to tell me I'm way off base here or
whatever :)
something tells me I'm going to hit this problem again when ou
Hi,
postmaster.c function win32_waitpid(int *exitstatus)
call to Win32 WaitForMultipleObjects
ret = WaitForMultipleObjects(win32_numChildren, win32_childHNDArray, FALSE,
0);
problem is 'win32_numChildren' could be more then 64 ( function supports ),
problem basically arise ( kills postgres ) whe
That's a good theory. I will definitely check it out.
I appreciate you looking into this Tom.
Spence
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 24, 2004 4:13 PM
To: Spencer Quin
Cc: [EMAIL PROTECTED]; Thomas Parry; Geoffrey Stitt
Subject: Re
Hello!
After splitting the the job into smaller pieces (e.g. 18x 1Mrow) the backend process
now seems to release the memory after each subjob. Therefore the trigger queue seems
to be a good candidate. Until now this queue was unknown to me.
Perhaps a note in the docu of COPY FROM and in the se
--- Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 22, 2004 at 09:39:07AM +0800, ??
> wrote:
> > BEGIN;
> > ...
> > ...
> > ...
> > END;
> >
> > PANIC: invalid xlog record length 236052
>
> Huh, so what kind of operations did you execute
> within the transaction?
>
> --
> Alvaro
The postmaster.pid file from the pre-crash instance remained in the data
directory. Deleted it and started fine.
>Using pgsql 8.0.0 beta 1 installed via PGInstaller 08092004 release
>on Windows 2000 SP4 build 5.00.2195, Dell Precision 360 single Pentium 4
>
>After a power cutoff and reboot, the d
Using pgsql 8.0.0 beta 1 installed via PGInstaller 08092004 release
on Windows 2000 SP4 build 5.00.2195, Dell Precision 360 single Pentium 4
After a power cutoff and reboot, the db service will not start, either
automatically or manually.
Two incidents; after the first I reinstalled before it wou
On Wed, 25 Aug 2004, PostgreSQL Bugs List wrote:
> CREATE OR REPLACE FUNCTION test_tr() RETURNS numeric AS'
> DECLARE
> a numeric;
> b numeric;
> BEGIN
> select next_number into b from test_trans where id=1;
> update test_trans set next_number=next_number+1 where id=1;
> select next_number into
"John R Pierce" <[EMAIL PROTECTED]> writes:
> so all of china uses CST, which is *NOT* CST as we know it here in North
> America ;-/
Yeah, it's going to be difficult to do much about this stuff with the
current approach of a hardwired table of zone names. There are other
unresolved conflicts (IS
Steffen Macke wrote:
> [PostgreSQL 8.0beta1 on Windows 2000 Professional]
>
> In case of a leftover postmaster.pid, pg_ctl start
> tries to start anyway,
> but pg_ctl runservice (as installer by the PostgreSQL
> Windows installer) will not start the service, requiring a manual
> removal of postma
Bellan Saravanan wrote:
> While performing Load testing using DOTS
> http://ltp.sourceforge.net/dotshowto.php ,
> during the tests, an update to a specific table starts hanging.
>
> The test name is called BTCJ2
> http://ltp.sourceforge.net/dotshowto.php#SEC26,
>
> "This test case mainly uses S
Stephan Szabo wrote:
On Wed, 25 Aug 2004, PostgreSQL Bugs List wrote:
CREATE OR REPLACE FUNCTION test_tr() RETURNS numeric AS'
DECLARE
a numeric;
b numeric;
BEGIN
select next_number into b from test_trans where id=1;
update test_trans set next_number=next_number+1 where id=1;
select next_number i
On Thu, 26 Aug 2004, Gaetano Mendola wrote:
> Stephan Szabo wrote:
>
> > On Wed, 25 Aug 2004, PostgreSQL Bugs List wrote:
> >
> > Actually, it shows that functions have odd behavior when locking is
> > involved (your statement would potentially be true if you could replicate
> > this without the f
"ÿceÿac" "ÿbdÿaa" <[EMAIL PROTECTED]> writes:
> --- Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>> Huh, so what kind of operations did you execute
>> within the transaction?
> There are 1600 tables in database 'db1', I wrote a
> pl/pgsql function "update_tables" like
> "
> FOR tabl
Stephan Szabo <[EMAIL PROTECTED]> writes:
> I believe it sees the one that was valid in the snapshot as of the
> beginning of the function.
Actually, the problem is that it can see *both* that row and the updated
row; it's a crapshoot which one will be returned by the SELECT INTO.
The reason this
so all of china uses CST, which is *NOT* CST as we know it here in North
America ;-/
Yeah, it's going to be difficult to do much about this stuff with the
current approach of a hardwired table of zone names. There are other
unresolved conflicts (IST is one I think).
Yeah, its a maze of twisty litt
23 matches
Mail list logo
