Professional Web Applications Themes

segmentation fault - PostgreSQL / PGSQL

hello to all I have the following problem, when making massive update of a table, I received the message "segmentation fault" without no other data of the error in log. Some idea of because it gives east message? I am using gentoo postgres 7.4.6 dual processor HP proliant 5 gigabyte of ram 147 gigabytes of hd. 47 free . BTW the column to update is the one of indice gist of FTS and the table has 22 million registries. any clue? best regards MDC __________________________________________________ _________ 250MB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo..ar ...

  1. #1

    Default segmentation fault


    hello to all
    I have the following problem, when making massive
    update of a table, I received the message
    "segmentation fault" without no other data of the
    error in log.
    Some idea of because it gives east message?
    I am using
    gentoo
    postgres 7.4.6
    dual processor HP proliant
    5 gigabyte of ram
    147 gigabytes of hd.
    47 free .

    BTW the column to update is the one of indice gist of
    FTS and the table has 22 million registries.
    any clue?
    best regards
    MDC






    __________________________________________________ _________
    250MB gratis, Antivirus y Antispam
    Correo Yahoo!, el mejor correo web del mundo
    http://correo..ar

    ---------------------------(end of broadcast)---------------------------
    TIP 5: Have you checked our extensive FAQ?

    http://www.postgresql.org/docs/faq

    marcelo Guest

  2. #2

    Default Re: segmentation fault

    On Wed, 9 Mar 2005 14:28:55 -0300 (ART), marcelo Cortez
    <com.ar> wrote: 

    You're doing this from within psql or elsewhere? What logging level
    are you using? How 'massive' is this update? What kind of parameters
    have you set for this database?


    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    L. Friedman com
    LlamaLand http://netllama.linux-sxs.org

    ---------------------------(end of broadcast)---------------------------
    TIP 6: Have you searched our list archives?

    http://archives.postgresql.org

    Lonni Guest

  3. #3

    Default Re: segmentation fault

    Lonni , folks

    configuration data: sorry for long response ;)


    Linux sume 2.6.9-gentoo-r1 #1 SMP Mon Feb 21 10:46:46
    Local time zone
    must
    be set--see zic i686 Intel(R) Xeon(TM) CPU 2.80GHz
    GenuineIntel
    GNU/Linux

    postgres:
    "PostgreSQL 7.4.5 on i686-pc-linux-gnu, compiled by
    GCC gcc (GCC) 3.3.4
    20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2,
    pie-8.7.6)"

    postgresql.conf:

    # -----------------------------
    # PostgreSQL configuration file
    # -----------------------------
    #
    # This file consists of lines of the form:
    #
    # name = value
    #
    # (The '=' is optional.) White space may be used.
    Comments are
    introduced
    # with '#' anywhere on a line. The complete list of
    option names and #
    allowed values can be found in the PostgreSQL
    doentation. The #
    commented-out settings shown in this file represent
    the default values.
    #
    # Any option can also be given as a command line
    switch to the
    # postmaster, e.g. 'postmaster -c log_connections=on'.
    Some options #
    can
    be changed at run-time with the 'SET' SQL command.
    #
    # This file is read on postmaster startup and when the
    postmaster
    # receives a SIGHUP. If you edit the file on a running
    system, you have
    #
    to SIGHUP the postmaster for the changes to take
    effect, or use
    # "pg_ctl reload".


    #---------------------------------------------------------------------------
    # CONNECTIONS AND AUTHENTICATION
    #---------------------------------------------------------------------------

    # - Connection Settings -

    #tcpip_socket = false
    max_connections = 100
    # note: increasing max_connections costs about
    500 bytes of
    shared
    # memory per connection slot, in addition to costs
    from
    shared_buffers # and max_locks_per_transaction.
    #superuser_reserved_connections = 2
    #port = 5432
    #unix_socket_directory = ''
    #unix_socket_group = ''
    #unix_socket_permissions = 0777 # octal
    #virtual_host = '' # what interface to
    listen on; defaults
    to
    any #rendezvous_name = '' # defaults to the
    computer name

    # - Security & Authentication -

    #authentication_timeout = 60 # 1-600, in seconds
    #ssl = false
    #password_encryption = true
    #krb_server_keyfile = ''
    #db_user_namespace = false


    #---------------------------------------------------------------------------
    # RESOURCE USAGE (except WAL)
    #---------------------------------------------------------------------------

    # - Memory -

    shared_buffers = 8192 # min 16, at least
    max_connections*2,
    8KB
    each sort_mem = 8192 # min 64, size in
    KB
    #vacuum_mem = 8192 # min 1024, size in KB

    # - Free Space Map -

    #max_fsm_pages = 20000 # min
    max_fsm_relations*16, 6 bytes
    each
    #max_fsm_relations = 1000 # min 100, ~50 bytes
    each

    # - Kernel Resource Usage -

    #max_files_per_process = 1000 # min 25
    #preload_libraries = ''


    #---------------------------------------------------------------------------
    # WRITE AHEAD LOG
    #---------------------------------------------------------------------------

    # - Settings -

    fsync = false # turns forced
    synchronization on or
    off
    #wal_sync_method = fsync # the default varies
    across platforms:
    # fsync, fdatasync,
    open_sync, or
    open_datasync
    wal_buffers = 40 # min 4, 8KB each

    # - Checkpoints -

    checkpoint_segments = 9 # in logfile segments,
    min 1, 16MB each
    #checkpoint_timeout = 300 # range 30-3600, in
    seconds
    #checkpoint_warning = 30 # 0 is off, in seconds
    #commit_delay = 0 # range 0-100000, in
    microseconds
    #commit_siblings = 5 # range 1-1000


    #---------------------------------------------------------------------------
    # QUERY TUNING
    #---------------------------------------------------------------------------

    # - Planner Method Enabling -

    #enable_hashagg = true
    #enable_hashjoin = true
    #enable_indexscan = true
    #enable_mergejoin = true
    #enable_nestloop = true
    #enable_seqscan = true
    #enable_sort = true
    #enable_tidscan = true

    # - Planner Cost Constants -

    effective_cache_size = 4000 # typically 8KB each
    #random_page_cost = 4 # units are one
    sequential page fetch
    cost
    #cpu_tuple_cost = 0.01 # (same)
    #cpu_index_tuple_cost = 0.001 # (same)
    #cpu_operator_cost = 0.0025 # (same)

    # - Genetic Query Optimizer -

    #geqo = true
    #geqo_threshold = 11
    #geqo_effort = 1
    #geqo_generations = 0
    #geqo_pool_size = 0 # default based on
    tables in statement,
    # range 128-1024
    #geqo_selection_bias = 2.0 # range 1.5-2.0

    # - Other Planner Options -

    #default_statistics_target = 10 # range 1-1000
    #from_collapse_limit = 8
    #join_collapse_limit = 8 # 1 disables
    collapsing of explicit
    JOINs


    #---------------------------------------------------------------------------
    # ERROR REPORTING AND LOGGING
    #---------------------------------------------------------------------------

    # - Syslog -

    #syslog = 0 # range 0-2; 0=stdout;
    1=both; 2=syslog
    #syslog_facility = 'LOCAL0'
    #syslog_ident = 'postgres'

    # - When to Log -

    #client_min_messages = notice # Values, in order of
    decreasing
    detail:
    # debug5, debug4,
    debug3, debug2,
    debug1, # log, info, notice, warning,
    error

    #log_min_messages = debug5 # Values, in order of
    decreasing
    detail:
    # debug5, debug4,
    debug3, debug2,
    debug1, # info, notice, warning, error,
    log, fatal, # panic

    #log_error_verbosity = verbose # terse, default, or
    verbose messages

    #log_min_error_statement = panic # Values in order of
    increasing
    severity:
    # debug5, debug4,
    debug3, debug2,
    debug1, # info, notice, warning, error,
    panic(off)

    #log_min_duration_statement = -1 # Log all statements
    whose
    # execution time
    exceeds the value, in
    #
    milliseconds. Zero prints all queries. #
    Minus-one disables.

    #silent_mode = false # DO NOT USE without
    Syslog!

    # - What to Log -

    debug_print_p = true
    debug_print_rewritten = true
    debug_print_plan = true
    debug_pretty_print = true
    log_connections = true
    log_duration = true
    log_pid = true
    log_statement = true
    log_timestamp = true
    log_hostname = true
    log_source_port = true


    #---------------------------------------------------------------------------
    # RUNTIME STATISTICS
    #---------------------------------------------------------------------------

    # - Statistics Monitoring -

    #log_pr_stats = false
    #log_planner_stats = false
    #log_executor_stats = false
    #log_statement_stats = false

    # - Query/Index Statistics Collector -

    #stats_start_collector = true
    #stats_command_string = false
    #stats_block_level = false
    #stats_row_level = false
    #stats_reset_on_server_start = true


    #---------------------------------------------------------------------------
    # CLIENT CONNECTION DEFAULTS
    #---------------------------------------------------------------------------

    # - Statement Behavior -

    #search_path = '$user,public' # schema names
    #check_function_bodies = true
    #default_transaction_isolation = 'read committed'
    #default_transaction_read_only = false
    #statement_timeout = 0 # 0 is disabled, in
    milliseconds

    # - Locale and Formatting -


    #datestyle = 'iso, mdy'
    #timezone = unknown # actually, defaults
    to TZ environment
    setting #australian_timezones = false
    #extra_float_digits = 0 # min -15, max 2
    #client_encoding = sql_ascii # actually, defaults
    to database
    encoding

    # These settings are initialized by initdb -- they may
    be changed
    lc_messages = 'C' # locale for system
    error message
    strings
    lc_monetary = 'C' # locale for monetary
    formatting
    lc_numeric = 'C' # locale for number
    formatting
    lc_time = 'C' # locale for time
    formatting

    # - Other Defaults -

    #explain_pretty_print = true
    #dynamic_library_path = '$libdir'
    #max_expr_depth = 10000 # min 10


    #---------------------------------------------------------------------------
    # LOCK MANAGEMENT
    #---------------------------------------------------------------------------

    #deadlock_timeout = 1000 # in milliseconds
    #max_locks_per_transaction = 64 # min 10,
    ~260*max_connections bytes
    each


    #---------------------------------------------------------------------------
    # VERSION/PLATFORM COMPATIBILITY
    #---------------------------------------------------------------------------

    # - Previous Postgres Versions -

    #add_missing_from = true
    #regex_flavor = advanced # advanced, extended,
    or basic
    #sql_inheritance = true

    # - Other Platforms & Clients -

    #transform_null_equals = false




    machine:


    processor : 0
    vendor_id : GenuineIntel
    cpu family : 15
    model : 2
    model name : Intel(R) Xeon(TM) CPU 2.80GHz
    stepping : 9
    cpu MHz : 2785.226
    cache size : 512 KB
    physical id : 0
    siblings : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8
    apic sep mtrr pge
    mca
    cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
    ht tm pbe cid xtpr
    bogomips : 5488.64


    processor : 1
    vendor_id : GenuineIntel
    cpu family : 15
    model : 2
    model name : Intel(R) Xeon(TM) CPU 2.80GHz
    stepping : 9
    cpu MHz : 2785.226
    cache size : 512 KB
    physical id : 0
    siblings : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8
    apic sep mtrr pge
    mca
    cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
    ht tm pbe cid xtpr
    bogomips : 5488.64

    processor : 2
    vendor_id : GenuineIntel
    cpu family : 15
    model : 2
    model name : Intel(R) Xeon(TM) CPU 2.80GHz
    stepping : 9
    cpu MHz : 2785.226
    cache size : 512 KB
    physical id : 0
    siblings : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8
    apic sep mtrr pge
    mca
    cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
    ht tm pbe cid xtpr
    bogomips : 5488.64

    processor : 3
    vendor_id : GenuineIntel
    cpu family : 15
    model : 2
    model name : Intel(R) Xeon(TM) CPU 2.80GHz
    stepping : 9
    cpu MHz : 2785.226
    cache size : 512 KB
    physical id : 0
    siblings : 2
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8
    apic sep mtrr pge
    mca
    cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
    ht tm pbe cid xtpr
    bogomips : 5488.64


    memory:

    total used free shared
    buffers
    cached
    Mem: 4933972 4930596 3376 0
    51848
    4318812
    -/+ buffers/cache: 559936 4374036
    Swap: 1003656 24800 978856








    __________________________________________________ _________
    250MB gratis, Antivirus y Antispam
    Correo Yahoo!, el mejor correo web del mundo
    http://correo..ar

    ---------------------------(end of broadcast)---------------------------
    TIP 6: Have you searched our list archives?

    http://archives.postgresql.org

    marcelo Guest

  4. #4

    Default Re: segmentation fault

    Lonni , folks
     
    from putty terminal from windows statiom 
    default i' guest 
    full , the update statement not have filter clause. 
    the update statement call fts function.
     
    next email y send this information.
    best regards
    MDC







    __________________________________________________ _________
    250MB gratis, Antivirus y Antispam
    Correo Yahoo!, el mejor correo web del mundo
    http://correo..ar

    ---------------------------(end of broadcast)---------------------------
    TIP 1: subscribe and unsubscribe commands go to org

    marcelo Guest

  5. #5

    Default Re: segmentation fault

    From your postgresql.conf it look like you're running with a default
    config, which is very likely unsuitable for the dataset and/or usage
    patterns that you have. Granted that should not cause a seg fault,
    but who knows what kind of weirdness is going on behind the scenes.

    I didn't see any info from you on what kind of 'massive' update you're
    performing that triggers this behavior, or even confirmation of where
    you're seeing it (in psql or elsewhere?). Are you updating all of the
    millions of rows at once? What kind of data is this that you're
    updating?


    On Wed, 9 Mar 2005 16:22:39 -0300 (ART), marcelo Cortez
    <com.ar> wrote: 



    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    L. Friedman com
    LlamaLand http://netllama.linux-sxs.org

    ---------------------------(end of broadcast)---------------------------
    TIP 9: the planner will ignore your desire to choose an index scan if your
    joining column's datatypes do not match

    Lonni Guest

  6. #6

    Default Re: segmentation fault

    On Wed, 9 Mar 2005 16:26:53 -0300 (ART), marcelo Cortez
    <com.ar> wrote: 
    > from putty terminal from windows statiom[/ref]

    That doesn't really answer the question. How are you interfacing with
    the database? Are you using a client, such as psql, or something
    else? putty just means that you're ssh'ing to the server, but once
    you're there, how are you connecting to the DB and issuing this
    update?
     
    > default i' guest[/ref]

    From your postgresql.conf i think i saw a debug5 for min_messages.
    That is not typically a default for most people. Admittedly your word
    wrap in your MUA is rather narrow (like 35 chars) so parsing through
    it wasn't the easiest in the world.
     
    > full , the update statement not have filter clause.[/ref]

    Full meaning all the rows are being updated? What kind of data is
    this that you're updating?


    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    L. Friedman com
    LlamaLand http://netllama.linux-sxs.org

    ---------------------------(end of broadcast)---------------------------
    TIP 3: if posting/reading through Usenet, please send an appropriate
    subscribe-nomail command to org so that your
    message can get through to the mailing list cleanly

    Lonni Guest

  7. #7

    Default Re: segmentation fault

    Lonni , folks 

    the fts engine using one tsvector field indexing with
    gist index

    the statement is something like this
    update from veryLargeTable
    set field = to_tsvector( coleace(field1) );
    any indication to improve the one configuration the
    DB.
    thanks for your support.
    best regards
    MDC







    __________________________________________________ _________
    250MB gratis, Antivirus y Antispam
    Correo Yahoo!, el mejor correo web del mundo
    http://correo..ar

    ---------------------------(end of broadcast)---------------------------
    TIP 1: subscribe and unsubscribe commands go to org

    marcelo Guest

Similar Threads

  1. Segmentation Fault
    By Jackson Miller in forum PHP Development
    Replies: 2
    Last Post: August 7th, 09:29 PM
  2. [PHP-DEV] Segmentation fault in v4.3.4
    By Jean-Pierre in forum PHP Development
    Replies: 5
    Last Post: November 27th, 01:31 AM
  3. [PHP] Segmentation Fault
    By Jay Blanchard in forum PHP Development
    Replies: 0
    Last Post: August 15th, 06:21 PM
  4. 1.8.0 Segmentation fault
    By Graham Brooks in forum Ruby
    Replies: 0
    Last Post: July 28th, 08:07 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139