From frum@ar-sd.net Mon Jun 26 14:19:30 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 46AFD9F9FE3 for ; Mon, 26 Jun 2006 11:19:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 74261-07 for ; Mon, 26 Jun 2006 11:19:21 -0300 (ADT) X-Greylist: delayed 00:23:34.455919 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 868D79FA226 for ; Mon, 26 Jun 2006 11:19:21 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by svr4.postgresql.org (Postfix) with ESMTP id 55CE05AF04A for ; Mon, 26 Jun 2006 13:55:45 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id C3F872F5AC for ; Mon, 26 Jun 2006 16:50:55 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19782-03 for ; Mon, 26 Jun 2006 16:50:53 +0300 (EEST) Received: from forge (forge.mpsro.dom [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id 0BEDA2F502 for ; Mon, 26 Jun 2006 16:50:53 +0300 (EEST) Message-ID: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> From: "Andy" To: Subject: Problem Setting DateStyle Date: Mon, 26 Jun 2006 16:55:51 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0143_01C69941.613F2510" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/226 X-Sequence-Number: 22188 This is a multi-part message in MIME format. ------=_NextPart_000_0143_01C69941.613F2510 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I want to have the DD/MM/YYYY date format in my database without to = specify it with: SET DateStyle=3D'SQL, DMY' at every query.=20 I tried to modify it in postgres.conf >>> datestyle =3D 'European' or = datestyle =3D 'SQL, DMY' and I tried to make=20 alter database test5 SET DateStyle=3D'SQL, DMY'; .... none of these worked.=20 If I run in a session=20 SET DateStyle=3D'SQL, DMY'=20 then it is ok for that session.=20 How can I make it default for the whole system or at least for some = databases? OS: Suse 10, pgsql 8.0.3. Regards, Andy. ------=_NextPart_000_0143_01C69941.613F2510 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I want to have the DD/MM/YYYY date = format in my=20 database without to specify it with:
SET DateStyle=3D'SQL, DMY' at every = query.=20
 
I tried to modify it in postgres.conf = >>>=20 datestyle =3D 'European' or datestyle =3D 'SQL, DMY'
and I tried to make
alter database test5 SET = DateStyle=3D'SQL,=20 DMY';
 
.... none of these worked. =
 
If I run in a session
SET DateStyle=3D'SQL, DMY' =
then it is ok for that session. =
 
How can I make it default for the whole = system or=20 at least for some databases?
 
OS: Suse 10, pgsql 8.0.3.
 
Regards,
 
Andy.
------=_NextPart_000_0143_01C69941.613F2510-- From tgl@sss.pgh.pa.us Mon Jun 26 14:50:54 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 53C519F9AD3 for ; Mon, 26 Jun 2006 11:50:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 82369-01 for ; Mon, 26 Jun 2006 11:50:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 536D29F9FE3 for ; Mon, 26 Jun 2006 11:50:49 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k5QEofB6029136; Mon, 26 Jun 2006 10:50:41 -0400 (EDT) To: "Andy" cc: pgsql-admin@postgresql.org Subject: Re: Problem Setting DateStyle In-reply-to: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> Comments: In-reply-to "Andy" message dated "Mon, 26 Jun 2006 16:55:51 +0300" Date: Mon, 26 Jun 2006 10:50:41 -0400 Message-ID: <29135.1151333441@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/228 X-Sequence-Number: 22190 "Andy" writes: > I tried to modify it in postgres.conf >>> datestyle = 'European' or > datestyle = 'SQL, DMY' > and I tried to make > alter database test5 SET DateStyle='SQL, DMY'; > .... none of these worked. They work for me. Perhaps you should show us exactly what you did and what happened. regards, tom lane From frum@ar-sd.net Mon Jun 26 15:15:17 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 86B4D9F9FE3 for ; Mon, 26 Jun 2006 12:15:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09717-03 for ; Mon, 26 Jun 2006 12:15:11 -0300 (ADT) X-Greylist: delayed 01:19:35.09656 by SQLgrey- Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by postgresql.org (Postfix) with ESMTP id 133579F9AD3 for ; Mon, 26 Jun 2006 12:15:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 43E782FA31; Mon, 26 Jun 2006 18:10:22 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21328-01; Mon, 26 Jun 2006 18:10:19 +0300 (EEST) Received: from forge (forge.mpsro.dom [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id 7735A2F7BC; Mon, 26 Jun 2006 18:10:19 +0300 (EEST) Message-ID: <003801c69933$58bad960$0b00a8c0@mpsro.dom> From: "Andy" To: "Tom Lane" Cc: References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> Subject: Re: Problem Setting DateStyle Date: Mon, 26 Jun 2006 18:15:20 +0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0035_01C6994C.7C583E80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/229 X-Sequence-Number: 22191 This is a multi-part message in MIME format. ------=_NextPart_000_0035_01C6994C.7C583E80 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Steps: 1. show datestyle DateStyle ISO, DMY 2. set datestyle to 'SQL, DMY'; show datestyle; DateStyle SQL, DMY >>>>>>>>>> this should be the good result. Now the tries: Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart the DB server. show datestyle DateStyle ISO, DMY ... there is no change. the other try: alter database test2 set datestyle to 'SQL, DMY'; SQL executed. show datestyle DateStyle ISO, DMY the same... Am I missing something??? If I set set datestyle to 'SQL, DMY' in a connection session then it works well for that session. I need this type of format: auftragsdatum 27/06/2005 27/06/2005 27/06/2005 27/06/2005 27/06/2005 27/06/2005 21/11/2005 09/12/2005 07/07/2005 29/06/2005 I don't know what am I missing in the configuration. I attach the postgres.conf. Best regards, Andy. ----- Original Message ----- From: "Tom Lane" To: "Andy" Cc: Sent: Monday, June 26, 2006 5:50 PM Subject: Re: [ADMIN] Problem Setting DateStyle > "Andy" writes: >> I tried to modify it in postgres.conf >>> datestyle = 'European' or >> datestyle = 'SQL, DMY' >> and I tried to make >> alter database test5 SET DateStyle='SQL, DMY'; > >> .... none of these worked. > > They work for me. Perhaps you should show us exactly what you did and > what happened. > > regards, tom lane > > ------=_NextPart_000_0035_01C6994C.7C583E80 Content-Type: application/octet-stream; name="postgresql.conf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="postgresql.conf" # -----------------------------=0A= # PostgreSQL configuration file=0A= # -----------------------------=0A= #=0A= # This file consists of lines of the form:=0A= #=0A= # name =3D value=0A= #=0A= # (The '=3D' is optional.) White space may be used. Comments are = introduced=0A= # with '#' anywhere on a line. The complete list of option names and=0A= # allowed values can be found in the PostgreSQL documentation. The=0A= # commented-out settings shown in this file represent the default values.=0A= #=0A= # Please note that re-commenting a setting is NOT sufficient to revert it=0A= # to the default value, unless you restart the postmaster.=0A= #=0A= # Any option can also be given as a command line switch to the=0A= # postmaster, e.g. 'postmaster -c log_connections=3Don'. Some options=0A= # can be changed at run-time with the 'SET' SQL command.=0A= #=0A= # This file is read on postmaster startup and when the postmaster=0A= # receives a SIGHUP. If you edit the file on a running system, you have =0A= # to SIGHUP the postmaster for the changes to take effect, or use =0A= # "pg_ctl reload". Some settings, such as listen_address, require=0A= # a postmaster shutdown and restart to take effect.=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # FILE LOCATIONS=0A= #------------------------------------------------------------------------= ---=0A= =0A= # The default values of these variables are driven from the -D command = line=0A= # switch or PGDATA environment variable, represented here as ConfigDir.=0A= # data_directory =3D 'ConfigDir' # use data in another directory=0A= # hba_file =3D 'ConfigDir/pg_hba.conf' # the host-based authentication = file=0A= # ident_file =3D 'ConfigDir/pg_ident.conf' # the IDENT configuration = file=0A= =0A= # If external_pid_file is not explicitly set, no extra pid file is = written.=0A= # external_pid_file =3D '(none)' # write an extra pid file=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # CONNECTIONS AND AUTHENTICATION=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Connection Settings -=0A= =0A= #listen_addresses =3D 'localhost' # what IP interface(s) to listen on; =0A= # defaults to localhost, '*' =3D any=0A= listen_addresses =3D 'localhost, 192.168.0.10' =0A= =0A= #port =3D 5432=0A= max_connections =3D 50=0A= # note: increasing max_connections costs about 500 bytes of shared=0A= # memory per connection slot, in addition to costs from shared_buffers=0A= # and max_locks_per_transaction.=0A= #superuser_reserved_connections =3D 2=0A= #unix_socket_directory =3D ''=0A= #unix_socket_group =3D ''=0A= #unix_socket_permissions =3D 0777 # octal=0A= #rendezvous_name =3D '' # defaults to the computer name=0A= =0A= # - Security & Authentication -=0A= =0A= #authentication_timeout =3D 60 # 1-600, in seconds=0A= #ssl =3D false=0A= #password_encryption =3D true=0A= #krb_server_keyfile =3D ''=0A= #db_user_namespace =3D false=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # RESOURCE USAGE (except WAL)=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Memory -=0A= =0A= #shared_buffers =3D 1000 # min 16, at least max_connections*2, 8KB each=0A= #work_mem =3D 1024 # min 64, size in KB=0A= #maintenance_work_mem =3D 16384 # min 1024, size in KB=0A= #max_stack_depth =3D 2048 # min 100, size in KB=0A= =0A= #2005.05.11 - andy=0A= #shared_buffers =3D 28160 # 220MB =3D 220 x 1024 x 1024 / (8 x 1024) = (8KB)=0A= #shared_buffers =3D 5000 # 220MB =3D 220 x 1024 x 1024 / (8 x 1024) = (8KB)=0A= shared_buffers =3D 5120 # 40MB =3D 40 x 1024 x 1024 / (8 x 1024) (8KB)=0A= #work_mem =3D 10240 # 10MB =3D 10 x 1024 KB=0A= work_mem =3D 2048 # 2MB =3D 2 x 1024 KB=0A= maintenance_work_mem =3D 51200 # 50MB =3D 50 x 1024 KB=0A= =0A= =0A= =0A= =0A= # - Free Space Map -=0A= =0A= #max_fsm_pages =3D 20000 # min max_fsm_relations*16, 6 bytes each=0A= #max_fsm_relations =3D 1000 # min 100, ~50 bytes each=0A= =0A= # - Kernel Resource Usage -=0A= =0A= #max_files_per_process =3D 1000 # min 25=0A= #preload_libraries =3D ''=0A= =0A= # - Cost-Based Vacuum Delay -=0A= =0A= #vacuum_cost_delay =3D 0 # 0-1000 milliseconds=0A= #vacuum_cost_page_hit =3D 1 # 0-10000 credits=0A= #vacuum_cost_page_miss =3D 10 # 0-10000 credits=0A= #vacuum_cost_page_dirty =3D 20 # 0-10000 credits=0A= #vacuum_cost_limit =3D 200 # 0-10000 credits=0A= =0A= # - Background writer -=0A= =0A= #bgwriter_delay =3D 200 # 10-10000 milliseconds between rounds=0A= #bgwriter_percent =3D 1 # 0-100% of dirty buffers in each round=0A= #bgwriter_maxpages =3D 100 # 0-1000 buffers max per round=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # WRITE AHEAD LOG=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Settings -=0A= =0A= #fsync =3D true # turns forced synchronization on or off=0A= #wal_sync_method =3D fsync # the default varies across platforms:=0A= # fsync, fdatasync, open_sync, or open_datasync=0A= #wal_buffers =3D 8 # min 4, 8KB each=0A= #commit_delay =3D 0 # range 0-100000, in microseconds=0A= #commit_siblings =3D 5 # range 1-1000=0A= =0A= # - Checkpoints -=0A= =0A= checkpoint_segments =3D 5 # in logfile segments, min 1, 16MB each=0A= #checkpoint_timeout =3D 300 # range 30-3600, in seconds=0A= #checkpoint_warning =3D 30 # 0 is off, in seconds=0A= =0A= # - Archiving -=0A= =0A= #archive_command =3D '' # command to use to archive a logfile segment=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # QUERY TUNING=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Planner Method Configuration -=0A= =0A= #enable_hashagg =3D true=0A= #enable_hashjoin =3D true=0A= #enable_indexscan =3D true=0A= #enable_mergejoin =3D true=0A= #enable_nestloop =3D true=0A= #enable_seqscan =3D true=0A= #enable_sort =3D true=0A= #enable_tidscan =3D true=0A= =0A= # - Planner Cost Constants -=0A= =0A= #effective_cache_size =3D 1000 # typically 8KB each=0A= random_page_cost =3D 3 # units are one sequential page fetch cost=0A= #cpu_tuple_cost =3D 0.01 # (same)=0A= #cpu_index_tuple_cost =3D 0.001 # (same)=0A= #cpu_operator_cost =3D 0.0025 # (same)=0A= =0A= #effective_cache_size =3D 6400 # 50MB =3D 50 x 1024 / 8 #2005.05.11 - = andy=0A= #effective_cache_size =3D 12800 # 100MB =3D 100 x 1024 / 8 #2005.05.11 - = andy=0A= effective_cache_size =3D 32000 # 250MB =3D 250 x 1024 / 8 #2005.05.11 - = andy=0A= #effective_cache_size =3D 57600 # 450MB =3D 450 x 1024 / 8 #2005.05.11 - = andy=0A= #effective_cache_size =3D 157600 # 450MB =3D 450 x 1024 / 8 #2005.05.11 = - andy=0A= =0A= =0A= # - Genetic Query Optimizer -=0A= =0A= #geqo =3D true=0A= #geqo_threshold =3D 12=0A= #geqo_effort =3D 5 # range 1-10=0A= #geqo_pool_size =3D 0 # selects default based on effort=0A= #geqo_generations =3D 0 # selects default based on effort=0A= #geqo_selection_bias =3D 2.0 # range 1.5-2.0=0A= =0A= # - Other Planner Options -=0A= =0A= #default_statistics_target =3D 10 # range 1-1000=0A= #from_collapse_limit =3D 8=0A= #join_collapse_limit =3D 8 # 1 disables collapsing of explicit JOINs=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # ERROR REPORTING AND LOGGING=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Where to Log -=0A= =0A= #log_destination =3D 'stderr' # Valid values are combinations of stderr,=0A= # syslog and eventlog, depending on=0A= # platform.=0A= =0A= # This is relevant when logging to stderr:=0A= #redirect_stderr =3D false # Enable capturing of stderr into log = files.=0A= # These are only relevant if redirect_stderr is true:=0A= #log_directory =3D 'pg_log' # Directory where log files are written.=0A= # May be specified absolute or relative to = PGDATA=0A= #log_filename =3D 'postgresql-%Y-%m-%d_%H%M%S.log' # Log file name = pattern.=0A= # May include strftime() escapes=0A= #log_truncate_on_rotation =3D false # If true, any existing log file of = the =0A= # same name as the new log file will be = truncated=0A= # rather than appended to. But such = truncation=0A= # only occurs on time-driven rotation,=0A= # not on restarts or size-driven rotation.=0A= # Default is false, meaning append to = existing =0A= # files in all cases.=0A= #log_rotation_age =3D 1440 # Automatic rotation of logfiles will = happen after=0A= # so many minutes. 0 to disable.=0A= #log_rotation_size =3D 10240 # Automatic rotation of logfiles will = happen after=0A= # so many kilobytes of log output. 0 to = disable.=0A= =0A= # These are relevant when logging to syslog:=0A= #syslog_facility =3D 'LOCAL0'=0A= #syslog_ident =3D 'postgres'=0A= =0A= =0A= # - When to Log -=0A= =0A= client_min_messages =3D notice # Values, in order of decreasing detail:=0A= # debug5, debug4, debug3, debug2, debug1,=0A= # log, notice, warning, error=0A= =0A= log_min_messages =3D notice # Values, in order of decreasing detail:=0A= # debug5, debug4, debug3, debug2, debug1,=0A= # info, notice, warning, error, log, fatal,=0A= # panic=0A= =0A= #log_error_verbosity =3D default # terse, default, or verbose messages=0A= =0A= #log_min_error_statement =3D panic # Values in order of increasing = severity:=0A= # debug5, debug4, debug3, debug2, debug1,=0A= # info, notice, warning, error, panic(off)=0A= =0A= #log_min_duration_statement =3D -1 # -1 is disabled, in milliseconds.=0A= =0A= #silent_mode =3D false # DO NOT USE without syslog or redirect_stderr=0A= =0A= # - What to Log -=0A= =0A= #debug_print_parse =3D false=0A= #debug_print_rewritten =3D false=0A= #debug_print_plan =3D false=0A= #debug_pretty_print =3D false=0A= log_connections =3D true=0A= #log_disconnections =3D false=0A= log_duration =3D true=0A= log_line_prefix =3D '%t %p - %l ' # e.g. '<%u%%%d> ' =0A= # %u=3Duser name %d=3Ddatabase name=0A= # %r=3Dremote host and port=0A= # %p=3DPID %t=3Dtimestamp %i=3Dcommand tag=0A= # %c=3Dsession id %l=3Dsession line number=0A= # %s=3Dsession start timestamp %x=3Dtransaction id=0A= # %q=3Dstop here in non-session processes=0A= # %%=3D'%'=0A= log_statement =3D 'all' # none, mod, ddl, all=0A= #log_hostname =3D true ## andy - don't use IT!=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # RUNTIME STATISTICS=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Statistics Monitoring -=0A= =0A= #log_parser_stats =3D false=0A= #log_planner_stats =3D false=0A= #log_executor_stats =3D false=0A= #log_statement_stats =3D false=0A= =0A= # - Query/Index Statistics Collector -=0A= =0A= #stats_start_collector =3D true=0A= #stats_command_string =3D false=0A= #stats_block_level =3D false=0A= #stats_row_level =3D false=0A= #stats_reset_on_server_start =3D true=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # CLIENT CONNECTION DEFAULTS=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Statement Behavior -=0A= =0A= #search_path =3D '$user,public' # schema names=0A= #default_tablespace =3D '' # a tablespace name, or '' for default=0A= #check_function_bodies =3D true=0A= #default_transaction_isolation =3D 'read committed'=0A= #default_transaction_read_only =3D false=0A= #statement_timeout =3D 0 # 0 is disabled, in milliseconds=0A= =0A= # - Locale and Formatting -=0A= =0A= #datestyle =3D 'iso, mdy'=0A= datestyle =3D 'SQL, DMY'=0A= #datestyle =3D 'ISO,US'=0A= #timezone =3D unknown # actually, defaults to TZ environment setting=0A= #australian_timezones =3D false=0A= #extra_float_digits =3D 0 # min -15, max 2=0A= #client_encoding =3D sql_ascii # actually, defaults to database encoding=0A= =0A= # These settings are initialized by initdb -- they might be changed=0A= lc_messages =3D 'en_US.UTF-8' # locale for system error message strings=0A= lc_monetary =3D 'en_US.UTF-8' # locale for monetary formatting=0A= lc_numeric =3D 'en_US.UTF-8' # locale for number formatting=0A= #lc_time =3D 'en_US.UTF-8' # locale for time formatting=0A= =0A= # - Other Defaults -=0A= =0A= #explain_pretty_print =3D true=0A= #dynamic_library_path =3D '$libdir'=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # LOCK MANAGEMENT=0A= #------------------------------------------------------------------------= ---=0A= =0A= #deadlock_timeout =3D 1000 # in milliseconds=0A= #max_locks_per_transaction =3D 64 # min 10, ~200*max_connections bytes = each=0A= =0A= =0A= #------------------------------------------------------------------------= ---=0A= # VERSION/PLATFORM COMPATIBILITY=0A= #------------------------------------------------------------------------= ---=0A= =0A= # - Previous Postgres Versions -=0A= =0A= #add_missing_from =3D true=0A= #regex_flavor =3D advanced # advanced, extended, or basic=0A= #sql_inheritance =3D true=0A= #default_with_oids =3D true=0A= =0A= # - Other Platforms & Clients -=0A= =0A= #transform_null_equals =3D false=0A= ------=_NextPart_000_0035_01C6994C.7C583E80-- From alvherre@commandprompt.com Mon Jun 26 15:59:26 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F17619FA6A2 for ; Mon, 26 Jun 2006 12:59:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 50606-05 for ; Mon, 26 Jun 2006 12:59:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from alvh.no-ip.org (201-221-201-100.bk11-dsl.surnet.cl [201.221.201.100]) by postgresql.org (Postfix) with ESMTP id F3E909FA226 for ; Mon, 26 Jun 2006 12:59:17 -0300 (ADT) Received: by alvh.no-ip.org (Postfix, from userid 1000) id B6E16C70337; Mon, 26 Jun 2006 11:59:15 -0400 (CLT) Date: Mon, 26 Jun 2006 11:59:15 -0400 From: Alvaro Herrera To: Andy Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Problem Setting DateStyle Message-ID: <20060626155915.GC8999@alvh.no-ip.org> Mail-Followup-To: Andy , Tom Lane , pgsql-admin@postgresql.org References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> <003801c69933$58bad960$0b00a8c0@mpsro.dom> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003801c69933$58bad960$0b00a8c0@mpsro.dom> User-Agent: Mutt/1.5.11+cvs20060403 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/231 X-Sequence-Number: 22193 Andy wrote: > Now the tries: > Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart the > DB server. > show datestyle > DateStyle > ISO, DMY Perhaps you edited the wrong postgresql.conf file, or restarted the wrong server, or forgot to uncomment the line. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support From smarlowe@g2switchworks.com Mon Jun 26 16:11:15 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 781B89FA6B2 for ; Mon, 26 Jun 2006 13:11:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 50671-08 for ; Mon, 26 Jun 2006 13:11:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id E93CE9F9AD3 for ; Mon, 26 Jun 2006 13:11:04 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Mon, 26 Jun 2006 16:11:02 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 26 Jun 2006 11:11:02 -0500 Subject: Re: Problem Setting DateStyle From: Scott Marlowe To: Andy Cc: Tom Lane , pgsql-admin@postgresql.org In-Reply-To: <003801c69933$58bad960$0b00a8c0@mpsro.dom> References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> <003801c69933$58bad960$0b00a8c0@mpsro.dom> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1151338262.4215.51.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 26 Jun 2006 11:11:02 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/233 X-Sequence-Number: 22195 On Mon, 2006-06-26 at 10:15, Andy wrote: > Steps: > 1. > show datestyle > DateStyle > ISO, DMY > > > 2. > set datestyle to 'SQL, DMY'; > show datestyle; > DateStyle > SQL, DMY > > >>>>>>>>>> this should be the good result. > > Now the tries: > Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart the > DB server. > show datestyle > DateStyle > ISO, DMY > > ... there is no change. > > the other try: > alter database test2 set datestyle to 'SQL, DMY'; > SQL executed. > show datestyle > DateStyle > ISO, DMY > > > the same... Have you set a date style for this particular database (not the cluster) with an alter database statement before? I'd try to alter the database to have a certain datestyle and see if that helps. From postgresql@aranya.com Tue Jun 27 00:20:46 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 257499FA2F7 for ; Mon, 26 Jun 2006 21:20:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 49441-07 for ; Mon, 26 Jun 2006 21:20:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by postgresql.org (Postfix) with ESMTP id 2377B9FAC76 for ; Mon, 26 Jun 2006 21:20:41 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so2323372ugf for ; Mon, 26 Jun 2006 17:20:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=C+3tnXbKILCTEwfnKhEVJpkALRkP1n0NfgeY64LRr1e38BjyqTlqYzCXOFSOwsQndCFS/wFa/D30v2j1hliceMngNHnfZUZDgiDdU5gT/MOoavp5q9CG9Gn1K+oXwglmkz5cqWpGAh+vKuzBpINXCQ6Jnz9biv1kimBzoOC6Nh8= Received: by 10.78.97.7 with SMTP id u7mr2322115hub; Mon, 26 Jun 2006 17:20:40 -0700 (PDT) Received: by 10.78.29.2 with HTTP; Mon, 26 Jun 2006 17:20:40 -0700 (PDT) Message-ID: Date: Mon, 26 Jun 2006 19:20:40 -0500 From: "Aaron Bono" To: "Scott Marlowe" Subject: Re: Problem Setting DateStyle Cc: Andy , "Tom Lane" , pgsql-admin@postgresql.org In-Reply-To: <1151338262.4215.51.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10681_30926202.1151367640185" References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> <003801c69933$58bad960$0b00a8c0@mpsro.dom> <1151338262.4215.51.camel@state.g2switchworks.com> X-Google-Sender-Auth: a085abff50a0369d X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/249 X-Sequence-Number: 22211 ------=_Part_10681_30926202.1151367640185 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Also, and I know this sounds stupid, you may check to see if the database really restarted. I recently got a new server and for some reason when I use the restart script found in /etc/init.d/postgres it doesn't actually restart the server (the shutdown fails) but when I go to the control panel installed by my ISP it restarts wonderfully. I saw what was happening when I looked at the date the postgres process started. -Aaron On 6/26/06, Scott Marlowe wrote: > > On Mon, 2006-06-26 at 10:15, Andy wrote: > > Steps: > > 1. > > show datestyle > > DateStyle > > ISO, DMY > > > > > > 2. > > set datestyle to 'SQL, DMY'; > > show datestyle; > > DateStyle > > SQL, DMY > > > > >>>>>>>>>> this should be the good result. > > > > Now the tries: > > Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart > the > > DB server. > > show datestyle > > DateStyle > > ISO, DMY > > > > ... there is no change. > > > > the other try: > > alter database test2 set datestyle to 'SQL, DMY'; > > SQL executed. > > show datestyle > > DateStyle > > ISO, DMY > > > > > > the same... > > > Have you set a date style for this particular database (not the cluster) > with an alter database statement before? > > I'd try to alter the database to have a certain datestyle and see if > that helps. > > ------=_Part_10681_30926202.1151367640185 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Also, and I know this sounds stupid, you may check to see if the database really restarted.  I recently got a new server and for some reason when I use the restart script found in /etc/init.d/postgres it doesn't actually restart the server (the shutdown fails) but when I go to the control panel installed by my ISP it restarts wonderfully.  I saw what was happening when I looked at the date the postgres process started.

-Aaron

On 6/26/06, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
On Mon, 2006-06-26 at 10:15, Andy wrote:
> Steps:
> 1.
> show datestyle
>       DateStyle
>       ISO, DMY
>
>
> 2.
> set datestyle to 'SQL, DMY';
> show datestyle;
>       DateStyle
>       SQL, DMY
>
> >>>>>>>>>> this should be the good result.
>
> Now the tries:
> Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart the
> DB server.
> show datestyle
>       DateStyle
>       ISO, DMY
>
> ... there is no change.
>
> the other try:
> alter database test2 set datestyle to 'SQL, DMY';
> SQL executed.
> show datestyle
>       DateStyle
>       ISO, DMY
>
>
> the same...


Have you set a date style for this particular database (not the cluster)
with an alter database statement before?

I'd try to alter the database to have a certain datestyle and see if
that helps.

------=_Part_10681_30926202.1151367640185-- From frum@ar-sd.net Tue Jun 27 07:12:03 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A65889FA490 for ; Tue, 27 Jun 2006 04:12:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 24479-03 for ; Tue, 27 Jun 2006 04:11:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by postgresql.org (Postfix) with ESMTP id DFFED9FA395 for ; Tue, 27 Jun 2006 04:11:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 26A192CB40; Tue, 27 Jun 2006 10:07:02 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26119-06; Tue, 27 Jun 2006 10:06:57 +0300 (EEST) Received: from forge (forge.mpsro.dom [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id 1DC532B0CC; Tue, 27 Jun 2006 10:06:57 +0300 (EEST) Message-ID: <008b01c699b8$fee9df90$0b00a8c0@mpsro.dom> From: "Andy" To: "Aaron Bono" , "Scott Marlowe" Cc: "Tom Lane" , References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> <003801c69933$58bad960$0b00a8c0@mpsro.dom> <1151338262.4215.51.camel@state.g2switchworks.com> Subject: Re: [SOLVED] Problem Setting DateStyle Date: Tue, 27 Jun 2006 10:12:03 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01C699D2.22C0CB40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/252 X-Sequence-Number: 22214 This is a multi-part message in MIME format. ------=_NextPart_000_0088_01C699D2.22C0CB40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ups, sorry folks,=20 I use pgadmin3 for database access and it seems that it executes SET = DateStyle=3DISO; every time it connects.=20 Same with phppgadmin4. If i connect with psql then it works fine.=20 Anyway good to know.=20 Best regards, Andy. ----- Original Message -----=20 From: Aaron Bono=20 To: Scott Marlowe=20 Cc: Andy ; Tom Lane ; pgsql-admin@postgresql.org=20 Sent: Tuesday, June 27, 2006 3:20 AM Subject: Re: [ADMIN] Problem Setting DateStyle Also, and I know this sounds stupid, you may check to see if the = database really restarted. I recently got a new server and for some = reason when I use the restart script found in /etc/init.d/postgres it = doesn't actually restart the server (the shutdown fails) but when I go = to the control panel installed by my ISP it restarts wonderfully. I saw = what was happening when I looked at the date the postgres process = started.=20 -Aaron On 6/26/06, Scott Marlowe wrote: On Mon, 2006-06-26 at 10:15, Andy wrote: > Steps: > 1. > show datestyle > DateStyle > ISO, DMY > > > 2. > set datestyle to 'SQL, DMY'; > show datestyle;=20 > DateStyle > SQL, DMY > > >>>>>>>>>> this should be the good result. > > Now the tries: > Edit the postgresql.conf. Set datestyle =3D 'SQL, DMY' parameter. = Restart the=20 > DB server. > show datestyle > DateStyle > ISO, DMY > > ... there is no change. > > the other try: > alter database test2 set datestyle to 'SQL, DMY'; > SQL executed. > show datestyle > DateStyle > ISO, DMY > > > the same... Have you set a date style for this particular database (not the = cluster) with an alter database statement before?=20 I'd try to alter the database to have a certain datestyle and see if that helps. ------=_NextPart_000_0088_01C699D2.22C0CB40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ups, sorry folks,
 
I use pgadmin3 for database access and = it seems=20 that it executes SET DateStyle=3DISO; = every time it=20 connects.
Same with phppgadmin4. If i connect with psql then = it works fine.=20
 
Anyway good to know.
 
Best regards,
Andy.
 
----- Original Message -----
From:=20 Aaron=20 Bono
Cc: Andy ; Tom Lane ; pgsql-admin@postgresql.org=
Sent: Tuesday, June 27, 2006 = 3:20=20 AM
Subject: Re: [ADMIN] Problem = Setting=20 DateStyle

Also, and I know this sounds stupid, you may check to = see if=20 the database really restarted.  I recently got a new server and = for some=20 reason when I use the restart script found in /etc/init.d/postgres it = doesn't=20 actually restart the server (the shutdown fails) but when I go to the = control=20 panel installed by my ISP it restarts wonderfully.  I saw what = was=20 happening when I looked at the date the postgres process started.=20

-Aaron

On 6/26/06, Scott=20 Marlowe <smarlowe@g2switchworks.com= >=20 wrote:
On=20 Mon, 2006-06-26 at 10:15, Andy wrote:
> Steps:
> = 1.
> show=20 datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
>
> 2.
> set datestyle to 'SQL, = DMY';
>=20 show datestyle;
>      =20 DateStyle
>       SQL,=20 DMY
>
> >>>>>>>>>> this = should be=20 the good result.
>
> Now the tries:
> Edit the=20 postgresql.conf. Set datestyle =3D 'SQL, DMY' parameter. Restart the =
>=20 DB server.
> show=20 datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
> ... there is no change.
>
> the = other=20 try:
> alter database test2 set datestyle to 'SQL, = DMY';
> SQL=20 executed.
> show = datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
>
> the same...


Have you set a = date style=20 for this particular database (not the cluster)
with an alter = database=20 statement before?

I'd try to alter the database to have a = certain=20 datestyle and see if
that=20 helps.

------=_NextPart_000_0088_01C699D2.22C0CB40--