then.
I opened an issue here: https://github.com/citusdata/pg_cron/issues/290
We reproduced the problem with postgresql 13/ postgresql-13-cron.
We could fix the problem temporarily with setting cron.timezone to 'GMT+24' in
/etc/postgresql//main/postgresql.conf
Thank you in advance for
Stefan Bellon:
>
> I'm on unstable and up-to-date and I get mails from cron with the
> following content:
>
> Insecure dependency in exec while running with -T switch at
> /usr/sbin/pg_maintenance line 49. calling vacuumdb on cluster 7.4/main
> failed
This has already been reported as bug #357237
On Thu, 2006-03-16 at 13:13 -0800, Casey T. Deccio wrote:
> However, AFAICT, the code in pg_maintenance looks like it is secure
> enough for -T. In fact, it doesn't fail when I run it. Can you
> run /usr/sbin/pg_maintenance from the shell without error?
>
I spoke too soon. My apt-get upgrade f
Casey T. Deccio wrote:
> On Thu, 2006-03-16 at 18:16 +0100, Stefan Bellon wrote:
> > [EMAIL PROTECTED]:~$ grep -- "-T" /usr/sbin/pg_maintenance
> You won't find it that way, because it is a command-line switch
> combined with another:
> #!/usr/bin/perl -wT
Argh! :-}
[snip]
> However, AFAICT,
On Thu, 2006-03-16 at 18:16 +0100, Stefan Bellon wrote:
> [EMAIL PROTECTED]:~$ cat -n /usr/sbin/pg_maintenance | head -50 | tail -7
> 44 @options = ('--cluster', "$v/$c", '-a');
> 45 push @options, '-f' if $full;
> 46 push @options, '-z' if $analyze;
> 47
Casey T. Deccio wrote:
> On Thu, 2006-03-16 at 11:37 +0100, Stefan Bellon wrote:
> > Insecure dependency in exec while running with -T switch at
> > /usr/sbin/pg_maintenance line 49. calling vacuumdb on cluster
> > 7.4/main failed
> Seems that the -T switch is new to the /usr/sbin/pg_maintenance
>
On Thu, 2006-03-16 at 11:37 +0100, Stefan Bellon wrote:
> Insecure dependency in exec while running with -T switch at
> /usr/sbin/pg_maintenance line 49. calling vacuumdb on cluster 7.4/main
> failed
>
Seems that the -T switch is new to the /usr/sbin/pg_maintenance script.
What does line 49 read
I'm on unstable and up-to-date and I get mails from cron with the
following content:
Insecure dependency in exec while running with -T switch at
/usr/sbin/pg_maintenance line 49. calling vacuumdb on cluster 7.4/main
failed
What does it mean and how can I fix it (assuming something is broken)?
TI
i try to install postgreSQL on debian testing, but i have problem :
> $> dpkg -l | grep postgre
> ii postgresql 7.1.3-4Object-relational SQL database, descended fr
> ii postgresql-cli 7.1.3-4Front-end programs for PostgreSQL
> ii postgresql-con 7.1.3-4Additional faci
On Sat, Jul 21, 2001 at 06:42:46AM +, p wrote:
> > On Wed, Jul 11, 2001 at 09:04:01PM -0400, Brian Schramm wrote:
>
> [snip]
> > > problem is that the postgresql database says that my username does not
> > > exist in the pg_shadow file any more. I thought that this was a problem
> > > that
>
> On Wed, Jul 11, 2001 at 09:04:01PM -0400, Brian Schramm wrote:
[snip]
> > problem is that the postgresql database says that my username does not
> > exist in the pg_shadow file any more. I thought that this was a problem
> > that
> > the users did not transfer so I created another user with th
On Fri, Jul 13, 2001 at 08:43:05AM -0400, Brian Schramm wrote:
> I tryed that. I can get in by the postgres user but cannot
> create a user from there. It does not give me an error message
> but does not create the user eather.
if you can get into the database as user postgres from the
command l
I tryed that. I can get in by the postgres user but cannot create a user
from there. It does not give me an error message but does not create the
user eather.
Brian
Brian Schramm
[EMAIL PROTECTED]ICQ 104442754 AIM schrammbrian
www.linuxexpert.org
On Fri, 13 Jul 2001, will
On Wed, Jul 11, 2001 at 09:04:01PM -0400, Brian Schramm wrote:
> I just upgraded from potato to Progeny Debian. The upgrade went fairly
> smooth (thanks Progeny) and the system seems to be working well. My
> problem is that the postgresql database says that my username does not
> exist in the pg_
I just upgraded from potato to Progeny Debian. The upgrade went fairly
smooth (thanks Progeny) and the system seems to be working well. My
problem is that the postgresql database says that my username does not
exist in the pg_shadow file any more. I thought that this was a problem that
the users
Hello,
I'm running postgresql 7.0.3-4, on debian unstable, and I have trouble to
connecting databases via odbc. I use unixodbc 2.0.3-1, and I can see the data
source in the DataManager, but when I try to connect I get the following error:
'[unixODBC]Could not connect to the server;
Could not co
Hello,
I'm running postgresql 7.0.3-4, on debian unstable, and I have trouble to
connecting databases via odbc. I use unixodbc 2.0.3-1, and I can see the data
source in the DataManager, but when I try to connect I get the following error:
'[unixODBC]Could not connect to the server;
Could not co
I have a cron job which dump my postgresql database each day. For the
past few days it reports a problem:
failed sanity check, type with oid 96867 was not found
Does anybody know what I should do to fix the problem?
Regards.
Johann
--
J.H. Spies, Hugenotestraat 29, Posbus 80, Franschhoek, 76
Michele Bianchi wrote:
>
>i found these problems in /usr/lib/postgresql/bin/postgresql-startup
>
>i fix line 131 with a \ before *:
>
> minbuf=`expr $BACKENDCOUNT \* 2`
>
>and line 132 with the ":
>
> if [ -n "$BUFFERS" ]
>
>i use the bash... i think it's better to surrou
Hello,
I downloaded the postgresql packages and the jdbc stuff and am trying to
get the included examples working. I get the following message when I
run the "basic" example in the jdbc package.
Connecting to Database URL = jdbc.postgresql://dragonknoll:5432/doug
Exception caught.
java.sql.SQLEx
20 matches
Mail list logo
