The following bug has been logged online:
Bug reference: 2303
Logged by: Massimo Fidanza
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux
Description:UPDATE from manual is incorrect
Details:
Hi all, I have an update similar to the one
The following bug has been logged online:
Bug reference: 2305
Logged by: H. Guijt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows 2000
Description:"No bufferspace available" error on large insert
Details:
We are using PostgreSQL
The following bug has been logged online:
Bug reference: 2308
Logged by: Matthew George
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST
2006; root:xnu-792.6.61.obj~1/RELEASE_PPC Power Macintosh
The following bug has been logged online:
Bug reference: 2306
Logged by: Andreas Jung
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.9
Operating system: Linux
Description:Duplicate primary key
Details:
Ihave the following table (with 'id' as primary key:
The following bug has been logged online:
Bug reference: 2307
Logged by: Giza Kamil
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows,Linux
Description:Buckup and sequences in DEFAULT part
Details:
Hi!
My script is:
CREATE SEQUENCE
The following bug has been logged online:
Bug reference: 2304
Logged by: Alexander Pivovarov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.1
Description:Time zone bug: '05:04 GMT+3' processing as '05:04:00
-03'
Details:
#
On Tue, Mar 07, 2006 at 04:43:18PM +, Andreas Jung wrote:
> PostgreSQL version: 7.4.9
7.4.12 is the latest in that branch; it contains several bug fixes
since 7.4.9.
> This gives me two rows with the same id=5077:
>
> Toolbox2Test=# select * from hierarchy where id >= 5077 order by id;
What
...
Upon issuing the insert statement I receive the following error message:
"could not send data to server: No buffer space available
(0x2747/10055)"
I suspect that this happens because we are inserting a lot of data: the
first BYTEA column is about 1.8MB, while the second is about 0.5MB.
"Matthew George" <[EMAIL PROTECTED]> writes:
> Since the logic obviously exists within pg_dump already to arrange the data
> in the correct order of reference dependencies, can this be added to the
> code path for `pg_dump -a` as well?
No. In a data-only restore there may not be *any* ordering th
"Giza Kamil" <[EMAIL PROTECTED]> writes:
> Buckups on 8.0 were OK, but on 8.1 I'm getting samething like that:
> CREATE TABLE schema.tab1(ID integer DEFAULT nextval('seq_taid'::regclass));
You haven't said why you think this is a problem. The dump is perfectly
valid AFAICS.
"Alexander Pivovarov" <[EMAIL PROTECTED]> writes:
> # select '05:04 GMT+3'::time with time zone;
>timetz
> -
> 05:04:00-03
> (1 row)
This isn't a bug; it's expected. The "GMT+n" syntax is defined by a
different standard than the one we follow for timestamp output, and
the two sta
On Mar 8, 2006, at 3:01 PM, Tom Lane wrote:
"Matthew George" <[EMAIL PROTECTED]> writes:
The best practice is to do standard schema+data dumps, wherein the
ordering problem can be handled properly by not creating the FK
constraints until after the data is loaded. If you really want to
do a data
Jim Nasby <[EMAIL PROTECTED]> writes:
> BTW, it would be really nice if we provided a better way to do this
> than manually dropping all the FK constraints and adding them back in
> later. Would it be difficult to allow deferring all constraints in
> the database during a specified transactio
"Massimo Fidanza" <[EMAIL PROTECTED]> writes:
> The query is the last but one
> UPDATE employees SET last_closed_deal = deal.id
> FROM accounts JOIN deals ON (account.id = deal.account_id)
> WHERE deal.employee_id = employees.id
> AND deal.name = 'Rocket Powered Skates'
> AND accou
I wrote:
> "Massimo Fidanza" <[EMAIL PROTECTED]> writes:
>> this query is not correct and doesn't work with postgresql 8.1.
> It still works, if you enable add_missing_from.
I take that back --- FROM is not the issue (indeed, it has one).
The problem is the ORDER BY and LIMIT clauses. I dunno wh
15 matches
Mail list logo