Maybe the reason why it worked not for me is, that I have used a
PreparedStatement?
I will try it with a Statement.
Thank you
Chantal
On Friday, 8. March 2002 18:16, Dave Cramer wrote:
> Chantal,
>
>
> I just tried it and it ran ok?
>
> con = getConnection();
> Statement st = con.createStatement();
> String sql = "vacuum analyze";
> st.execute(sql);
>
> This if from the logs
>
> ProcessQuery
> 2002-03-08 11:50:42 DEBUG: CommitTransactionCommand
> 2002-03-08 11:50:45 DEBUG: StartTransactionCommand
> 2002-03-08 11:50:45 DEBUG: query: vacuum analyze
> 2002-03-08 11:50:45 DEBUG: ProcessUtility: vacuum analyze
> 2002-03-08 11:50:45 DEBUG: --Relation pg_type--
> 2002-03-08 11:50:45 DEBUG: Index pg_type_oid_index: Pages 5; Tuples
> 144: Deleted 795.
> CPU 0.00s/0.02u sec elapsed 0.01 sec.
>
>
>
> Dave
>
>
>
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Chantal Ackermann
> Sent: Friday, March 08, 2002 11:09 AM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] vacuum
>
>
> hello all,
>
> I try to call VACUUM ANALYZE through a PreparedStatement. As the logfile
> only
> lists debug messages for VACUUM that I start in psql I suspect that the
> the
> VACUUM in my java app is never called.
>
> Prepared Statement prepVacuumAnalyze = con.prepareStatement( "VACUUM
> ANALYZE"
> );
> prepVacuumAnalyze.execute();
> con.commit(); // auto commit is off
>
> Is it not possible to call such SQL commands in jdbc?
>
> thank you
> Chantal
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html