The following bug has been logged online:
Bug reference: 3376
Logged by: Felipe Nogueira
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Windows 2003
Description:Erro : COMMIT
Details:
PostgreSQL 8.2.4 on i686-pc-mingw32, compiled by GCC
Please keep the list CC'd so that others can help and learn from the
discussion.
Felipe Nogueira wrote:
How I commit? I have a function that it will insert into a table, after
all,
I have commit.
You commit after calling the function. Like this:
BEGIN;
SELECT data(1,2);
COMMIT;
--
Heikki
Felipe Nogueira wrote:
I have the following function
CREATE OR REPLACE FUNCTION "public"."data" (integer, integer) RETURNS
integer AS
$body$
DECLARE
vDATA integer;
BEGIN
COMMIT;
END;
$body$
LANGUAGE 'plpgsql' STABLE CALLED ON NULL INPUT SECURITY INVOKER;
When I execute i have the error
ERR
Galy Lee wrote:
> * Bug-2: 0-cost-limit for autovacuum worker
>
> When autovacuum_max_workers > autovacuum_vacuum_cost_limit, the above
> zero-division error also happened.
Ah, this is a problem in the balance code -- it fails to consider that
the cost limit may be end up being 0 in the integer
The following bug has been logged online:
Bug reference: 3377
Logged by: Kevin Neufeld
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux Fedora Core 3
Description:pg_dump: No matching tables were found
Details:
pg_dump does not seem
Kevin Neufeld wrote:
> $ pg_dump -U postgres -t mytable postgres | less
> pg_dump: No matching tables were found
>
> $ pg_dump -U postgres -n test -t mytable postgres | less
> pg_dump: No matching tables were found
Try pg_dump -t test.mytable
Then check the docs of the new version, which state
I Think that your problem is: test.mytable() <> test.mytable, why your
table name include --> ()
On Fri, 2007-06-08 at 16:59 +, Kevin Neufeld wrote:
> The following bug has been logged online:
>
> Bug reference: 3377
> Logged by: Kevin Neufeld
> Email address: [EMAIL PROTE
